Engineering intelligence.
Inside your chosen boundary.
Compare Waydev-managed cloud, customer-controlled private environments and disconnected deployments. Explore data flow, ownership and the security review before onboarding.
Pick a deployment. Understand the tradeoffs.
Every option requires a tenant-specific review of classification, identity, integration permissions, network dependencies and contracts.
Managed Waydev Cloud
A managed service for approved SaaS environments. Review tenancy, region, access and integration permissions.
Git · Jira · CI/CD · AI tools
Only approved connectors and source permissions
Managed Waydev analytics
Delivery, AI adoption, investment and role-scoped reporting
Brain inference architecture to be confirmed
Private model data path depends on architecture
Residency
Confirm supported storage and processing regions.
Identity
Review SSO and roles.
Connectors
Document access and retention.
One table for the first security meeting.
The matrix describes areas to validate. It does not promise that every integration or infrastructure vendor is supported.
| Dimension | Managed cloud | Private cloud | Disconnected |
|---|---|---|---|
| Infrastructure ownership | Waydev | Customer | Customer |
| Data locality | Configured supported region | Approved customer region | Customer perimeter |
| Network | Controlled online connectivity | Customer routing policies | Offline ingress and updates |
| Integration fit | Supported online providers | Approved private/public sources | Compatible self-hosted providers |
| Security work | Contract, tenancy, IAM | Network, keys, operations | Patch, support, audit and egress tests |
| Commercial scope | Per agreement | Per technical scoping | Per technical scoping |
Give evaluators the details they need.
Source to report
Permissions, data categories, storage and retention.
Identity and roles
SSO, RBAC and integration permission scope.
Inference boundary
Model location, dependencies and supported connections.
Sustainment plan
Patching, updates, backup, incident handling and support.
Start with a defined boundary.
Map your requirements to a supported Waydev configuration and verify them through a technical evaluation.
