01
Zero-hesitation deploy
One command. No regions, instance sizes or YAML to pick. Agents and people use the same path.
Nothing to pick
- Region
- Instance size
- YAML
One command
homer deploy
The AI-native cloud
Your agents build.Homer runs.
One command to deploy. Built for AI agents. Homer takes your code from push to live, and bills every service per minute on one meter that people and agents can read.
You or your agent
$homer deploy
Same path
- git push
- POST /v1/deploy, coming soon
- MCP: deploy
Push to live
Push to live: build, tests, security, secrets, DNS and TLS, deploy and watch passed; previews are coming soon. The app is live.
Meter · per minuteLast 60 min
Illustrative meter over one hour: the web service and database are metered for 38 minutes, then the idle app sleeps for 22 minutes, which are not metered.
- Web service
- 38min
- Database
- 38min
- Asleep · Not metered
- 22min
Illustrative output for a demo app called notes. Homer runs today as a local engine in Docker. Dashed items, including previews, are coming soon.
The problem
Writing code got cheap.Shipping is still hard.
More code is written than ever. Getting it live, and keeping it safe, is where it stalls.
GitHub commits per month
Monthly commits on GitHub doubled, from 1.4B to 2.9B, since April 2026.
Bar chart. GitHub commits per month: 1.4 billion in April 2026 and 2.9 billion in the latest month reported (GitHub, 20 Aug 2026).
2×
In about four months
More code than ever is waiting to ship.
11%
of 9,041 vibe-coded apps on GitHub have a working deployment.
Deng et al., Sep 2026
91%
of 200 audited, deployed vibe-coded apps had at least one vulnerability.
Deng et al., Sep 2026
Sources: GitHub CTO blog, 20 Aug 2026 (2.9B is the latest month reported); Deng et al., arXiv 2606.23130 (opens in a new tab), Sep 2026.
We lived it
Shipping one AI-built app took us 27+ tools.
Hosting, database, CI, secrets, DNS, auth, QA, security and monitoring. Each one is another account, another bill and another dashboard your agent cannot see.
Secrets: 1 tool
Code review: 3 tools
QA: 2 tools
Security: 2 tools
CI runners: 2 tools
DNS and edge: 2 tools
Hosting: 3 tools
Cloud: 2 tools
Database: 1 tool
Auth: 2 tools
Analytics: 1 tool
Email: 1 tool
Monitoring and observability: 5 tools
27+
Tools for one app
Our own stack count while shipping AI-built apps in 2026. Our count, not an industry statistic.
How it works
You push.Homer does everythingafter that.
One command or MCP call starts the same eight steps, whether a person or an agent sent it. A deploy API is coming soon.
You or your agent
git pushhomer deployPOST /v1/deployComing soonMCP: deploy
Homer, automatically
Every deploy- 01
Build
Every release built in a container.
- 02
Test gate
Your tests must pass.
- 03
Security gate
Blocks high and critical issues.
- 04
PreviewComing soon
A URL per PR, plus a database branch.
- 05
Secrets
Scoped, and kept out of logs.
- 06
DNS + TLS
Domains and certificates, handled.
- 07
Deploy
Health-checked cutover.
- 08
Watch
Auto-rollback on failed checks.
Result
Live app
A live URL, logs, the meter and one-command rollback.
- url
- notes.homer.app
- logs
- homer logs
- meter
- per minute
- rollback
- homer rollback
Homer runs today as a local engine in Docker. Previews with a branched Postgres database and the deploy API are coming soon.
Why Homer
Everyone sells a piece.Homer runs the whole path.
Built agent-first. People and agents deploy the same way and read the same meter.
02Agents can read it
One transparent meter
Every service billed per minute on one meter. Agents read it before they act.
03
Idle apps sleep
An idle app goes to sleep and is not metered while it does. No seats, no minimums, one bill.
0min
Metered while asleep
- No seats
- No minimums
- One bill
04
Spend caps
Set a cap per app and per agent. Agents see the limit before they act.
- App · notes62% of cap
- Agent · release-bot38% of cap
05Coming soon
Previews expire
Every PR gets its own preview, and previews shut down on their own. Nothing forgotten keeps running on the meter.
- pr-42.notes.homer.appLive
- pr-41.notes.homer.appExpired
- pr-40.notes.homer.appExpired
06Agent-first
The whole path on one meter.
Build, test gate, security gate, secrets, DNS, deploy and watch run as one system, with previews coming soon. Built for agents first and just as simple for people.
- Command
- 1
- Meter
- 1
- Bill
- 1
Meter, caps and previews are illustrative, for a demo app called notes.
Use cases
One platform for everything your agents ship.
Homer is built first for AI-built apps and internal tools. The rest is on our roadmap.
Built for now
- 01Core
Ship AI-built apps
Deploy what your coding agents built.
Solo builders · Startups
- 02Core
Internal tools
Share small internal apps inside your company.
Ops · Finance · Non-engineers
Coming soon
- 03
A preview for every PR
A live URL and a branched database per change.
Product teams · Reviewers
- 04
Agent sandboxes
Isolated VMs where agents run code and tests.
AI agents · Agent platforms
- 05
CI runners
Run test suites on Homer runners, billed per minute.
Engineering teams
- 06
Deploy API
AI app builders host their users' apps on Homer.
AI app builders
- 07
Self-healing prod
Homer explains a failure and opens a fix PR.
On-call teams
- 08
Mobile apps
Build and ship Android and iOS apps on the same meter.
Mobile teams
Team
LondonWe hit the shipping wall ourselves.
About Homer
We are two engineers in London. We build with AI agents every day, and we kept losing days to the same 27+ tools to get one app live.
Homer is the cloud we wanted: one command to deploy, one meter to read, and built so agents can use it as well as people.
Alexander Reinicke
CEO · Co-founder
- SWE and operations at Corgi
- Lovable Ambassador
- Ex-PwC, ex-BMW Group
- Apple WWDC23 Scholar
Jaafar Mohamed
CTO · Co-founder
- SWE at Corgi
- Open source and DevEx at Daytona
- 4 years backend at Fingo Africa
- Co-founded Gigsasa
Early access
Be first to shipwith Homer.
Join the waitlist. We will email you when Homer is ready for your first deploy.
- One command
- Built for agents
- Made in London