Security
Where your apps and data run, who on your team can touch them, and what your coding agent is allowed to do.
Last reviewed October 2026 security@ownkube.io
Where your data lives
You decide where every app and database runs.
Two regions, your pick
Ownkube Compute runs in Mumbai and Germany. Each app runs in the region you choose for it.
Fenced off from other customers
On Compute, each organization's apps run on an isolated network that other customers and the platform itself can't reach. Every request is checked against your organization.
HTTPS on every app
Every app gets a TLS certificate on its hostname automatically, and it renews on its own.
Or inside your own AWS account
Run the same app in your own or a customer's AWS account and its data stays there. Ownkube connects through a least-privilege IAM role and never holds AWS keys.
- Mumbai live
- Germany live
- Your AWS account live
- GCP and Azure coming soon
Databases and caches
Your data stays reachable only by your apps until you decide otherwise.
Private by default
Postgres and Valkey have no public endpoint until you turn one on. Public access then runs over TLS on its own certificate.
7-day point-in-time restore
Personal and Team databases can keep 7 days of encrypted backups and restore to any moment inside that window.
Standby replicas
On Team, a database can run up to two standbys with automatic failover.
Every console query logged
Statements run from the dashboard Data tab are logged as text, never with their results.
Who can do what
Owners and admins hold everything destructive, and members can deploy. The same rules apply in the dashboard, the CLI and your coding agent.
| Action | Owners and admins | Members |
|---|---|---|
| Deploy, configure and roll back apps | Allowed | Allowed |
| Read logs, metrics and alerts | Allowed | Allowed |
| Delete apps, databases and environments | Allowed | Not allowed |
| Billing, top-ups and budgets | Allowed | Not allowed |
| Credentials and cloud connections | Allowed | Not allowed |
| Open a shell into an app | Allowed | Not allowed |
| Write data from the Data tab | Allowed | Not allowed |
Sign-in goes through Google or GitHub, so Ownkube keeps no account passwords. SSO and audit logging come with Enterprise. SSH keys belong to each person, never to the organization.
Coding agents
An agent deploys for you with your permissions, inside the one organization you approved.
You sign in, not the agent
Connecting a coding agent opens a browser sign-in. You approve access for one organization.
Same role as the person
The agent gets exactly the role of whoever signed it in. Sign it in as a member and it can deploy, while deletes and billing stay with owners and admins.
No shell over the agent
Shell and SSH stay in the dashboard and the CLI, for owners and admins.
Spend controls
A runaway loop can only spend what is already in the wallet.
Prepaid wallet
Usage draws down credit you loaded. At a zero balance services suspend, so spend stops at what you paid in.
Monthly budget
Set a cap and choose what happens when spend reaches it: an email, or a pause for your apps, workers and jobs. Data is kept, and raising the budget resumes them.
Spending alerts
The account owner gets an email at 50%, 80% and 100% of the budget.
Found a vulnerability?
Email us directly and keep it out of public issues until it is fixed.
Include
- Description and impact
- Steps to reproduce
- Screenshots or logs