Skip to main content

Enterprise

Bolti's standard product is designed to get a small team from zero to a working production agent in an afternoon. The enterprise plan is for the cases where that's not enough — where you have stricter security requirements, regulatory constraints, multi-region operations, multi-team governance, or volume that needs dedicated capacity.

This page is a map of what changes when you move from the standard product to enterprise, and where to read more about each piece.

When to consider enterprise​

You don't need to be huge to need enterprise — you need to have at least one of these:

SignalWhat's behind it
"Audio cannot leave our network."Security or regulatory constraint that rules out third-party hosting. → On-Prem Deployment
"Customer data must stay in <region>."Residency requirement (DPDP Act, GDPR, sovereign data laws). → Data Residency
"We can't send PII to OpenAI / Anthropic / etc."Vendor or compliance policy on what reaches third-party LLMs. → PII Data Protection
"We have many independent customers / business units."You need clean tenancy boundaries for billing, isolation, branding. → Sub-Accounts
"We need centralized control over many workspaces."Org-wide policy, SSO, audit logs, role governance at scale. → Organization Management
"We're going to do hundreds of concurrent calls."Dedicated capacity, SLAs, capacity planning. → contact your account team
"We need to sign a DPA / BAA / SCC."Standard legal cover for processing personal or health data. → contact your account team

If none of these apply, you almost certainly don't need enterprise — the standard plan covers everything in Getting Started, Agent Setup, Tool Calling, and Calling.

What changes on enterprise​

Enterprise isn't a different product — it's the same Bolti, with additional controls, deployment options, and contractual cover unlocked.

Deployment options​

The standard plan runs in Bolti's managed cloud. Enterprise unlocks two additional shapes:

  • Multi-region managed cloud — your tenant runs in EU, US, or another supported region instead of (or alongside) the default India region. See Data Residency.
  • On-prem — the entire stack runs inside your environment (your VPC, your bare metal, or your private cloud). See On-Prem Deployment.

Both options keep the same dashboard, same API, same MCP server, same agent runtime — they just change where the data and compute live.

Security & privacy controls​

Beyond the defaults that apply to every workspace, enterprise adds:

  • PII redaction in the agent runtime, with hybrid regex + NER detection and per-workspace policy. See PII Data Protection.
  • SSO (OIDC / SAML) with Okta, Azure AD, Google Workspace, or any standards-compliant IdP.
  • Audit logging with retention you control, exportable to your SIEM (Splunk, Datadog, Chronicle, etc.).
  • Custom retention policies for recordings and transcripts.
  • Dedicated KMS for at-rest encryption keys.

Tenancy & governance​

For organizations running Bolti across multiple internal teams or customer-facing sub-brands:

  • Sub-Accounts — fully-isolated tenants under a single contract, with separate billing rollups and per-account branding.
  • Organization Management — central policy controls across all your workspaces (default roles, allowed providers, allowed regions, mandatory PII profiles).

Operations & support​

  • Dedicated support channel with the engineering team — Slack Connect, shared Jira, or your preferred channel.
  • Architectural reviews at the start of the engagement and quarterly thereafter.
  • SLA on uptime and response times — specific numbers depend on your deployment shape.
  • Reserved capacity for predictable concurrent-call volumes — no contention with other tenants.
  • Custom upgrade cadence for on-prem, so you control when new versions land.

Contractual cover​

  • Master Service Agreement that replaces the standard click-through terms.
  • Data Processing Agreement (GDPR-aligned), signed.
  • Business Associate Agreement for HIPAA workloads on US deployments.
  • Standard Contractual Clauses for cross-border transfers where applicable.
  • DPDP Act addenda for India-resident personal data.

Pick a starting point​

Most enterprise conversations start in one of three shapes. If you're not sure where you are, the page that matches your hardest constraint is usually the right entry point.

If your hardest constraint is…Start here
Where data physically livesData Residency
Whether data can leave your network at allOn-Prem Deployment
What gets sent to third-party LLMsPII Data Protection
Multi-customer / multi-brand isolationSub-Accounts
Centralized policy across many teamsOrganization Management

These pages aren't exclusive — most enterprise deployments combine two or three. A typical regulated-industry rollout, for example, lands on data residency (EU region) + PII redaction (healthcare profile) + organization management (SSO + audit log).

How an enterprise engagement works​

The engagement is short and concrete — we want you in production, not in procurement.

  1. Discovery call (30–60 min). We understand your scale, regulatory posture, existing infrastructure, and timeline. You hear what's realistic and what isn't.
  2. Architecture proposal. Within a week, you get a written proposal: deployment shape, region, providers, capacity sizing, security controls, and price.
  3. Legal review in parallel. DPA / BAA / MSA / SCCs negotiated alongside technical work — not sequentially after it.
  4. Staging deployment. We stand up your tenant (or your on-prem stack) in a non-production environment and validate end-to-end.
  5. Production rollout. Once staging is green, we cut over and document a runbook with your team.

Typical timeline: 2–6 weeks from discovery to production traffic. On-prem in unfamiliar environments can run longer; cloud-region adds for established customers can be done in days.

Talk to us​

The fastest path is to reach out via your account team or hello@bolti.co.in with:

  • A one-paragraph description of what you're building
  • Your hardest constraint (residency, on-prem, PII, scale, compliance)
  • Your target go-live timeline
  • Existing relevant infrastructure (cloud provider, IdP, telephony carrier)

We'll come back within a business day with a discovery slot and an initial read on the right shape.