Deployment overview — A / B / C

Claresia ships in three deployment modes. Pick based on seat count, residency, and regulatory posture.

Mode A

Claresia Cloud Shared

Audience

<200 seats

Time-to-value

< 24 hours

SLA

99.5%

Mode B

Claresia Cloud Dedicated

Audience

200–5000 seats

Time-to-value

5 business days

SLA

99.9%

Mode C

Customer Cloud (BYOC)

Audience

Regulated industries

Time-to-value

2–6 weeks

SLA

99.9% control

At-a-glance comparison

Dimension	Mode A Shared	Mode B Dedicated	Mode C BYOC
Seat range	30–200	200–5000	200–unlimited
Hub location	Claresia Cloud, shared Postgres + RLS	Claresia Cloud, dedicated Postgres per tenant	Customer cloud (Postgres / SharePoint / Snowflake)
Encryption keys	Claresia-rotated AES-256	CMEK in customer-named KMS / Key Vault	Customer-owned KMS
Region choice	eu-south-1 (default)	eu-south-1 (Milano), eu-central-1 (Frankfurt) (more on roadmap)	Any cloud, any region
Telemetry payloads	Full payload in Claresia Cloud	Full payload in Claresia Cloud	Envelope only (payload stripped customer-side)
DPA required	Online click-through DPA	Signed DPA, Schrems II compliant	Signed DPA + customer security review
SOC 2 evidence delivery	On request	Annual delivery + reviewed	Annual delivery + reviewed
NIS2 Readiness Pack	Not available	Available (Q3 2026)	Available
Time-to-go-live	< 24 hours	5 business days	2–6 weeks
Pricing tier	Standard cc-033 v2	Standard + $12k/yr regional residency (eu-central)	Standard + $50k/yr BYOC fee
Customer-side install	Zero	Zero	Apply Terraform module
SLA — Uptime	99.5%	99.9%	99.9% control plane (data plane = customer-owned SLA)
SLA — Sev 1 response	30 min	15 min	15 min
Support phone	Not included	Included for Sev 1	Included for Sev 1
Customer Lockbox	N/A	Available	Available
IP allowlisting	No	Yes	Yes (customer-controlled)

How to pick

Decision tree

1. Do you have a residency requirement? (EU-only, US-only, sovereign)
   • Yes, but standard region is fine → Mode B
   • Yes, and you need a non-standard region ((EU residency only; no US-Gov pursuit), Azure Gov, Saudi, etc.) → Mode C
2. Are you a regulated industry? (pharma, finance, defense, public sector)
   • Yes → Mode C (data sovereignty, customer KMS, customer audit access)
3. Are you under 200 seats and SaaS-comfortable?
   • Yes → Mode A
4. Otherwise → Mode B

What’s the same across all modes

• Identity is always Claresia Cloud (WorkOS-fronted SAML/OIDC + SCIM)
• Distribution Plane is always Claresia Cloud (publishes Skill IR to your LLM)
• Command Center is always Claresia Cloud
• End-User Surfaces always live in your LLM tenant (Teams app, Slack app, Browser Extension, Adaptive Cards)
• Skill IR contract and Hub schema contract are byte-identical across modes

What’s different

• Hub data plane location (shared Postgres / dedicated Postgres / customer cloud)
• Telemetry granularity (full payload / full payload / envelope-only)
• Customer-side ops burden (none / none / Terraform + security review)
• Pricing add-ons ($0 / +$12k regional / +$50k BYOC)
• Time-to-go-live (<24h / 5 days / 2–6 wks)

The non-functional contract

These hold across all three modes — they are non-negotiable:

1. Per-tenant isolation by default. Postgres RLS keyed on tenant_id, per-tenant CMEK in Modes B/C, per-tenant object-storage prefix.
2. No “shared bucket” patterns.
3. Identity is delegated — Claresia never stores your users’ passwords.
4. Auditability is total. 7-year retention on governance_event chain.
5. Backwards-compatible contracts. You can pin a Skill IR or Hub schema version; breaking changes ship behind feature flags with 12-month deprecation.
6. Cloud-agnostic. Even in Mode A/B, the Claresia control plane is built on Terraform and runs across AWS + Azure + GCP first-class.

Per-mode deep dives

• Mode A — Claresia Cloud Shared
• Mode B — Claresia Cloud Dedicated
• Mode C — Customer Cloud (BYOC)