Skip to content

Changelog

What changed, newest first, and what each change means for your validation. Validation impact says whether the change touches a GxP-relevant function you have qualified: None (no regulated behaviour changed), Low (a regulated function changed in a way your existing PQ still covers — review the release notes), or Re-test (re-run the PQ scripts named).

October 2026 — Security hardening

  • Platform signing key moved into a key-management service. The key that seals signed PDFs is now generated inside OVHcloud KMS and never leaves it; the application holds only the certificate. PDFs sealed before the change still verify against the earlier certificate. Validation impact: Re-test — PDF signing and signed-PDF verification.
  • Django admin requires a passkey sign-in. The platform operators' admin site opens only to staff who signed in with a passkey; its password form is gone. Organisation, user and signing-certificate changes are now kept in an audit history. Validation impact: None for customer workflows (operator-only).
  • One address for everyone. Organisations no longer have their own subdomain; sign-in cookies are bound to the single site address. Validation impact: Low — sign-in and SSO redirect URLs.
  • Rate limits and client addresses. Sign-in and signing rate limits are shared across the whole service, and the client IP address recorded in audit rows can no longer be supplied by the client. Validation impact: Low — audit-trail IP field.
  • security.txt. /.well-known/security.txt says where to report a vulnerability. Validation impact: None.

September 2026 — Sign-up, restore and assistants

  • Self-serve sign-up with a 60-day evaluation; an expired evaluation turns read-only rather than locking you out. Validation impact: None (evaluations are not for GxP use).
  • Organisation restore from an export archive, round-trip tested. Validation impact: Low — export/restore.
  • AI assistants over OAuth. Hosted assistants (Claude.ai, ChatGPT) connect with OAuth as well as API tokens; they edit drafts and never sign. Validation impact: Low — API and MCP access controls.
  • Validation packages are published to organisation admins. Validation impact: None.
  • Records: visual field builder, record-to-record links. Training: My training first, inline attestation, instructor-attested classes; a Reader can complete their own training. Validation impact: Re-test — Quality Records schema editing, Training completion.

August 2026 — eTMF, tasks and data loading

  • Trial Master File: receive CRO transfers, verified and reconciled.
  • Recurring GxP tasks with records and weekly reminders.
  • Table fields in Quality Records, with starter templates updated.
  • Bulk load and export engine for getting data in and out.
  • Training matrix report with Excel export; vendor audit reports.
  • Email through SES with bounce and complaint handling.

Validation impact: Re-test — each new module's PQ scripts (eTMF, Tasks, Quality Records table fields, data loading).

July 2026 — First release

  • Foundation: organisations isolated by database row-level security, email sign-in, SSO (OIDC/SAML), passkeys, and a fresh re-authentication for every electronic signature.
  • Modules: Quality Documents (with Word-to-PDF conversion), Quality Records, Training, People, Deviations & CAPA, Change Control, Complaints, Vendors & Audits, Notifications and Reporting, with global search.
  • Electronic signatures with signing meanings, segregation-of-duties checks and a hash-chained signing log.
  • API and MCP endpoint for AI-tool access.

Validation impact: Initial validation — full IQ/OQ/PQ.