# Frequently asked questions

The Markdown copy of <https://yeeted.ai/docs/faq.html>.

### Do I need to know how to use a server or Docker?

For supported source layouts, your agent can deploy without a Dockerfile. Yeeted auto-detects common stacks;
unrecognized layouts need a Dockerfile. An optional `yeeted.yaml` configures runtime settings,
but does not add support for an unrecognized stack.

### Which AI agents work with Yeeted?

Any MCP-compatible agent: Claude, Cursor, and others. Paste the connection URL from
[Getting started](https://yeeted.ai/docs/getting-started.md) and you're set.

### Can I roll back?

Yes. Ask your agent to restore a retained app image by git hash or named checkpoint, or redeploy a previous build from the dashboard. A plain image or git-hash rollback does not automatically roll back database changes. A named production checkpoint with a captured database snapshot can also restore supported production data except Redis on plans with snapshots if the restore succeeds. Check the rollback result.

### Can I take my code and data somewhere else?

Always. Download your source as a tar.gz from the Projects tab or clone it with git, export any database except Redis as a standard dump
file, or keep a live mirror of your database on your own infrastructure (Small Business and up, after the beta; not Redis). No exit
permission required.

### Can support see my secrets or passwords?

No one can see secret values or passwords - they're write-only, for everyone. Support can see which
secret *names* exist to help you debug, and anything support does shows up in your Activity feed.

### Can real users hit my app?

Yes. Promote to production and share your `prod.yeeted.ai` URL: it always serves your
production deployment.

[Get started](https://dashboard.yeeted.ai/signup)
[Back to home](https://yeeted.ai/)