Platform / Deployment
Your Intelligence. Your Infrastructure. Your Control.
CIP is architected as one application that can run in different environments: hosted by Cirrusage, inside your own cloud, or on private infrastructure. Here is each reference model, and exactly how far along it is.
Same CIP core, different deployment environments.
The application, its intelligence engine and its governance rules stay the same. What changes is who owns the infrastructure, where the data lives, and who operates it.
Cirrusage Intelligence Platform (CIP Core)
Conversations
Text and voice
Pilot (Available in pilot)Memory
Persistent, governed context
Pilot (Available in pilot)Knowledge
Enterprise information
Pilot (Available in pilot)Live Meetings
Real-time assistance
Pilot (Available in pilot)Agents
Governed tasks with human oversight
Roadmap (Architectural roadmap)Governance
Security, policy and audit
Pilot (Available in pilot)
Infrastructure services
On Azure today. A provider-neutral interface in front of these services is the portability architecture we are designing toward.
Models
Language, speech and embedding models
Storage
Object storage for originals
Search
Vector and hybrid search
Identity
Sign-in and access control
Database
Relational database
Secrets
Secrets and key management
Messaging
Queues and events
Observability
Logs, metrics and tracing
Cirrusage-hosted
Managed by Cirrusage
Roadmap (Architectural roadmap)
Cirrusage Cloud
Operated and maintained by Cirrusage
Isolated CIP environment per organization
CIP application
- Web app
- API
- Workers
- Database
- Object storage
- Search
- Secrets
- Monitoring
- Approved models
- Your identity provider
DESIGNED FOR
- Fastest route to value
- Cirrusage-managed operations and updates
- Isolation per organization
Customer-managed cloud
Dedicated deployment in your cloud
In development (In development)Your cloud subscription
Azure first; other providers when validated
Your virtual network
CIP application
- Web app
- API
- Workers
- Your storage
- Your database
- Your search
- Your key vault
- Your identity provider
- Your approved model endpoints
DESIGNED FOR
- You control data residency
- Deployed with containers and infrastructure as code
- Dedicated, single-organization deployment
Private / on-premises
In your data center or private cloud
Roadmap (Architectural roadmap)Your data center or private cloud
Private Kubernetes or supported virtual machines
Your infrastructure
CIP application
- Web app
- API
- Workers
- Internal storage
- Internal database
- Internal search
- Internal secrets
- Internal identity
- Your monitoring
- Local or approved models
DESIGNED FOR
- Customer-owned infrastructure
- Private networking end to end
- Your operational processes and controls
Same CIP core, different deployment environments
Read a text description of this diagram
Top: the CIP core: conversations, memory, knowledge, live meetings, agents and governance. Below it, the infrastructure services the application depends on: models, storage, search, identity, database, secrets, messaging and observability. These run on Azure today.
Below that, three columns, one per deployment model. 1: Cirrusage-hosted, managed by cirrusage. 2: Customer-managed cloud, dedicated deployment in your cloud. 3: Private / on-premises, in your data center or private cloud.
- Available in pilot
- Working in the Cirrusage-operated CIP environment today, shown in guided walkthroughs and available to design-partner pilots. Not generally available.
- In development
- Partly built, or built and not yet validated end to end. Being actively engineered.
- Architectural roadmap
- Part of the platform architecture we are designing toward. Not built yet.
Each model in detail.
Choose a model to see its reference architecture, where it stands today, and who it suits.
Cirrusage-hosted
Managed by Cirrusage
Roadmap (Architectural roadmap)Cirrusage Cloud
Operated and maintained by Cirrusage
Isolated CIP environment per organization
CIP application
- Web app
- API
- Workers
- Database
- Object storage
- Search
- Secrets
- Monitoring
- Approved models
- Your identity provider · Enterprise sign-in
DESIGNED FOR
- Fastest route to value
- Cirrusage-managed operations and updates
- Isolation per organization
Read a text description of this diagram
Organization users connect over HTTPS to cirrusage cloud (operated and maintained by cirrusage). Inside the boundary labelled “Isolated CIP environment per organization” runs the CIP application: web app, API and workers.
Supporting services: Database, Object storage, Search, Secrets, Monitoring, Approved models.
Integrations: Your identity provider (Enterprise sign-in).
Cirrusage-hosted
Managed by Cirrusage
WHERE IT STANDS TODAY
CIP runs today in a Cirrusage-operated Azure environment used for development and guided walkthroughs. A managed service for customer organizations is part of the architecture, not yet offered.
BEST FOR
Organizations that want the platform without operating it.
Customer-managed cloud
Dedicated deployment in your cloud
In development (In development)Your cloud subscription
Azure first; other providers when validated
Your virtual network
CIP application
- Web app
- API
- Workers
- Your storage
- Your database
- Your search
- Your key vault
- Your identity provider · Microsoft Entra ID
- Your approved model endpoints · e.g. Azure OpenAI in your subscription
DESIGNED FOR
- You control data residency
- Deployed with containers and infrastructure as code
- Dedicated, single-organization deployment
Read a text description of this diagram
Your users connect over HTTPS to your cloud subscription (azure first; other providers when validated). Inside the boundary labelled “Your virtual network” runs the CIP application: web app, API and workers.
Supporting services: Your storage, Your database, Your search, Your key vault.
Integrations: Your identity provider (Microsoft Entra ID); Your approved model endpoints (e.g. Azure OpenAI in your subscription).
Customer-managed cloud
Dedicated deployment in your cloud
WHERE IT STANDS TODAY
Infrastructure as code already deploys a complete CIP environment into an Azure subscription. Deployment into an independent customer Azure subscription and tenant is the first portability target, and is not yet validated. Other clouds are not yet supported.
BEST FOR
Organizations whose data must stay inside their own cloud boundary.
Private / on-premises
In your data center or private cloud
Roadmap (Architectural roadmap)Your data center or private cloud
Private Kubernetes or supported virtual machines
Your infrastructure
CIP application
- Web app
- API
- Workers
- Internal storage
- Internal database
- Internal search
- Internal secrets
- Internal identity · Your directory service
- Your monitoring · Your observability stack
- Local or approved models · On-premises or approved remote endpoints
DESIGNED FOR
- Customer-owned infrastructure
- Private networking end to end
- Your operational processes and controls
Read a text description of this diagram
Internal users connect over HTTPS on your internal network to your data center or private cloud (private kubernetes or supported virtual machines). Inside the boundary labelled “Your infrastructure” runs the CIP application: web app, API and workers.
Supporting services: Internal storage, Internal database, Internal search, Internal secrets.
Integrations: Internal identity (Your directory service); Your monitoring (Your observability stack); Local or approved models (On-premises or approved remote endpoints).
Private / on-premises
In your data center or private cloud
WHERE IT STANDS TODAY
An architectural target for organizations that require private infrastructure. Not built or validated. On-premises is not the same as air-gapped: fully disconnected operation would need local models, speech, search, updates and licensing, and is not planned today.
BEST FOR
Organizations with strict infrastructure or data-sovereignty requirements.
What changes between models.
| Aspect | 1Cirrusage-hosted | 2Customer-managed cloud | 3Private / on-premises |
|---|---|---|---|
| Infrastructure ownership | Cirrusage | You, in your cloud subscription | You, in your data center or private cloud |
| Data residency | Cirrusage-operated region, agreed per engagement | Your chosen regions | Your facilities |
| Identity integration | Your enterprise identity provider | Microsoft Entra ID in your tenant; other providers on the roadmap | Your internal directory |
| Model endpoints | Cirrusage-approved model services | Model endpoints you approve, in your subscription | Local models or approved remote endpoints |
| Operations | Cirrusage | Shared: you run the environment, Cirrusage supports the application | You, with Cirrusage support |
| Network connectivity | Internet over HTTPS | Your virtual network and access policies | Your internal network |
| Maturity today | Architectural roadmap | In development (Azure first) | Architectural roadmap |
1Cirrusage-hosted
- Infrastructure ownership
- Cirrusage
- Data residency
- Cirrusage-operated region, agreed per engagement
- Identity integration
- Your enterprise identity provider
- Model endpoints
- Cirrusage-approved model services
- Operations
- Cirrusage
- Network connectivity
- Internet over HTTPS
- Maturity today
- Architectural roadmap
2Customer-managed cloud
- Infrastructure ownership
- You, in your cloud subscription
- Data residency
- Your chosen regions
- Identity integration
- Microsoft Entra ID in your tenant; other providers on the roadmap
- Model endpoints
- Model endpoints you approve, in your subscription
- Operations
- Shared: you run the environment, Cirrusage supports the application
- Network connectivity
- Your virtual network and access policies
- Maturity today
- In development (Azure first)
3Private / on-premises
- Infrastructure ownership
- You, in your data center or private cloud
- Data residency
- Your facilities
- Identity integration
- Your internal directory
- Model endpoints
- Local models or approved remote endpoints
- Operations
- You, with Cirrusage support
- Network connectivity
- Your internal network
- Maturity today
- Architectural roadmap
Who is responsible for what.
In a private deployment, much of what makes a system secure is operated by you. We make that split explicit rather than leaving it to the contract.
| Responsibility | Cirrusage-hosted | Customer-managed cloud | Private / on-premises |
|---|---|---|---|
| Physical infrastructure and hosting | Cirrusage | Customer | Customer |
| Network boundaries and connectivity | Cirrusage | Customer | Customer |
| Identity provider and user lifecycle | Customer | Customer | Customer |
| Access policy inside CIP (workspaces, roles) | Customer | Customer | Customer |
| Data storage, encryption keys and backups | Cirrusage | Customer | Customer |
| Approved model endpoints | Cirrusage | Customer | Customer |
| Application releases and security fixes | Cirrusage | Shared | Shared |
| Platform monitoring and incident response | Cirrusage | Shared | Customer |
| Regulatory and contractual compliance | Shared | Shared | Shared |
Cirrusage-hosted
- Physical infrastructure and hosting
- Cirrusage
- Network boundaries and connectivity
- Cirrusage
- Identity provider and user lifecycle
- Customer
- Access policy inside CIP (workspaces, roles)
- Customer
- Data storage, encryption keys and backups
- Cirrusage
- Approved model endpoints
- Cirrusage
- Application releases and security fixes
- Cirrusage
- Platform monitoring and incident response
- Cirrusage
- Regulatory and contractual compliance
- Shared
Customer-managed cloud
- Physical infrastructure and hosting
- Customer
- Network boundaries and connectivity
- Customer
- Identity provider and user lifecycle
- Customer
- Access policy inside CIP (workspaces, roles)
- Customer
- Data storage, encryption keys and backups
- Customer
- Approved model endpoints
- Customer
- Application releases and security fixes
- Shared
- Platform monitoring and incident response
- Shared
- Regulatory and contractual compliance
- Shared
Private / on-premises
- Physical infrastructure and hosting
- Customer
- Network boundaries and connectivity
- Customer
- Identity provider and user lifecycle
- Customer
- Access policy inside CIP (workspaces, roles)
- Customer
- Data storage, encryption keys and backups
- Customer
- Approved model endpoints
- Customer
- Application releases and security fixes
- Shared
- Platform monitoring and incident response
- Customer
- Regulatory and contractual compliance
- Shared
“Shared” means the split is agreed per engagement. Regulatory and contractual compliance always depends on how the platform is configured and operated in your environment, and on your own assessment.
How an enterprise adopts CIP.
You should be able to see the route before the first call. This is it.
- 01
A guided walkthrough
See CIP working today, and talk through your environment: identity, networking, data boundaries and approved model providers.
- 02
Requirements and constraints
We map your security, residency and infrastructure requirements against each deployment model, including what is not yet built.
- 03
A scoped design-partner pilot
A pilot shaped around one real workflow and your constraints, with the deployment route agreed up front and the open engineering named.
- 04
Deployment and operation
Production deployment in the model that fits, with responsibilities between your team and Cirrusage written down before go-live.
Bring us your constraints.
Security reviews, network topology, identity providers, approved model endpoints, data residency: the earlier we see them, the more honest our answer about fit.