Enterprise
On-prem deployment for regulated environments
When policy or regulation rules out public cloud, run Ciao-built applications inside your own data center — available under separate terms, with the same governed delivery loop.
On-prem deployment runs Ciao-built applications inside your own data center, behind your own network boundary, and is available under separate terms. Unlike SaaS-only AI app builders, Ciao supports the full range of postures — Ciao cloud, your own AWS, Azure or GCP account, private VPC, or on-prem — so regulated teams can adopt AI-assisted engineering without moving workloads outside infrastructure they control.
Published 2026-07-03 · Last updated 2026-07-03
Some environments cannot make exceptions
There are organizations where the deployment conversation ends before it starts: workloads run in our facilities, under our physical and network controls, full stop. Defense-adjacent suppliers, some public-sector bodies, financial infrastructure operators and healthcare systems with strict data mandates do not need convincing that the cloud is safe — they need vendors who respect that the rule is not theirs to waive.
The awkward result is that these are often the organizations with the largest backlogs of internal software, and the least access to modern delivery tooling. Every AI development platform that is SaaS-only is simply out of scope, whatever its merits. Teams are left choosing between the backlog growing and an exception process that legal will not grant.
Ciao treats on-prem as a legitimate posture rather than an afterthought. Applications built with Ciao can run inside your own data center, under separate terms, with the delivery loop that makes AI-assisted engineering defensible — governed merges, automated QA, security testing and an audit trail — intact rather than stripped out for the deployment target.
What Ciao provides
- On-prem under separate terms — Deploy to Ciao cloud, your own AWS, Azure or GCP account, private VPC, or on-prem under separate terms — the posture is scoped contractually, not improvised per project.
- Governance that survives the boundary — Guardrails maps code into business areas, detects risky changes, applies plain-English policies, records human review and leaves an audit trail behind every merge — the control set your review expects, regardless of where the application runs.
- Testing before and after ship — QA runs deterministic browser replays, self-healing tests and smoke gates before publish; Security runs static scanning, dependency checks and access-control probes, confirming vulnerabilities against the live app before flagging them.
- Standard, exportable code — Ciao generates real React, TypeScript and Supabase applications you own — 100% code ownership, exportable to your own repo at any time, which matters even more when the runtime is your own hardware.
- Model data handling you can put in front of legal — Customer code is not used to train models, and inference runs under zero-retention model contracts — contractual language your counsel reviews during procurement.
- Identity and audit — SSO via SAML and OIDC, optional MFA, role-based access control, and an append-only audit trail across prompts, merges, deploys and admin actions.
How an on-prem engagement runs
1. Qualify the requirement
The enterprise team works through what your regulation or policy actually requires — sometimes a private VPC satisfies it; when it does not, on-prem is scoped under separate terms.
2. Agree the terms
On-prem is a distinct contractual engagement: deployment architecture, operational responsibilities, update cadence and support model are documented before anything is installed.
3. Review the evidence
Your security and legal teams review SOC 2 Type II reports under NDA, the security pack and the data-handling terms — including zero-retention model contracts — as part of procurement.
4. Build and govern
Teams build in plain language with the full delivery loop: Guardrails policy review with recorded human decisions, automated QA and live-confirmed security findings on every serious change.
5. Run inside your boundary
Production workloads run in your data center under your physical, network and operational controls, with the audit trail available to your internal and external auditors.
Verification and commercial notes
On-prem is available under separate terms — deliberately so, because a data-center deployment carries operational commitments on both sides that a standard subscription does not describe. Expect the engagement to start with a scoping conversation, not a checkout page. SOC 2 Type II reports are available under NDA, and the security pack is available on request via the contact page. Serious production programs start at USD 10,000 per year; on-prem terms are quoted on top of that baseline according to scope. If your requirement is a hard cloud boundary rather than a hard facility boundary, the private-cloud posture may fit with less operational overhead — the enterprise team will tell you honestly which one your constraints actually demand.
A note on expectations: on-prem engagements succeed when both sides treat the data center as a first-class deployment target rather than a compromise. The delivery loop was built to be posture-independent — the same Guardrails policies, the same QA gates, the same audit evidence — so your teams are not asked to accept a reduced platform in exchange for the boundary. What changes is where the software runs; what does not change is how defensibly it gets there.
What changes on-prem — and what does not
| Dimension | Ciao cloud | On-prem (separate terms) |
|---|---|---|
| Where the application runs | Ciao-managed infrastructure | Your data center, your controls |
| Governance and audit | Guardrails policies, recorded review, append-only audit trail | Same delivery loop, same evidence |
| QA and security testing | Smoke gates, production checks, live-confirmed findings | Same testing discipline |
| Code ownership | 100% yours, exportable at any time | 100% yours, exportable at any time |
| Commercial model | Programs from USD 10,000 per year | Scoped under separate terms |
Frequently asked questions
Is on-prem a standard product tier?
No — it is available under separate terms. On-prem deployments involve architecture, operations and support commitments that are agreed contractually with the enterprise team rather than sold as a self-serve tier.
Do we lose Guardrails, QA or the audit trail when we run on-prem?
No. The delivery loop is the point of the platform, not a hosting feature. Guardrails applies plain-English policies with recorded human review, QA runs its gates and checks, and the append-only audit trail covers prompts, merges, deploys and admin actions.
How do AI models fit into an on-prem posture?
Model inference runs under zero-retention contracts, and customer code is not used to train models. How model access is architected for your specific boundary is part of the scoping conversation — bring your network and data-flow constraints and the enterprise team will map them.
What evidence can our regulator or auditor see?
SOC 2 Type II reports under NDA, the security pack on request, the contractual data-handling terms, and the append-only audit trail of the work itself — who prompted, who approved, what merged, what deployed. That last item is often what auditors of AI-assisted development actually ask for.
Can we start in the cloud and move on-prem later?
Because Ciao generates standard React, TypeScript and Supabase code you fully own, applications are not welded to one runtime. Many teams evaluate on Ciao cloud or a private VPC, then take regulated workloads on-prem under separate terms once procurement completes.