Your model stays yours
Ansvar supplies evidence and workflow services. The customer chooses the model, client and inference environment.
Deployment and trust models
Choose who operates the evidence layer. Keep your model where it runs today.
Ansvar runs no server-side language model. Use the managed EU gateway, a dedicated Company environment or discuss the first customer-managed production deployment through a design partnership.
- EU-hosted managed service
- Dedicated Company infrastructure by agreement
- Customer-managed design-partner path
Deployment options
Compare the operator and trust boundary.
The served evidence contract sets the design target. Each deployment must specify infrastructure ownership, receipt attestation and update delivery.
| Decision | Managed EU service | Dedicated Company | Customer-managed design partner |
|---|---|---|---|
| Operator | Ansvar operates the shared gateway service on disclosed EU infrastructure. | Ansvar operates a tenant-exclusive environment, scoped and provisioned under the Company agreement. | The customer would operate the deployment inside its own perimeter under an agreed design. |
| Model inference | Your AI client or agent runs the model. | Your AI client or agent runs the model. | Your existing model environment would stay separate from the evidence services. |
| Customer evidence | Team and Company add paragraph-cited document grounding in tenant-isolated storage under the managed service controls. | The Company agreement can scope the document plane onto the dedicated environment. | Storage, keys and retention would follow the customer-approved production design. |
| Audit evidence | Managed operational records; no Company cryptographic ledger. | Signed, tenant-specific receipts and an exportable audit ledger. | The parties must define keys, signing roles and any external anchoring before production. |
| Corpus updates | Ansvar operates source synchronization and exposes source freshness. | Ansvar would operate the same update and freshness controls for the dedicated environment. | The production scope must define update signing, delivery, freshness limits and air-gap handling. |
| Commercial path | Select the managed plan on the pricing page. | Company agreement with a dedicated infrastructure scope; the first dedicated environment is delivered as a design partnership. | Design partnership with a separate implementation and operating agreement. |
Stable product boundaries
Separate the model, evidence service and licensed content.
A customer-managed install changes infrastructure control. It does not transfer source rights or remove the need to state corpus freshness.
Entitlements still apply
SIS-licensed standards remain licensed per person or machine identity and per standard. A customer-managed installation needs an agreed rights model.
Read the add-on terms →Freshness remains visible
Each deployment must expose the age and health of the evidence it serves. Air-gapped use cannot imply current coverage after updates stop.
Customer-managed design work
Resolve the production contract before installing the platform.
The first production design needs decisions across licensing, update delivery and independent receipt verification.
Packaging and operations
- Approved infrastructure, secrets and storage boundaries
- Digest-pinned release and corpus update channels
- Freshness limits, support duties and recovery procedures
Trust and licensing
- Customer-held keys, signing roles and receipt export
- Standards entitlements and corpus-storage rights
- Independent anchoring where the assurance case requires it
- In-plane agent surfaces serve Anthropic models today; other providers are design scope
Set the trust boundary before the procurement review.
Tell us which systems must stay inside your perimeter, which standards you need and who must attest to each receipt.