Setup · concierto enterprise · talk to us

Concierto, fitted to a regulated environment.

Enterprise is the path for organizations that need data residency, SSO, audit logging, custom model routing, or private inference (Bedrock, Vertex, or your own endpoint). It's quoted per deployment and rolled out with a named TAM, not via the marketing site.

What Enterprise covers

Inference — AWS Bedrock, Google Vertex, Azure OpenAI, or a private endpoint of your choice. Per-team and per-environment routing.
Identity — SAML 2.0 SSO, OIDC, SCIM provisioning, domain-claimed accounts.
Data — VPC peering, dedicated Postgres, BYO-KMS for secrets, exportable audit log per workspace.
Deployment — managed by Concierto in your AWS / GCP / Azure tenant, or fully self-host with a quarterly rollout window from our team.
SLAs — 99.9% on managed deploys, 99.95% on dedicated infra. Named TAM, named on-call.
Compliance — SOC 2 Type II report, GDPR DPA, DPIA on request. HIPAA BAA available on dedicated infra.

Is it a fit?

Common signals you should be on Enterprise rather than Hosted Pro / BYOK Connect:

500+ seats, or expecting to scale past that in the next 12 months.
Procurement requires a master service agreement and a DPA, not click-through ToS.
Your security team needs a vendor questionnaire (CAIQ, SIG, custom) before we get approved.
You’re in a regulated industry (financial services, healthcare, government, defense).
You need agents to call inference inside your own VPC and the data must not leave it.
You want Concierto deployed inside your own AWS / GCP / Azure tenant, not as a SaaS.

Contact sales

Email enterprise@nstack.ai with a one-paragraph note about the team size, your inference constraints (Bedrock? Vertex? air-gapped?), and a rough rollout timeline. You’ll get a reply within one business day with a discovery call slot.

What to bring to the call

Org shape— number of teams that’ll get Concierto, expected agent and track volume, projected model spend.
Identity provider — what your team uses for SSO today (Okta, Azure AD / Entra, Google Workspace, etc.).
Cloud account — which provider, which region, whether VPC peering is on the table.
Inference strategy — are you all-in on one provider, mixing them, or experimenting with private models?
Compliance regime — SOC 2, ISO 27001, HIPAA, FedRAMP, or industry-specific (PCI, GxP, etc.).

Already piloting?

If your team is already on Hosted Pro and the conversation is about graduating to a dedicated deployment, mention the workspace slug and the rough seat count in your first email. That lets us mirror the workspace into the new environment rather than starting fresh.