Yeeted
Hosting for AI-built apps.
Run by your coding agent.
Yeeted is a hosting platform for AI-built apps. Your coding agent deploys and manages your app, databases, logs, domains, and rollbacks from the conversation.
Every plan deploys to development. Production apps are on Small Business and up, which opens after the beta.
Three words: “deploy my app”
Claude, Cursor, or any MCP-enabled agent sends your code straight to us. No terminals, no config files.
Every deploy lands in a test space first, so nothing breaks for real users. On Small Business and up (after the beta), that space is seeded from a snapshot of your production data.
Say “make it live.” On Small Business and up, after the beta, we swap it into production instantly - and one word rolls it back.
The deploy target your agent can drive alone
Agents don't read dashboards - they read tool results. Every Yeeted answer is designed to be acted on by a model: structured, honest, and never blaming your code for our problems.
Every failure carries cause_category and self_fixable, with file:line when it's the code. A capacity miss says "platform, don't touch your app." A stack trace says "fix this line." No more agents rewriting healthy code because a build queue hiccuped.
validate dry-runs before shipping, smoke_test probes the live app, diagnose returns one internally-consistent verdict with a recommended action, and rollback restores a retained app image by checkpoint name or git hash. An agent can run the app deployment cycle unattended.
Re-sending identical code is a no-op, not a second build. Retry loops can't stampede. project_context reports live capacity headroom, and queue_on_capacity parks a batch deploy until a slot frees instead of failing it.
Every deploy is a numbered version with stored source. whats_changed diffs two versions, checkpoint names a known-good state, and new errors are flagged new since last deploy, so the agent knows whether to fix forward or roll back.
Under the hood
For the curious: your history is the source of truth, immutable builds are what actually run.
Auto-detection covers common layouts for Node.js, Next.js, React/Vite, Python (FastAPI), PHP, Ruby (Rails/Rack), Go, static HTML. Unrecognized layouts need a Dockerfile. See build support and beta stacks.
Plans that grow with your app
More resources, more resilience, safer testing, as you need it.
Beta is free while we're in beta · Paid plans open after it, billed monthly
Managed databases, two engine types
Pro's scope with 500 MB build images
No card needed
For testing and development, not mission-critical apps yet. No SLA or uptime guarantee during the beta, but we're happy to help where we can.
Previews stop 15 min after each start, wake on request
A small managed database
Managed databases, two engine types
Development only; Small Business adds a live app
Larger 2 GB databases
Tests seeded from your production data
Everything in Pro
Everything in Small Business, up to 2 replicas per app
Larger 4 GB databases
Every plan includes unmetered bandwidth and builds (fair use applies). The price above is the whole bill.
Need dedicated capacity, SSO, or a custom SLA? Talk to us about Enterprise →
Common questions
Short answers first; the docs go deeper.
What is Yeeted?
Yeeted is a hosting platform built for apps written with AI coding agents. Your agent deploys straight from the conversation you are already having with it, and Yeeted runs the app with a managed database, logs, secrets and domains - you never touch a server or a config file.
How do I deploy an app with Yeeted?
Tell your agent to deploy - literally “yeet it”. The agent calls Yeeted’s MCP tools, your code is built into a container and comes up on a live URL. There is no git push, no YAML to write and no dashboard step in the loop.
Which AI coding agents does Yeeted work with?
Any agent that speaks MCP over HTTP: Claude Code, Cursor and others. Yeeted is agent-agnostic by design - it works inside whatever tool you already build with, rather than asking you to switch.
Does Yeeted provide databases?
Yes, on the Beta plan (free while we are in beta) and on Developer and up once paid plans open; the Free plan has no database. Yeeted attaches managed Postgres, MySQL, MariaDB, MongoDB or Redis to your project on request and injects the connection details automatically. Exports cover every engine except Redis, as do production-data snapshots (Small Business and up, after the beta), and password rotation covers all five - all driveable by your agent.
Can I roll back a bad deploy?
Yeeted records deploy history and retains rollback images within a bounded window. Ask your agent to use a retained git hash or a named checkpoint, such as “before payments”. A git-hash or previous-image rollback restores app code only; database changes are not automatically rolled back. On plans with database snapshots (Small Business and up, after the beta), a named production checkpoint that captured data can also restore supported production databases except Redis if the restore succeeds. Check the rollback result to confirm what was restored. No git is required.
Do I need Git to use Yeeted?
No. Yeeted deploys the code your agent has in hand and records its source revision. You can diff versions, and restore an app image while it is retained. Name a checkpoint to protect a restore point. If you use git, that works too - Yeeted just doesn’t require it.