Enterprise Deployment
Deploy Sage entirely within your own cloud, bring your own AI provider keys, and lock every byte of customer data to the region you choose. Zero vendor lock-in, full audit trail.
Deploy Sage entirely within your own cloud account. Your VPC, your security perimeter, your billing.
| Cloud Provider | Supported Services | Status |
|---|---|---|
| AWS | DynamoDB, S3, Lambda, SQS, CloudFront | Fully validated |
| Google Cloud | Cloud Spanner, GCS, Cloud Run, Pub/Sub | Fully validated |
| Microsoft Azure | Cosmos DB, Blob Storage, Azure Functions, Service Bus | Fully validated |
| Any cloud | Terraform modules are provider-agnostic for compute and queue layers | Portable |
| On-premise | Air-gapped and sovereign cloud deployments | Supported |
You are never forced to route AI model requests through Advent AI's accounts. Use your own API keys from any provider and the latest available models from each.
OpenAI
Direct to your OpenAI billing, including GPT-series and reasoning models
Anthropic
Direct to your Anthropic account, including Claude-series models
Direct to Google AI billing, including Gemini-series models
Azure OpenAI
Custom endpoint and deployment ID for Azure enterprise agreements
OpenRouter
Single key routing across a wide selection of providers and models
Any OpenAI-compatible endpoint
Fine-tuned models, locally hosted models, and private deployments
Your API keys are stored encrypted in your own deployment, never transmitted to Advent AI, and are scoped per-tenant. You control spend, rate limits, and model availability directly from your provider dashboard.
Choose exactly where every byte of your customer data lives. No data crosses regional boundaries unless you explicitly configure multi-region replication.
| Region | Compliance | Coverage |
|---|---|---|
| EU (eu-west-1, eu-central-1) | GDPR | EU-resident data never leaves EU infrastructure |
| US (us-east-1, us-west-2) | CCPA | US federal and state requirements |
| APAC (ap-southeast-1, ap-northeast-1) | Local residency | Regional data residency requirements |
| India (ap-south-1) | DPDP Act | Digital Personal Data Protection Act compliance |
| Sovereign / air-gapped | Custom | Fully isolated deployments for regulated industries |
All modes are provisioned via the same Terraform codebase. Switching from Sage Cloud to BYOC is a configuration change, not a migration.
| Mode | Best For | Data Location | LLM Keys |
|---|---|---|---|
| Sage Cloud (Managed) | Starter and Growth | Advent AI infrastructure | Sage-managed |
| BYOC — Single Region | Mid-market | Your cloud account, chosen region | Your keys |
| BYOC — Multi-Region | Global enterprise | Multiple regions, data-residency locked | Your keys |
| Full Self-Hosted | Regulated / sovereign | On-premise or private cloud | Your keys |
| Hybrid | Custom requirements | Config on Sage Cloud, data self-hosted | Your keys |
Sage Enterprise ships with SOC 2 Type II compliance coverage, Role-Based Access Controls, and an independent audit trail for all data access events.
Shadow-routing provides a parallel audit path that logs every input and output for compliance review without impacting production latency.
Security Controls
Can I use my own AI API keys?
Yes. BYOK (Bring Your Own Keys) is supported for all major AI providers including OpenAI, Anthropic, Google, Azure OpenAI, and any OpenAI-compatible endpoint. Your keys are stored encrypted in your own deployment and never transmitted to Advent AI.
Is my data stored in my own cloud?
Yes, with BYOC (Bring Your Own Cloud). The entire Sage infrastructure stack is provisioned into your AWS, Google Cloud, or Azure account via Terraform. Advent AI provides the application layer but never touches your production data.
How does Sage handle GDPR compliance?
Sage supports region-locked deployments where EU-resident data never leaves EU infrastructure. The Memory Admin API includes right-to-erasure endpoints, and all data is encrypted per-tenant with full audit trails.
Can I switch from Sage Cloud to self-hosted later?
Yes. All deployment modes are provisioned via the same Terraform codebase. Switching from Sage Cloud to BYOC is a configuration change, not a migration project.
Book a personalized demo to see Sage in action, or join our waitlist for early enterprise access.