How the Customer-Owned Cloud Model Works
You own the account. DevPanel makes it usable.
Customer-owned cloud does not mean handing raw AWS or Azure credentials to a web team and hoping for the best.
It means separating infrastructure ownership from platform operation.
Layer 1: Your cloud infrastructure
Your organization controls the cloud account or subscription.
Depending on the selected architecture, this may include:
- Compute
- Networking
- Load balancing
- Storage
- Databases
- Identity and access
- Monitoring
- Backup services
- Security services
The exact architecture depends on traffic, application requirements, risk, and budget.
Layer 2: DevPanel
DevPanel provides the application operating layer.
That may include:
- Application and environment provisioning
- Git-based workflows
- Continuous integration and deployment
- Development, testing, staging, and production environments
- Browser-based VS Code
- Scaling and orchestration
- Backup and recovery workflows
- Central site and portfolio management
- Team access
- Operational support
Layer 3: Your applications and teams
Drupal, WordPress, and other applications run through a repeatable workflow rather than a collection of manually configured servers.
Developers focus on applications.
Digital teams manage sites and environments.
Infrastructure and operational specialists handle the platform responsibilities appropriate to the engagement.
Responsibility model
Your organization owns
- Cloud account and commercial relationship
- Organizational access policies
- Data governance
- Application ownership
- Business requirements
- Final risk decisions
DevPanel supplies
- Platform software
- Automation
- Implementation
- Operational expertise
- Support and escalation
- Enterprise services when contracted
The cloud provider supplies
- Underlying cloud services
- Service-level commitments for those services
- Physical and foundational cloud controls
- Usage billing
A typical transition
- Inventory the current sites, environments, integrations, traffic, and support needs.
- Review current costs and contract assumptions.
- Design the target cloud architecture.
- Establish the DevPanel operating layer.
- Migrate and validate representative applications.
- Test security, performance, recovery, and deployment.
- Move remaining workloads in controlled phases.
- Operate and optimize the platform.