Enterprise
Deploy into your own cloud account or private VPC
Keep the full Ciao delivery loop — Guardrails, QA, Security, deployment — while the application and its data run inside AWS, Azure or GCP infrastructure your team already controls.
Private cloud deployment on Ciao means the applications you build run inside your own AWS, Azure or GCP account or a private VPC rather than on shared vendor infrastructure. Unlike AI app builders that host only on their own cloud, Ciao keeps the full delivery loop — Guardrails governance, automated QA, live security testing and deployment — while the workload lives inside a cloud boundary your team already monitors.
Published 2026-07-03 · Last updated 2026-07-03
The deployment boundary is the first question, not the last
For most security architects, the first question about any development platform is not what it builds — it is where the result runs. Network topology, IAM policy, logging pipelines, incident response: all of it is already built around your cloud accounts. A platform that can only host applications on its own infrastructure forces you to extend that perimeter to a new vendor, re-answer every data-flow question, and duplicate monitoring you already operate well.
AI-assisted development sharpens the problem. When software is generated and shipped faster, the deployment target sees more change, more often. If that target sits outside your boundary, every review cycle involves a second organization's controls. If it sits inside your boundary, the change velocity lands on infrastructure your team already governs — same VPC flow logs, same IAM guardrails, same cost controls.
Ciao is built for the second posture. You can start on Ciao cloud for speed, and deploy production workloads to your own AWS, Azure or GCP account or a private VPC when the review demands it. The delivery loop — how software is built, tested, governed and shipped — stays the same; only the place the application runs changes.
What Ciao provides
Each item below is an approved platform capability your reviewers can verify during evaluation.
- Your account, your boundary — Deploy to Ciao cloud, your own AWS, Azure or GCP account, or a private VPC — and on-prem under separate terms for the environments that require it.
- The full delivery loop, unchanged — Guardrails maps code into business areas, detects risky changes, applies plain-English policies and records human review; QA and Security testing run against the application wherever it is deployed.
- Code you own outright — Ciao generates real React, TypeScript and Supabase applications you own — standard code, exportable to your own repo at any time, with no proprietary runtime between you and your cloud.
- Identity aligned with your estate — SSO via SAML and OIDC, optional MFA and role-based access control, so platform access follows the same identity provider that governs the rest of your cloud.
- An audit trail that travels with the work — An append-only audit trail records prompts, merges, deploys and admin actions — evidence your cloud-security review can line up against your own CloudTrail, activity logs or audit sinks.
- Infrastructure designed to scale — Kubernetes, isolated pods, hibernation and wake, and multi-region support underpin the build environment, so the platform side of the engagement holds up as the project count grows.
How a private-cloud engagement runs in practice
1. Scope the posture
With the enterprise team, you define where production workloads will run — which cloud, which accounts, which regions — and what your security review needs to see before go-live.
2. Build with the full loop
Teams describe what they need in plain language; Ciao builds it in real code with Guardrails policy review, automated QA and live security testing on every serious change.
3. Deploy inside your boundary
The application deploys into your own AWS, Azure or GCP account or private VPC, where your existing network controls, logging and monitoring apply from day one.
4. Operate with shared visibility
Doctor, Ciao's read-only AI SRE, probes the live app, DNS and CDN to diagnose issues and draft fixes, while your own observability stack keeps first-party coverage of the infrastructure.
5. Verify continuously
The append-only audit trail, QA production checks and the security dashboard give both your team and your auditors a running record of what changed, who approved it and what was tested.
Verification and commercial notes
Private-cloud deployment is scoped with the enterprise team rather than switched on self-serve, because the right answer depends on your accounts, regions and review requirements. SOC 2 Type II reports are available under NDA, and the security pack — architecture, isolation, data handling — is available on request via the contact page. Serious production programs start at USD 10,000 per year; private-cloud scope is agreed as part of that engagement. If your requirements go beyond a private VPC, on-prem deployment is available under separate terms.
One practical note on evaluations: teams often run the review in two tracks. The security architecture track examines the posture on paper — account structure, network design, logging integration — while a delivery track builds something real on Ciao cloud in parallel. By the time the private-cloud posture is approved, the team already knows how the platform behaves, and the first production workload lands in your account with the evaluation's lessons already absorbed.
Deployment postures compared
| Posture | Where the application runs | Typical fit |
|---|---|---|
| Ciao cloud | Ciao-managed infrastructure | Fast starts, internal tools, evaluation builds |
| Your AWS, Azure or GCP account | Your cloud account, your IAM and logging | Production workloads with cloud-boundary requirements |
| Private VPC | Isolated network inside your cloud estate | Data-sensitive applications behind existing network controls |
| On-prem | Your own data center, under separate terms | Regulated environments that exclude public cloud |
Frequently asked questions
Which clouds do you support for customer-account deployment?
You can deploy to your own AWS, Azure or GCP account, or into a private VPC. The specific account structure, regions and network design are scoped with the enterprise team so the deployment matches how your cloud estate is already organized.
Does governance still apply when the app runs in our account?
Yes. The delivery loop is independent of the deployment target: Guardrails applies plain-English policies and records human review, QA runs smoke gates before publish and production checks after, and the append-only audit trail covers prompts, merges, deploys and admin actions.
Do we keep ownership of the code if we ever leave?
Yes. Ciao generates standard React, TypeScript and Tailwind code with 100% code ownership, exportable to your own repo at any time. An application deployed in your cloud account remains yours, in code and in infrastructure.
How does your team access our environment during deployment?
Access model and operational boundaries are documented in the security pack and agreed during scoping — reviewer-grade detail belongs in that document set rather than a marketing summary. Platform access itself is governed by SSO via SAML and OIDC, optional MFA and role-based access control.
What does private-cloud deployment cost?
It is part of an enterprise engagement rather than a self-serve tier. Serious production programs start at USD 10,000 per year, and private-cloud scope — accounts, regions, review support — is agreed with the enterprise team during procurement.