Help

Everything you need to get set up - and answers to the questions we hear most.

Getting set up

The one thing to understand: Yeeted is driven by your coding agent. You connect the agent once (it takes a minute), and from then on you deploy by asking - "Deploy this project to Yeeted" - not by filling in forms. The getting-started walkthrough covers this step by step; the short version:

1. Copy your MCP URL: loading…

2. Add it to your agent as an MCP server (per-agent instructions are in the walkthrough and on the Connect agent page).

3. Connecting opens a browser window - log in and approve. Done. (Claude Code: run /mcp and choose Authenticate; Cursor: press Login next to yeeted in its MCP settings.)

Using Claude? The easiest path is Claude's connector settings - visit claude.ai/new#settings/customize-connectors, add a custom connector, and paste your MCP URL. Claude Code users can instead run:

loading…

Q&A

I connected my agent - now what?

Open a project in your agent and ask it to deploy:

"Deploy this project to Yeeted."

The agent packages your code, builds it, and replies with a live URL. Your app then appears on the dashboard with its status, logs, and metrics.

My agent doesn't show any Yeeted tools.

Most often the agent has not logged in yet: Yeeted shows no tools until you do. In Claude Code run /mcp, pick yeeted and choose Authenticate; in Cursor press Login next to yeeted in its MCP settings. Otherwise the MCP server wasn't added (re-check the config against the walkthrough) or the agent wasn't restarted after adding it.

What plan am I on? What does it cost?

Every new account starts on the free plan automatically - there's nothing to choose at signup. It includes 5 projects and a budget of 5 deployments and builds, which does not reset. While we're in beta, switch to the Beta plan on Billing when you run out or want a managed database: Pro's scope (30 projects, 3 running at a time, managed databases) at no cost and with no card. The paid plans are shown there with their prices but are not on sale until after the beta: Developer ($10/mo), Pro ($20/mo), Small Business ($50/mo, 1 always-on production app) and High Availability ($199/mo, 10 production apps with up to 2 replicas each). If you already pay for a plan you keep it, and cancelling any paid plan puts you back on the free plan.

Yeeted is for testing and development, so please don't run anything mission-critical on it yet. While we're in beta, expect occasional downtime, and we may need to reset projects or data. Keep your own copy of anything you can't afford to lose. We can't promise support response times during the beta, but we read every piece of feedback and are happy to help where we can. There is no SLA or uptime guarantee during the beta (see the Terms).

Can Yeeted support see my code, logs or data?

Only if you allow it. On Profile, under Data access, you choose whether Yeeted staff may see your code, data, logs and metrics, and why: not at all (the default), for support only, or also to improve the platform for your stack. If you ask for help with a problem in your app, we may need you to allow the relevant one first, and our tools will tell us which. You can change it at any time and it takes effect immediately. Running your apps, and showing you your own logs and metrics, is not affected. See the Privacy Policy.

Do I need an API key?

No - API keys don't exist on Yeeted. Interactive agents authorize through OAuth in the browser (no credentials to copy). For CI jobs and scripts, create an OAuth credential (client id + secret) on the Connect agent page; secrets are shown once, at creation.

Can my app have a database?

Yes - just ask: "Deploy this app with a Postgres database attached." Postgres, MySQL, MariaDB, MongoDB, and Redis are supported. The connection URL is injected into your app's environment automatically; credentials live in the secrets vault, and you can export a dump of your data any time.

Why did my development app stop?

Development apps stop 15 minutes after each deploy or wake (traffic does not extend the timer), and their databases stop once no app is using them. Both start again on the next deploy or request. Production apps (Small Business and up) are kept always-on, restarted on crash, and load-balanced across servers.

How do rollbacks work?

Yeeted retains recent app images and images protected by named checkpoints. Ask your agent to roll back by a retained git hash or checkpoint name. A git-hash or previous-image rollback restores app code only; database changes are not automatically rolled back. On plans with database snapshots, 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.

Can I use my own domain?

Yes. Add domain: yourdomain.com to your project's yeeted.yaml and deploy, then finish setup on the Domains page — it shows you exactly what to point where, and Yeeted obtains and renews a free Let's Encrypt TLS certificate automatically once your DNS points at us.

Where does my data live?

Your account is homed to a geographic area at signup (e.g. US or EU), and everything you deploy — apps, databases, logs — stays inside it. Data is never moved or replicated across areas. EU hosting isn't available yet, so an account that chooses Europe at signup is hosted in North America, after you acknowledge that. You can download everything we hold about you from your account settings, and closing your account permanently erases your personal data after a 30-day grace window.

How do I revoke an agent's access?

Connect agent page → find the client → revoke. The agent loses access immediately for new tokens; in-flight sessions end within a minute. Re-connecting later just repeats the one-time browser approval.

Something's broken — where do I look?

Start with your app's logs and build output on the dashboard (your agent can also fetch them — ask "show me the logs for my app"). Build failures include the compiler or tooling error verbatim. If a deploy sits in "deploying", the build log usually says why.

Still stuck? Ask your agent — it can read your deploy status, logs, and build errors directly. This is a research preview: things move fast, and your data may be reset between releases.