Starter
One EC2 instance you size yourself. No Ownkube fee: you pay AWS for the instance. Unlimited apps, workers, jobs, databases and caches on that one box. Also the home of custom domains and access protection.
Run in your own AWS account
Everything else in these docs describes Ownkube Compute: you push code, Ownkube runs it, and you pay for what you use. This section covers the option to run the same apps inside your own AWS account instead. Same deployments, same environments, same dashboard, logs, metrics and alerts. The difference is where the containers run and who gets the AWS bill.
When to run in your own account
Section titled “When to run in your own account”- Data residency. Your code, databases, logs and traffic never leave your VPC. Ownkube’s control plane only holds configuration. See Security.
- Your own bill. AWS charges you for the instances directly. Credits, Reserved Instances and Savings Plans apply as usual.
- A customer’s account. Deliver your product into a customer’s AWS account and still operate it from one dashboard.
If none of those apply, stay on Ownkube Compute. It is cheaper to start and there is nothing to provision.
Two cluster shapes
Section titled “Two cluster shapes”Production
Managed EKS across availability zones with node autoscaling. $5 per vCPU and $1 per GiB RAM a month, metered per second on what your deployments request. AWS bills the underlying compute at its own rates.
You can run both at once in the same organization, for example Starter for development and Production for live traffic. Clusters compares them in detail.
Set up in three steps
Section titled “Set up in three steps”-
Connect your AWS account
A CloudFormation stack creates one least-privilege role Ownkube assumes with a unique external ID. No access keys are stored. About three minutes. See Connect your AWS account.
-
Create a cluster
Pick Starter or Production, a region and a size. Starter is ready in about five minutes, Production in about ten. See Create a cluster.
-
Deploy to it
Choose the cluster instead of a Compute region when you create a deployment, or pass
--clustertookctl. Everything after that is the same as on Compute.
What stays the same
Section titled “What stays the same”| Ownkube Compute | Your AWS account | |
|---|---|---|
| Deploy from GitHub, GitLab or an image | Yes | Yes |
| Environments, variables, promotion | Yes | Yes |
| Managed Postgres and Valkey | Yes | Yes. Starter runs a single instance; Production supports standbys |
| Logs, metrics, alerts | Yes | Yes |
| Public hostname with HTTPS | *.ownkube.app | *.ownkube.app, plus your own domain on Starter |
| Sleep when idle, autoscaling | Yes | Yes |
| Billing | Prepaid wallet | AWS bill, plus the Production fee on your wallet |
What is different
Section titled “What is different”- Capacity is yours to size. On Starter you pick the instance. On Production you pick a starting vCPU and memory floor and the node pool scales from there.
- Platform updates. Each cluster runs a cluster platform version. Turn on automatic updates in a weekly window or apply them yourself. See Platform updates.
- Disconnecting is safe. Delete the CloudFormation stack and Ownkube loses access; your clusters keep running on AWS.
Connect your AWS account The CloudFormation stack, the IAM role and every permission it holds.
Create a cluster Walk through the Starter and Production wizards.
Clusters Shapes, the cluster page, platform updates and the CLI.