Private Cloud Deployment
Overview
OpsWorker deployed within your own AWS account. All data stays in your infrastructure, providing full data sovereignty while maintaining the same functionality as the SaaS deployment.
How It Works
| Component | Where It Runs |
|---|---|
| Investigation engine | Your AWS account |
| Data storage | Your AWS account |
| Portal | Your AWS account |
| AI models | Your Bedrock / Azure OpenAI / BYO LLM |
| Kubernetes Agent | Your clusters |
Benefits
- Data sovereignty — All data stays in your infrastructure
- Custom AI provider — Use your own Bedrock access, Azure OpenAI, or BYO LLM
- Custom retention — Configure data retention policies to meet your requirements
- Region selection — Deploy in your preferred AWS region
- Network isolation — No data traverses shared infrastructure
Considerations
- Requires AWS infrastructure management (with OpsWorker support)
- Longer setup time compared to SaaS
- Customer is responsible for infrastructure costs
Best For
- Organizations with strict data residency requirements
- Regulated industries (finance, healthcare) with compliance mandates
- Teams that need custom AI provider configuration
Getting Started
Contact the OpsWorker team to plan your private cloud deployment. The team will:
- Assess your requirements (region, LLM provider, retention)
- Deploy OpsWorker in your AWS account
- Provide ongoing support and updates
Next Steps
- Dedicated AWS — Single-tenant alternative
- AWS PrivateLink — SaaS with private networking