// Push to deploy. On your own AWS account.

Ship like a
giant.
Stay lean like a
startup.

[ok] Your code stays in your AWS [ok] No lock-in, walk anytime [ok] Free for small teams
// your aws account
live
$ git push origin main
Building image ...
Rolling out ...
Live at api.acme.ownkube.io
us-east-1 · 2m 14s · 0 errors
push_from: GitHub | deploys_to: AWS GCP (soon) | credits: AWS Activate GCP for Startups (soon)

// 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.

Node.js
Go
Python
PHP
Ruby
Rust
Bun
Deno
Next.js
Django
Ruby on Rails
Laravel
Spring
.NET
Elixir
Docker
PostgreSQL
Redis
MongoDB
GitHub

// why_ownkube

Use what you already pay for in AWS.

Activate credits, Savings Plans, your VPC. Ownkube turns them into a developer platform without a platform team.

Every AWS dollar lands as AWS.

Wholesale rates. No platform markup. Activate credits and Savings Plans burn against your bill, not ours.

aws.bill / your-account
EC2 (Savings Plan) $0.0464/hr
EC2 (spot burst) $0.0139/hr
Activate credit applied - $312.40
Ownkube markup $0.00

Your VPC, your data

Workloads, databases, secrets stay inside your account. Disconnect anytime.

Compute that fits

Right-sized services, on-demand plus spot, idle envs auto-sleep.

Savings Plans first

Baseline rides your committed rates. Bursts spill to spot. Nothing wasted.

// autonomous_agents

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.

Live feed
[12:00:01] detect: api-worker over-provisioned, 2GB allocated, 340MB peak
[12:00:05] action: right-sized to 512MB, idle envs scheduled to sleep
$18/mo saved

Incident agent

Translates crashes into plain-English root cause hints.

Log analytics
[14:22:10] alert: api-worker crashed, restart loop after deploy
[14:22:15] cause: out of memory, 2GB dataset into 512MB instance
Rolled back to v1.2.0

Scaling agent

Adjusts replicas and spot placement ahead of traffic.

Traffic monitor
[18:45:00] detect: traffic up 2.4x on api-gateway in 5 min
[18:45:12] action: scaled to 3 replicas, ETA 12s
p95 latency 42ms

Security agent

Watches inbound traffic and flags suspicious activity to admins.

Edge guard
[23:10:00] detect: malicious traffic from 185.220.101.42, 1.2k req/min
[23:10:05] action: IP blocked at edge, admins notified
1 IP blocked

// from_push_to_production

One git push. The platform takes it from there.

Build, ship, deploy, watch. It ships on Ownkube in your own cloud.

01

You push.

git

git push origin main. That is the whole interface.

$ git push origin main
Pushing to your cloud...
Ownkube has it from here.
02

We figure it out.

detect

Framework, runtime, env vars. No config file to babysit.

Looking at your repo
FrameworkNext.js
RuntimeNode 20
Env vars12 carried over
DatabasePostgres, attached
No config file. No babysitting.
03

Built in your cloud.

build

Your VPC, your AWS bill at wholesale. Activate credits go further.

Building inside your VPC
api · v1.2.4in your cloud
Regionus-east-1, your account
Computewholesale EC2, no markup
CreditsAWS Activate burns 1:1
04

Live in seconds.

deploy

Preview URL ready to send a customer. Zero downtime, every time.

Rolling out api · v1.2.4
us-east-1a
live
us-east-1b
live
us-east-1c
live
Preview URL ready. Send it to a customer.
Zero-downtime, every time
05

Agents take over.

agents

Cost, Incident, Scaling, Security. The platform team you did not have to hire.

costright-sized api-worker, 2GB to 512MB~$18/mo
incidentno crashes in last 24hhealthy
scalingtraffic up 2.4x · added 2 instances3 live
securityedge clean · 0 blocks todayclear

// 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.

app.ownkube.io/dashboard
Applications Databases Workers Insights
AWS us-east-1
A
Applications
8
All healthy
Databases
4
Auto-backup on
Previews
3
Active PRs
Cost / mo
$412
34% optimized
Service Type Region Last deploy Status
api-gateway Web App us-east-1 2m ago Running
payment-worker Worker us-east-1 1h ago Running
postgres-main Database us-east-1 idle Healthy
Cost agent

3 staging envs idle since 8pm. Auto-slept. ~$127/mo saved this week.

cost trend
$41234% down
uptime / 90d
99.98%

// how it works

Zero to production in three steps

Self-serve from a browser. No config files to write, no sales calls to book.

01

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.

access scope [least privilege]
+ Run compute and databases tagged ownkube
+ Read cluster health and logs
+ Store build artifacts in ownkube buckets
- Create users or change billing
- Touch anything outside ownkube tags
02

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.

$ git push origin main
Built in your cloud
Live at api.preview.ownkube.io
03

Ship and forget

Cost, Incident, and Scaling agents watch the stack from there. You go back to writing product code.

Cost agent
api-worker right-sized. ~$18/mo saved.

// compare

How Ownkube compares

Managed-platform simplicity, running in your own cloud account at wholesale rates.

dimension
Ownkube recommended
Heroku
Render
Railway
Runs in your cloud account
Yes, your AWS
No
No
No
SOC 2 / HIPAA compliance scope
Your AWS, your BAA
Shield add-on
Paid tiers only
Not advertised
Preview environments
Full-stack + DB fork
Review apps
Preview
PR deploy
Cost optimization
Auto-sleep + spot
Eco dynos
Manual
Manual
Burns AWS / GCP credits
Yes, 1:1
No
No
No
Vendor lock-in
Low
High
Medium
Medium
win partial missing

// 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.

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.