V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us

Security & trust

How we protect the records auditors read.

V5 stores batch and device records, complaints, CAPAs and e-signatures. This page sets out the controls, where data is hosted and how to get the documents your review needs.

Procurement referenceBackup, recovery & resilienceHow V5 uses AI
Laptop and tablet open on a desk for a security and procurement review

On this page

  • Six pillars
  • Where it runs
  • Controls
  • Security Assurance
  • Procurement Q&A
  • Security Pack
  • Report a Vulnerability
Two hosting regionsLondon + Oregon
One databaseOregon, United States
Independent BackupsGoogle US multi-region
No AI Trainingon Customer Data (EULA §5.1)
Six pillars

What we protect, how we protect it

One line each. Open any card for the detail.

Encryption — in Transit and at RestTLS for user connections; encryption and encrypted backups committed in the Commercial Terms.

Encryption for hosted services and encrypted backups are commitments in the Commercial Terms, and user connections use TLS. Per-layer algorithm and scope confirmation is shared on request. On-Premises customers manage encryption and keys in their own environment; how keys are held depends on their infrastructure.

Identity — SAML SSOSAML 2.0 single sign-on. SCIM provisioning is coming soon.

SAML 2.0 single sign-on with common identity providers such as Okta, Entra ID and Google Workspace; your specific provider is confirmed during scoping. SCIM automatic provisioning is coming soon and is not available yet.

Access Control — RBAC + Workspace IsolationRole-based access, with every tenant query isolated by row-level security.

Roles are stored in a separate user_roles table (not on profiles) to prevent privilege escalation. Every query is RLS-scoped per tenant via security-definer SQL functions. Platform admin gated by hard-coded email allowlist.

Audit Trail — Queryable, Part 11 ControlsWho, when, why and before/after — not editable or deletable in the app.

Signatures, overrides and changes to regulated records are written to an audit trail with user, time, reason and before/after values, and it cannot be edited or deleted through the application. Exact coverage per record type is shown in your demo.

Monitoring & Incident ResponseProduction alerting and a documented incident-response runbook.

Production monitoring with alerts on failed sign-ins, unusual export volume. Documented incident-response runbook with customer notification on confirmed incidents per contract.

Deployment — Cloud or On-PremisesHosted in London (UK and Europe) or Oregon (rest of world), or On-Premises in your environment.

United Kingdom and European customers are hosted in London, United Kingdom (application, database, sign-in, files and backups); other customers are hosted in Oregon, United States. Hosted services include point-in-time recovery, daily independent copies and a separate backup location; the location of each layer is confirmed for your deployment. On-Premises ships as container images you run in your own environment, with customer-owned database and encryption keys; any outbound connections depend on the features you enable and are confirmed during scoping.

Where V5 Cloud runs

Two hosting regions. Your records in one.

United Kingdom and European customers are hosted in London. Everyone else is hosted in Oregon. Independent backup copies are kept apart from the live database.

Your team, anywhere

United Kingdom & Europe

London, United Kingdom

Application, database, sign-in and files

Rest of the world

Oregon, United States

Application, database, sign-in and files

Providers

Google Cloud and Supabase on Amazon Web Services

Not an EU-only or all-copies-in-Europe commitment; support, AI, email and SMS providers are on the Sub-processors page.

Independent backup copies

London (UK & Europe) · Google US multi-region (others)

Kept apart from the live database.

Locations for your deployment are confirmed in your Order. How backup and recovery work

Controls catalog

The checklistyour security team will ask for

Three areas. Open one to see every control.

Application Controls5controls
  • Two e-signatures (preparer + independent reviewer) on formula and master document approval — same-person approvals rejected per 21 CFR 211.186 / 111.205.
  • Immutable approved formulas — edits create v+1 and the previous version stays read-only.
  • Operator-only users locked to /app/kiosk — no admin UI access.
  • Training status can be checked before operator tasks, where your workspace is configured to do so.
  • Device calibration status can be checked before use, where configured; the exact scope is shown in your demo.
Platform Controls4controls
  • Row-Level Security on every tenant-scoped table; security-definer functions for cross-tenant operations.
  • Service-role database key isolated to server-side admin operations; never bundled to client.
  • Secrets stored in encrypted secret manager; rotated on schedule.
  • S.G. Systems does not hold SOC 2 or ISO 27001. Hosting providers' own assurance reports describe those providers, not S.G. Systems, and are shared on request through the security review process.
Data Residency & Ownership4controls
  • Hosted services: United Kingdom and European customers are hosted in London, United Kingdom — application, database, sign-in, files, archive copies and backups. Other customers are hosted in Oregon, United States, with independent backup copies in a Google Cloud United States multi-region location. This is not an EU-only or all-copies-in-Europe commitment: US-hosted support, authorised international support access, and AI, email and SMS providers are listed on the Sub-processors page. The locations for your deployment are confirmed in your Order.
  • On-Premises: data stays in your environment; outbound connections depend on the features you enable.
  • Customer-owned export: regulated records can be exported for your own retention; formats are confirmed per record type.
  • S.G. Systems does not use Customer Data to train AI models (EULA §5.1). When AI features are used, submitted content is processed by the AI providers on the sub-processors page; see How V5 uses AI.
Security assurance

Security assurance

S.G. Systems does not currently hold a security certification or attestation such as ISO 27001, SOC 2 or Cyber Essentials.

Regulatory assessment · completed

Independent 21 CFR Part 11 assessment

Dr R.D. McDowall (R D McDowall Ltd, UK) assessed the V5 Ultimate 5.10 manufacturing technical controls against 21 CFR Part 11 and 211; report approved 25 September 2026. QMS and QC areas were out of scope, and your own procedures are still required. This is a regulatory assessment, not a security certification.

Read the scope and report

Release management for regulated customers

Updates that respect your validated state.

Hosted customers receive advance notice of planned releases and access to a validation pack on request. Private Cloud customers can defer non-security updates for up to 180 days as set out in the Commercial Terms; shared Cloud workspaces move with each release. Full release-management terms — notification lead times, supported version windows, rollback provisions and validation artefacts — are agreed in the customer contract.

If you have specific GxP, Part 11 or Annex 11 requirements you need us to commit to in writing, raise them during procurement and we'll address them in the Commercial Terms or a regulatory addendum.

Procurement reference

Hosting, backup and recovery — straight answers

The questions supplier-assessment teams ask, answered in one place. Where a signed Order or customer-specific agreement exists, it governs. Otherwise the current S.G. Systems SLA and the applicable commercial terms set the commitments; Orders that accepted MSA V1.24 keep its terms. This page describes how the service currently operates; it does not change, add to or replace any contract term.

Version 1.6· 17 November 2026· V5 Ultimate hosted services (Cloud and Private Cloud). On-Premises and customer-managed cloud deployments are operated by the customer; see the On-Premises specification.

Download
Service Levels and Support2Hosting and Data Location2Backup and Recovery7Encryption and Data Protection3Insurance and Commercial Terms3

Service Levels and Support

Is there an uptime SLA, and how does it differ from a 2-hour response?

They are different measures. Uptime measures how much of the month a hosted service is available. A response target measures how quickly a person at S.G. Systems starts working on your issue. For critical (Severity 1) issues that is 2 hours, 24/7/365. It is not uptime, automated recovery or a guaranteed fix time.

  • Uptime, backups, RPO/RTO and service credits apply only to V5 Ultimate Cloud and Private Cloud, under the S.G. Systems SLA (§5 and §6).
  • Severity 1 (critical): a person from S.G. Systems responds within 2 hours, 24/7/365, for every supported deployment, including V5 Classic and on-premises. Hosted services also keep a 1 business hour target during business hours. Other severities run in business hours.
  • A response time is when a person starts working on the issue. It is not a fix time, an automated recovery, an uptime figure or a recovery objective.

Terms: SLA §4 response targets · SLA §5 hosted service levels · SLA §6 service credits. Link to this answer

What happens in a critical outage, and is support 24/7?

A Severity 1 incident gets a human initial response from S.G. Systems within 2 hours, 24/7/365, whether you bought directly or through a reseller, and is worked with engineering until service is restored. You can always report directly to S.G. Systems; the clock starts when your report reaches the S.G. Systems support channel.

  • The commitment is set in the S.G. Systems SLA §4.1. Severity 2 to 4 targets run in business hours (09:00-18:00 local, weekdays) unless your Order says otherwise.
  • Orders that accepted MSA V1.24 keep their accepted support terms until renewal on the new documents.
  • Security incidents follow the notification commitment in Commercial Terms §9.2.

Terms: SLA §4.1 critical support · SLA §3 reporting an issue · Commercial Terms §9.2 security incidents. Link to this answer

Hosting and Data Location

Who hosts the service?

The V5 Ultimate application runs on Google Cloud Run. The database, sign-in and file storage run on Supabase, which operates on Amazon Web Services. Independent backup and archive copies are kept in Google Cloud Storage. Source code, code review and release approval are managed in GitHub; production builds and releases run on Google Cloud.

  • This describes the V5 Ultimate application. The public marketing website is hosted separately and holds no Customer Data from the application.
  • Operating servers in more than one location does not by itself provide failover for the database or for a whole provider.
  • The sub-processors that process Customer Data are listed on the Sub-processors page.
  • Dated supplier assessments (approved 14 October 2026) record our assessment and approval of the hosting, database and source-control suppliers used for the V5 Cloud shared service, with documented conditions and residual risks. They do not cover On-Premises or customer-managed installations.
  • Those assessments record our review and acceptance of the applicable Google Cloud and Supabase ISO/IEC 27001 certification and SOC 2 Type II reports for the service roles assessed. This is supplier assurance, not an S.G. Systems certification; a SOC 2 Type II report is an independent assurance report, not a certification.
  • As recorded in those assessments (12 and 14 October 2026), multi-factor authentication is enforced for administrative access to the reviewed source-control and database supplier organisation accounts. This does not cover every credential, customer sign-in or deployment.

Terms: Sub-Processors. Link to this answer

Where is our data stored geographically?

United Kingdom and European customers are hosted in London, United Kingdom: application, database, sign-in, files, archive copies and backups. Other customers are hosted in Oregon, United States, with independent backup copies in a Google Cloud United States multi-region location. The locations for your deployment are confirmed in your Order.

  • London hosting is not an EU-only or all-copies-in-Europe commitment. Support through S.G. Systems' US-hosted support system, authorised international support access, and AI, email and SMS providers are listed on the Sub-processors page.
  • Before 2 November 2026 the European application location was the Netherlands, with the database in Oregon. Orders keep the locations stated in the version they accepted.
  • On-Premises customers keep data in their own environment.

Terms: On-Premises Specification. Link to this answer

Backup and Recovery

Could we lose a day's lot and traceability records?

Daily backups are one layer of protection, not the only one. Database point-in-time recovery is enabled to help recover from damaged data while the database provider remains available. For that scenario, we work towards a recovery point within about 5 minutes of the incident; this is still being qualified, not a guaranteed limit. If the primary database provider is unavailable, recovery depends on the independent copy, which can be about 24 hours old, plus capture delay. Recent lot and traceability records not captured in that copy could therefore be lost.

The Cloud SLA sets a 24-hour recovery point objective (RPO) and an 8-hour service-restoration objective (RTO) for Severity 1 incidents. RPO concerns recent data potentially lost; RTO concerns time to restore service. These are objectives, not guaranteed maximums or a statement that every incident loses a day of data.

The shorter recovery point depends on the failure scenario. Five-minute file copies are separate and do not mean the whole database is copied every five minutes. Complete end-to-end service recovery timings have not yet been proven.

If your recall readiness, BRCGS procedures or other record obligations require a shorter loss window, raise this before signing. Review deployment-specific recovery evidence and agree any different commitment in your Order. Choosing Private Cloud alone does not establish a five-minute recovery promise or compliance.

Explore the recovery layers and evidence
What is the Recovery Time Objective (RTO)?

RTO is the objective for how long restoring the service takes, not how much data could be lost. Contractually, the S.G. Systems SLA sets an RTO of 8 hours for Severity 1 incidents on Cloud and 4 hours on Private Cloud. Internally we work to a 4-hour target for restoring the complete service, but that target is provisional and has not yet been proven in a full recovery exercise. These are restoration objectives, not guaranteed maximum outage durations.

  • The internal 4-hour figure is an objective, not a tested result, and does not replace the contract.
  • A complete takeover of production at another provider has not yet been exercised end to end (see Latest recovery test).

Terms: SLA §5.1 Cloud · SLA §5.2 Private Cloud. Link to this answer

What is the Recovery Point Objective (RPO)?

RPO describes how far back recovered data may go: recent changes after that point could be lost. Contractually, the S.G. Systems SLA sets an RPO of 24 hours on Cloud and 12 hours on Private Cloud. How much data could be lost in practice depends on what fails: if data is corrupted while our database provider is still running, we aim to recover to within about 5 minutes; if the provider itself is unavailable, the latest independent database copy can be about 24 hours old, plus capture delay. How long restoration takes is a separate measure, the RTO. This does not mean every incident loses a day of data; recent lot and traceability records not captured in the independent copy could nevertheless be lost in a provider outage.

  • The 5-minute figure is a working objective for that one scenario and is still being qualified. It is not a guaranteed data-loss limit for the whole service.
  • Private Cloud backup timing is deployment-specific. Ask for the evidence for your deployment before relying on a figure other than the SLA.

Terms: SLA §5.1 Cloud · SLA §5.2 Private Cloud. Link to this answer

How often is the database backed up?

Point-in-time recovery is switched on for the database, and a full independent copy of the database and files is taken every day. Files are also copied on a separate 5-minute schedule, and archive transfers run hourly.

  • Point-in-time recovery is configured for 7 days. The history actually available varies and has recently been slightly under 7 days, so we do not promise an uninterrupted 7-day window.
  • The 5-minute schedule applies to files only. The whole database is not copied every 5 minutes.
  • The S.G. Systems SLA commitment for Cloud is encrypted backups every 24 hours (§5.1).

Terms: SLA §5.3 disaster recovery. Link to this answer

How long are backups and records kept?

Rolling recovery copies are kept for at least 30 days and operational evidence for 365 days. Scoped manufacturing and contract-signature records are also archived with a 15-year minimum retention setting. No automatic deletion of archives is currently enabled.

  • The archive retention setting is not yet locked, so it can be changed by administrators. We do not describe it as tamper-proof (WORM) storage, and proving that complete, readable historical records can be produced for the full period is still in progress.
  • Backup retention is separate from your contract rights. After termination, Customer Data is retrievable on request for 90 days under Commercial Terms §5.4 (MSA §5.4 for prior Orders), then deleted from active systems subject to the DPA, legal holds and backup rotation. You remain responsible for your own regulatory record retention (§7.3).

Terms: Commercial Terms §5.4 after termination · Commercial Terms §7.3 data retention. Link to this answer

When was recovery last tested, and what did it show?

On 30 September 2026 we restored the previous day's real backup copies into an isolated environment. The database tables, rows and available files were checked, stored signature hashes were verified, and a sample of encrypted values was successfully decrypted.

  • Not yet proven: a full production takeover at another provider, a hosted point-in-time restore, restoring original passwords, MFA and single sign-on, every external dependency, and end-to-end service timings.
  • An earlier test, before the October 2026 region change, showed application traffic rerouting in about 79 seconds. That was an application-only routing test, not a database recovery and not a service-level commitment.
  • After the 2 October 2026 move of the application to the Netherlands, routing checks passed and both locations returned to normal routing. No provider outage or customer workflow was simulated and no timing is claimed.
  • Our policy requires restore tests at least every 90 days and an annual regional or provider exercise.

Link to this answer

Do you have a business continuity and disaster recovery policy?

We have a documented backup and recovery policy and operating guide (current versions dated 5 October 2026). A summary and the latest test evidence are available on request, usually under NDA. We do not currently publish a separate, broader business continuity plan, and we don't claim one beyond what those documents cover.

  • The infrastructure programme behind the policy closed with recorded exceptions. That is not a blanket compliance approval.
  • An approved assessment (rev 3, 25 September 2026) covers the V5 Ultimate 5.10 manufacturing technical controls. It does not cover the QMS or QC areas and is not a disaster-recovery certification.
  • The S.G. Systems SLA §5.3 commits to a disaster recovery plan and periodic recovery testing.

Terms: SLA §5.3. Link to this answer

Encryption and Data Protection

How is data encrypted?

The Commercial Terms (MSA V1.24 for prior Orders) commit to encryption for hosted services and encrypted backups. Connections from users to the service use TLS. We are confirming the exact algorithms and scope for each layer, and share that confirmation on request rather than publish unverified detail.

  • One internal connection, between the database connection pooler and the database, is still being confirmed. For that reason we don't claim end-to-end encryption.
  • On-Premises customers manage their own encryption and keys.

Terms: Commercial Terms §7.3 · Commercial Terms §9.1 security. Link to this answer

How quickly will you notify us of a breach?

Without undue delay and in any event within 72 hours of becoming aware of a Security Incident, followed by a detailed report within 3 business days. The clock runs from awareness, not from later confirmation. Any shorter period required by law or the DPA applies.

Terms: Commercial Terms §9.2. Link to this answer

Can we export our data when we leave, and what does it cost?

Yes. You can export using the software's standard export methods during the subscription and for 90 days after termination on request. Standard exports are not charged as migration services. Custom formats or extra work need a separate written agreement.

  • Standard exports keep records linked to their audit trail and e-signature information as far as the export format allows.

Terms: Commercial Terms §12.5 data export · Commercial Terms §5.4 after termination. Link to this answer

Insurance and Commercial Terms

What cyber and professional indemnity insurance do you hold?

We don't publish insurance limits. Ask us for current certificates and we will share them through the document request below.

Link to this answer

Can the deposit be reviewed?

Payment and deposit terms are set in your Order and the applicable commercial terms. Requests to change them are reviewed by our commercial team; nothing is agreed until it is confirmed in writing.

Terms: Commercial Terms Section 6 Fees and Payment. Link to this answer

Can the liability cap be reviewed?

The current Commercial Terms (§17) limit total liability to the fees paid under the applicable Order in the 12 months before a claim, subject to its agreed terms and exceptions. Requests to change the cap are reviewed by our commercial team and apply only once agreed in writing.

Terms: Commercial Terms §17.1. Link to this answer

Sources and evidence dates

  • S.G. Systems Support & Service Level Agreement Version 1.1 (v5ultimate.com/legal/sla, provided by S.G. Systems, LLC for direct and reseller customers), V5 Commercial Terms for Software and Services Version 2.3 and SG Systems EULA Version 1.2, both dated 19 October 2026 (v5ultimate.com/legal/commercial-terms and v5ultimate.com/legal/eula) — contractual commitments; Orders that accepted Master Services Agreement V1.24 (v5ultimate.com/legal/msa) keep its terms
  • SG Systems Supplier Quality Agreement (SQA) Version 1.11, dated 19 October 2026, sets quality responsibilities for regulated customers (v5ultimate.com/legal/sqa); customers who signed Supplier Quality Addendum Version 1.10 (effective 20 April 2026) keep that version and every right in it
  • SG Systems backup and recovery policy SG-POL-BR-001 v2.10 and guide SG-GDE-BR-001 v2.8, 5 October 2026 — current operating facts (internal; summarised here, not published)
  • Isolated recovery check of 30 September 2026 using 29 September 2026 copies — latest evidence
  • Owner confirmation, 2 November 2026: European hosting moved from the Netherlands to London, United Kingdom; United Kingdom and European customers' application, database, files, archives and backups are in London; other customers remain in Oregon (internal)
  • SG Systems supplier qualifications for Google Cloud, Supabase/AWS and GitHub, revision 1.1, approved 14 October 2026 (internal; summarised only)

Controlled documents (backup and recovery policy summary, recovery-test evidence, encryption scope, insurance certificates, deployment-specific terms) are shared on request, usually under NDA. 17questions answered on this page.

Change history

Current · v1.6· 17 November 2026

Clarified layered recovery protection, potential loss of recent lot and traceability records, and the distinction between data-loss and service-restoration objectives. Made the conditional five-minute objective and provider-outage limits explicit.

Scope: Explanatory wording only. No SLA, Order, legal term, provider configuration or recovery qualification changed. Shorter commitments require deployment-specific evidence and agreement.

Evidence: Existing published recovery reference and SLA §5; no new recovery test or measured result is claimed.

Affects: /security, /security/backup-recovery, /read/security-procurement-reference-2026-11-17

v1.5· 2 November 2026

Hosting locations updated: United Kingdom and European customers are now hosted in London, United Kingdom (application, database, sign-in, files, archive copies and backups), replacing the Netherlands application location. Other customers remain in Oregon, United States.

Scope: Hosting locations only. Not an EU-only or all-copies-in-Europe commitment; support, AI, email and SMS providers are unchanged. Recovery evidence status is unchanged: complete end-to-end service recovery evidence is still required. Data Processing Addendum Version 1.1 records the same locations; Version 1.0 stays in force for Orders that incorporate it.

Evidence: Owner confirmation, 2 November 2026. No test result, failover qualification or approval is implied.

Affects: /security, /security/backup-recovery, /legal/sub-processors, /legal/dpa, /faq/where-is-my-data-stored, /numbers

v1.4· 19 October 2026

GitHub's role corrected (source, review and release approval; production builds run on Google Cloud). Policy references updated to the 5 October 2026 versions. Dated supplier assessment status, supplier ISO/IEC 27001 and SOC 2 Type II assurance (not an S.G. Systems certification) and scoped administrative MFA added. Provider-outage data age reworded as capture delay, separate from restoration time. Earlier routing test dated. Sources list now names the Supplier Quality Agreement Version 1.11 and states the current EULA Version 1.2 and Commercial Terms Version 2.3.

Scope: Descriptive wording only. No contractual commitment changed; recovery evidence status unchanged.

Evidence: Approved supplier qualifications, revision 1.1, 14 October 2026 (internal).

Affects: /security, /security/backup-recovery, /legal/sub-processors

v1.3· 6 October 2026

Application locations updated: the V5 Cloud application now runs in the Netherlands and Oregon (United States), with traffic shared between both, instead of a split by customer region.

Scope: Application servers only. The database, sign-in and file storage remain in Oregon, United States, and EU-only data storage is not implied. Recovery evidence status is unchanged: complete end-to-end service recovery evidence is still required.

Evidence: Owner and CTO confirmation, 6 October 2026. No test result, failover qualification or approval is implied.

Affects: /security, /security/backup-recovery, /faq/where-is-my-data-stored, /numbers

v1.2· 2 October 2026

Deployment split clarified: EMEA and EU deployments run in the Netherlands; the rest of the world runs in Oregon, United States. An internal programme name was removed from the assessment answer.

Scope: Deployment server locations only. It does not mean every database, file, backup or provider location, or every earlier customer deployment, is in that region; each layer is confirmed per deployment.

Evidence: Owner and CTO confirmation, 2 October 2026. No test result or approval is implied.

Affects: /security, /security/backup-recovery, /faq/where-is-my-data-stored, Security procurement reference PDF v1.2

v1.1· 2 October 2026

Server operating locations updated to Oregon (United States) and the Netherlands; Iowa removed. Statements that hosting is US-only or that no EU location exists were withdrawn.

Scope: Server locations only. Database, files and recovery-copy locations are confirmed per deployment; no EU residency, region choice, failover or recovery claim is made.

Evidence: Owner and CTO confirmation, 2 October 2026. No test result or approval is implied.

Affects: /security, /security/backup-recovery, /faq/where-is-my-data-stored, Security procurement reference PDF v1.1 (superseded the same day; not published)

v1.0· 30 September 2026

First published procurement reference: service levels, hosting layers (application in Oregon and Iowa, database in Oregon, US multi-region backups), backup, recovery and retention.

Scope: Hosted Cloud and Private Cloud.

Evidence: Backup and recovery policy and guide of 30 September 2026; isolated recovery check of 30 September 2026.

Affects: /security, Security procurement reference PDF v1.0

For regulated buyers

SQA, DPA, Part 11 — the supplier pack

Everything a supplier assessment asks for, in one pack.

Sub-ProcessorsThe official list, with purpose, data and location.

The official list of sub-processors, with purpose, data and location, is kept on one page so it never drifts. We notify designated Customer contacts at least 30 days before adding a new sub-processor.View the list On-Premises deployments: no sub-processor has access to Customer Data — all data stays in your environment.

Supplier Quality Agreement (SQA)Quality responsibilities for regulated customers.

Change notification, quality issue handling and CAPA, validation support, audit support, supplier oversight and exit. Version 1.11 (binding once signed) can be read online; customers who signed Version 1.10 keep it.

Data Processing Addendum (DPA)Data-processing terms for personal data.

Contractual data-processing terms for personal data in Customer Data. Under the Commercial Terms (§2.32) the DPA is incorporated where required by law or where we process personal data in Customer Data, and is available on request. Sub-processors are listed on the sub-processor page, which also describes the transfer safeguards used, such as the EU Standard Contractual Clauses. The DPA (Version 1.0) applies when an Order expressly incorporates it and can be read online.

21 CFR Part 11 / EU Annex 11Clause-by-clause control matrix.

A control matrix mapping platform features to each clause is available on request. See Security assurance above for the scope of the independent assessment.

For security reviews

We answer security questionnaires without flinching.

Architecture diagrams, the supplier qualification questionnaire and the Part 11 control matrix — available on request.

Read the Commercial TermsRead the S.G. Systems SLARead the EULAPrivacy & subprocessors

Found a vulnerability?

Email security support at support@sgsystemsglobal.com with a clear description and reproduction steps. We acknowledge within two working days, will keep you informed of remediation, and won't pursue good-faith researchers who follow this policy. Full policy at /.well-known/security.txt.

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC

Page version 1.17· Last revised 12 Oct 2026