Skip to main content
Seal follows a structured release process designed for GxP-regulated environments, in accordance with the agile lifecycle principles of GAMP 5 2nd Edition. Every update is tested, reviewed, and categorized by risk level to ensure customers have appropriate notice and time to validate changes.

​
Release previews

Functionality changes are often released behind a Release Preview flag. Admins can enable upcoming changes in Settings → Release Previews to test them before they go live for everyone. This allows Organization Admins to:
  • Test new features before they are enabled for all users
  • Enable previews individually in User Settings
  • Validate workflows and update internal documentation ahead of the wider release
  • Auto-enroll in all future release previews to stay ahead of changes
Features remain in preview for a time period corresponding to their risk level, ensuring adequate time for validation. If you don’t enable a preview, it becomes standard automatically after the testing period—no action required.

​
Risk levels

Every release is categorized into one of the following risk levels:
Risk LevelDescriptionNotification & Preview Policy
NoneNo functionality changes, no user-facing workflow changesNo action required
MinorMinor functionality change; no change to how users carry out work2 weeks advance notice. Released as Preview first
SignificantChanges to how users carry out work (e.g., UI changes)2 weeks advance notice. Released as Preview first
MajorMajor functionality change (e.g., removing a feature)At least 4 weeks advance notice. Released as Preview first
Customer consultation for major changesBefore any major release that could affect your UAT or training, we consult with you directly and extend timelines as needed. Our goal is 100% adoption of the latest release—if any customer cannot upgrade, we treat that as a problem to solve together.
Automated UAT and trainingSeal can fully automate your UAT process and training management within the platform. AI-assisted tools can generate test scripts and training materials, significantly reducing the effort required to validate and roll out new releases.

​
Deployment process

All production releases follow a zero-downtime deployment process:
  1. New version deployed using live/candidate strategy
  2. Automated health checks verify functionality before receiving traffic
  3. Traffic switched only after all validations pass
  4. If any check fails, deployment is cancelled automatically
Every release must pass all automated tests and peer reviews before deployment.

​
Documentation

  • Feature changes are documented in Release Notes
  • Executed platform tests are visible in the Validation tab within your Seal platform
  • All deployment activity is logged and auditable