// Push to deploy. On your own AWS account.
Ship like a
giant.
Stay lean like a
startup.
// scriptable. agent-ready.
npx skills add ownkube/ownkube-cli // your_stack
Whatever you build, it ships on Ownkube.
Push your repo. We figure out the framework, build it in your own cloud, and hand back a preview URL. If it runs in Docker, it runs here.
// the_math
Your AWS account, minus the platform team.
Ownkube runs inside your account at wholesale rates. Activate credits and Savings Plans burn against your bill, not a vendor's margin. The same workload, billed two ways.
Every AWS dollar lands as AWS.
No platform multiplier between you and EC2. Your committed rates carry the baseline, spot absorbs the bursts, and every credit dollar applies in full.
Your VPC, your data
Workloads, databases, and secrets stay inside your account. Disconnect anytime and everything keeps running.
Wholesale, no markup
You pay AWS directly for EC2 and storage. Ownkube never sits in the middle of your compute bill.
Savings Plans first
Your baseline rides committed rates. Bursts spill to spot. Credits apply against the whole thing, one to one.
// the_agent_roster
Four agents do the platform team's work.
Each agent watches one slice of the stack and ships concrete actions with numbers. No vague "AI insights."
Cost agent
Right-sizes workloads, auto-sleeps idle envs, catches spend anomalies.
Incident agent
Translates crashes into plain-English root cause hints.
Scaling agent
Adjusts replicas and spot placement ahead of traffic.
Security agent
Watches inbound traffic and flags suspicious activity to admins.
// from_push_to_production
One git push. The platform takes it from there.
Build, ship, deploy, watch. No config files, no runbooks. It ships on Ownkube in your own cloud.
- 01
You push.
gitgit push origin main. That is the whole interface.
- 02
We figure it out.
detectFramework, runtime, env vars. No config file to babysit.
- 03
Built in your cloud.
buildYour VPC, your AWS bill at wholesale. Activate credits go further.
- 04
Live in seconds.
deployPreview URL ready to send a customer. Zero downtime, every time.
- 05
Agents take over.
agentsCost, Incident, Scaling, Security. The platform team you did not have to hire.
Enumerating objects: 48, done.[detect] framework: Next.js 15 (app router)[detect] runtime: node 22 · postgres 16[build] image pushed to your ECR · 34s[deploy] rolling out to your VPC (us-east-1)[live] https://pr-142.ownkube.app// platform
Watch your agents work.
Apps, databases, agent activity, and your AWS bill in one view. The workloads run in your cloud account, not ours.
3 staging envs idle since 8pm. Auto-slept. ~$127/mo saved this week.
// command_line
Drive Ownkube from your terminal.
okctl is the Ownkube CLI. Connect an AWS account, ship deployments, tail logs, and pull connection details without leaving your shell. It is scriptable, agent-friendly, and every read command speaks JSON.
# Install with Homebrew (macOS and Linux)
brew install ownkube/tap/okctl
# Log in and connect your AWS account
okctl login
okctl aws connect// connect_and_ship
Zero to production in three steps
Self-serve from a browser. No config files to write, no sales calls to book.
Connect your cloud
A few minutes in the browser, one click in AWS. Ownkube only gets the access it needs to ship your apps. Your data and workloads never leave your account.
Push your code
Git push, or point us at a repo. We figure out the framework. You get a preview URL you can send a customer.
Ship and forget
Cost, Incident, and Scaling agents watch the stack from there. You go back to writing product code.
// compare
How Ownkube compares
Managed-platform simplicity, running in your own cloud account at wholesale rates.
// faq
Frequently asked questions
How does Ownkube work?
Ownkube is a developer platform that lives in your own AWS account, with named agents (Cost, Incident, Scaling, Security) that handle the recurring work of a platform team. You connect your AWS account with least-privilege access, push your code via git, and Ownkube handles the rest: building, shipping to your cloud, and watching the apps from there. The named agents run alongside: the Cost agent right-sizes workloads and auto-sleeps idle envs, the Incident agent translates crashes into plain-English root cause hints, the Scaling agent adjusts replicas ahead of traffic surges, and the Security agent flags exposed secrets and access drift.
Should I start on the Starter or Production tier?
Starter is the right default for indie developers, side projects, small-team dev environments, and anyone evaluating the platform. It runs on one AWS instance inside your AWS account and is free for teams: no Ownkube platform fee, no credit card. You only pay AWS for the underlying EC2, at wholesale rates, so AWS Activate credits stretch all the way. Production is the right choice once you have live traffic, need high availability across availability zones, or want a deeper observability story. Production is billed at $5/vCPU + $1/GB RAM per month. You can migrate from Starter to Production without replatforming. The application code and workflow are identical.
What DNS and ingress do I get?
Cloudflare, included in every Ownkube project. Ownkube provisions a ready-to-share preview domain on a Cloudflare subdomain, so you can send preview URLs to customers, teammates, or stakeholders without buying a domain or setting up Route 53. You get Cloudflare's free DDoS protection, bot protection, and scrape protection out of the box. Bring your own custom domain whenever you want.
What database do I get by default?
Ownkube runs Managed Postgres on your own EC2, on both Starter and Production. Fully operated by Ownkube, no managed AWS data services required. You pay only wholesale EC2 for the compute. The same Postgres workflow ships across both tiers.
What clouds does Ownkube support?
AWS right now. GCP is coming soon. Everything deploys into your own cloud account, so you keep full control of your infrastructure, data, and cloud provider credits.
Can I use my AWS Activate credits with Ownkube?
Yes, and burning them efficiently is the whole point. Activate credits expire in 12 to 24 months, so you want to spend them on real infrastructure before they evaporate. Ownkube runs in your own AWS account, so every Activate dollar lands as actual EC2, S3, and bandwidth. On Starter, you pay AWS only, so credits cover 100% of the bill. On Production, AWS infrastructure is billed directly to your account against your credits, and the small Ownkube platform fee ($5/vCPU + $1/GB RAM per month) is billed separately. Same applies to GCP for Startups and other provider credit programs.
What happens if I disconnect from Ownkube?
Your infrastructure keeps running. Ownkube uses vanilla cloud resources, standard VPCs, load balancers, and container services, with no proprietary glue on top. If you disconnect, everything stays in your account exactly as-is. Zero vendor lock-in.
Do I need a platform team to use Ownkube?
No. The four named agents (Cost, Incident, Scaling, Security) cover the work a platform team typically does: right-sizing, crash explanations, replica scaling, IAM drift detection. Indie developers and small teams can ship on Starter without any DevOps knowledge. Scaling startups on Production get the same developer experience without hiring a dedicated DevOps engineer ($180K to $250K loaded cost in the US, by current market rates). Basic cloud and container literacy helps, but nobody on the team needs infrastructure as their full-time job.
// get_started
You shouldn't have to trade velocity for control.
Connect your AWS account in minutes. Push code, get a preview URL, and let the agents take ops off your plate.
Free tier on AWS. Setup in 5 minutes from your browser.