Deployment profiles
Compare hosted, private, and self-host deployment profiles through responsibility boundaries, not sales language.
Generated
2026-04-26T09:14:06.058Z
Overall status
Ready with noted limits
Target studio
https://studio.osuite.ai
Runtime rows
4
Baseline p95 ceiling
2593.34 ms
Burst p95 ceiling
920.41 ms
Soak errors
0%
Plugin signatures
8
Use this page when
Read this page when a buyer or operator asks how responsibilities change across deployment models.
Profiles
- hosted
- private deployment
- self-host
Comparison table
| Profile | Best fit | Main question |
|---|---|---|
| Hosted | teams that want fast rollout with shared operating discipline | how much control stays tenant-visible |
| Private deployment | buyers that need stronger network or data boundaries | which responsibilities shift to the customer |
| Self-host | operators that want the most deployment control | what evidence and buyer packaging remain first-class |
Boundary questions to answer
- where the identity provider lives
- where runtime governance executes
- where proof export and buyer artifacts are stored
- where local hook assets or project config are installed
- whether trusted-project activation is required before local governance loads
- which support and incident responsibilities remain shared
What success looks like
The page is working when a buyer can compare profiles by responsibility boundary instead of asking for a custom explanation of each model.
Read next
Live deployment profile artifact
SaaS
Live profile visible
Architecture
Hosted shared control plane
Network boundary
OSuite-managed public edge with tenant-scoped API enforcement
Operations
OSuite-operated upgrades and release validation
Monitoring and backup
Managed operational monitoring and backup posture
Identity integration
Hosted account center + workspace roles
Dependencies
- Managed database
- Managed Redis
- Managed publication stack
Capabilities
self host
Declared profile
Architecture
Customer-managed private or self-hosted deployment
Network boundary
Customer-owned ingress, egress, secrets, and deployment topology
Operations
Customer platform operations with OSuite deployment guidance
Monitoring and backup
Customer-operated monitoring and restore posture
Identity integration
Customer identity provider and local bootstrap path
Dependencies
- Customer-managed runtime services
- Optional curated plugin sync
Capabilities
azure marketplace
Live profile visible
Architecture
Azure procurement-aligned customer deployment profile
Network boundary
Regional Azure landing-zone aligned boundary
Operations
Shared: OSuite publishes package, customer operates deployment
Monitoring and backup
Customer Azure telemetry and backup posture
Identity integration
Azure/Microsoft-centered enterprise identity path
Dependencies
- Azure subscription
- Customer network and policy configuration
Capabilities
teams plugin
Live profile visible
Architecture
Companion collaboration surface that defers authority to OSuite
Network boundary
Microsoft 365 collaboration boundary with controlled deep links
Operations
OSuite-governed collaboration semantics
Monitoring and backup
Inherited from primary control plane and collaboration telemetry
Identity integration
Microsoft 365 collaboration identity mapped to workspace authority
Dependencies
- Teams app packaging
- OSuite deep link and approval flows
Capabilities