--- title: "Kuberns Facts | Regions, Backups, Pricing Model and Compliance" description: "Verified facts about Kuberns in one place: regions, database backups and restores, how billing works, support, availability and compliance status." source: "https://kuberns.com/facts" --- # Kuberns facts Verified facts about the Kuberns platform in one place. Prices and plan details are on the pricing page, so they are never out of date here. Last updated 7 November 2026. ## Company - **Company**: Kuberns Tech Private Limited. - **What Kuberns is**: An Agentic AI platform for deployment that helps teams deploy, operate, and scale full-stack and complex backend projects. - **Contact**: Email support@kuberns.cloud, or use the contact page. ([Contact](https://kuberns.com/contact)) ## Regions and data location - **Deployment regions**: Mumbai, Sydney, London, Frankfurt, and N. Virginia (U.S.A). You choose the region when you create a service. - **Where platform data is processed**: The control plane, accounts, billing, and platform metadata are hosted in India. AI processing for the deployment agent happens in the United States. Deployed applications run in the region you choose. ([Security](https://kuberns.com/security)) - **Third parties**: Every third party that receives personal data is listed on the subprocessors page. ([Subprocessors](https://kuberns.com/subprocessors)) ## Pricing and billing - **Billing model**: You pay for runtime. One credit equals one US dollar and is charged while resources run, with no per-service subscriptions. - **Data transfer**: 5 GB of data transfer per month is included for each service environment. Transfer above that is billable. - **Plans and prices**: Current plans and prices are on the pricing page. ([Pricing](https://kuberns.com/pricing)) ## Deployments - **Git provider**: GitHub. A push to the deployed branch triggers a deployment through a signed webhook. - **Frameworks with a dedicated guide**: Node.js, React, Django, Flask, FastAPI, Laravel, and Spring Boot. ([Services](https://kuberns.com/services)) - **Health checks**: If you set a health check path and a Git push deployment leaves the application down, Kuberns restores the previous version. - **Team roles**: Owner, Co-Owner, Maintainer, Developer, and Partner. ## Databases and backups - **Managed databases**: PostgreSQL, MySQL, and MongoDB. - **Backups**: Take a backup on demand, or turn on automatic backups on an interval you choose: every 1, 3, 6, 12, or 24 hours. - **Restore**: Restore a backup from the dashboard, or restore from your own dump file (uploads up to 5 GB). A restore replaces the current data, and Kuberns takes a safety backup first. A restore returns the database to the state of the backup you pick, so writes made after that backup are not recovered. ([Restoring a database](https://docs.kuberns.com/docs/datastores#restoring-a-database)) - **Retention**: Kuberns does not expire backups automatically. They stay until you delete them. Deleting a datastore is irreversible, so download any backup you still need first. ## Availability - **Uptime commitment**: Kuberns does not offer a contractual uptime commitment on self-serve plans. ([Terms of Service](https://kuberns.com/terms-conditions)) - **Live status**: Current service status is published at status.kuberns.com. ([Status](https://status.kuberns.com)) - **Self-healing**: Kuberns detects and attempts recovery for supported container failures. Recovery is best effort and is not an uptime guarantee. ## Security and compliance - **Certifications**: Kuberns does not currently hold SOC 2 or ISO/IEC 27001 certification. The platform is tested internally by our own team. That is our own testing, not an independent audit. - **Security practices**: Encryption, access control, backups, incident response, and shared responsibility are described on the security page. ([Security](https://kuberns.com/security)) - **Report a vulnerability**: Use the contact details in our security.txt. ([security.txt](https://kuberns.com/.well-known/security.txt)) - **Privacy and data handling**: The privacy policy, data processing addendum, and data retention periods are published. ([Privacy Policy](https://kuberns.com/privacy-policy)) ## Support - **Availability**: Support is available 24/7. - **Channels**: Email support@kuberns.cloud, the help assistant in the dashboard, or the contact page. ([Contact](https://kuberns.com/contact)) - **Who helps you**: Customers work directly with a Kuberns engineer, who stays with the problem until it is resolved. ## Frequently asked questions ### Is Kuberns SOC 2 or ISO 27001 certified? No. Kuberns does not currently hold SOC 2 or ISO/IEC 27001 certification. The platform is tested internally by our own team. That is our own testing, not an independent audit. Our security practices are described on the Kuberns security page at https://kuberns.com/security. ### Does Kuberns have an uptime SLA? Kuberns does not offer a contractual uptime commitment on self-serve plans. Live service status is published at https://status.kuberns.com. ### How do database backups and restores work? You can back up a managed PostgreSQL, MySQL, or MongoDB database on demand, or automatically on an interval you choose: every 1, 3, 6, 12, or 24 hours. You can restore a backup from the dashboard, or restore from your own dump file. A restore replaces the current data, and Kuberns takes a safety backup first. A restore returns the database to the state of the backup you pick, so writes made after that backup are not recovered. Kuberns does not expire backups automatically. They stay until you delete them, and deleting a datastore is irreversible, so download any backup you still need first. ### Which regions does Kuberns run in? You can deploy in five regions: Mumbai, Sydney, London, Frankfurt, and N. Virginia (U.S.A). You choose the region when you create a service. ### What support does Kuberns provide? Support is available 24/7 by email at support@kuberns.cloud, through the help assistant in the dashboard, and through the contact page at https://kuberns.com/contact. Customers work directly with a Kuberns engineer, who stays with the problem until it is resolved.