Kabaido Cloud and Private Cloud
Kabaido runs on Kabaido Cloud by default; Private Cloud keeps your database, files and sign in in your own account, in your region.
Updated 10 November 2026
On this page
- Why
- Some companies need their data stored in an account they own.
- How
- Kabaido Cloud unless you ask for Private Cloud at the proposal.
The two choices
| Kabaido Cloud | Private Cloud | |
|---|---|---|
| Offered | The default. Recommended | Optional, on request and quoted separately |
| App and engine | Kabaido's | Kabaido's |
| Database, files and sign in | Kabaido's, with each customer isolated | Your own account, in the region you choose |
| Your engine file | Sealed, in your workspace | Sealed, in your own database |
| Effort | Nothing extra | A heavier implementation |
Kabaido Cloud
One production for every customer. Each customer is an organisation of its own, isolated from every other, with its engine file sealed separately. Security describes the isolation.
Private Cloud
Private Cloud moves only the data. You create the database account in your region and grant Kabaido a limited role. Your workspace is routed to it.
The app does not move. In Private Cloud your data passes through the app in memory while a request runs and is stored only in your own account: stored in your account, processed by Kabaido's app.
Private Cloud is arranged for a project that asks for it. Raise it at the walkthrough so it is in the proposal.
What is not offered
Kabaido does not run on computers at your site in current projects.
Related
- The engine file and the driveYour dedicated design modules are one sealed file that opens only inside Kabaido with two keys. A copy stays with you on an encrypted drive.
- How an implementation runsAn implementation runs in five steps, from a walkthrough on a live workspace to a handover with your people and your Claude connected.