Documentation Index
Fetch the complete documentation index at: https://docs.cubby.pro/llms.txt
Use this file to discover all available pages before exploring further.
Choose your path
Cubby is intentionally small: install the CLI, connect an app, deploy it, and share the URL. The best first steps depend on what you are trying to ship.AI coders
Use Codex, Claude, Cursor, or another agent. Paste one prompt and it installs the CLI, runs
cubby init, reads the generated rules, and deploys.Rapid prototypes
Start from
cubby init, deploy early, and iterate in public or with a small invite-only group.Database-backed apps
The default template is SQLite; choose Neon Postgres when you need Postgres. Both come with Prisma wired up.
Shared tools
Invite collaborators, manage access, and let Cubby handle authentication around the app.
If you are using an AI coding assistant
You do not need a working local app first — let the agent scaffold one. Paste the Expert from paste prompt into Codex, Claude, or Cursor and it will install the CLI, log in, runcubby init with the right template, read the
generated CUBBY.md / AGENTS.md / CLAUDE.md, ask you about local dev, then
cubby check and cubby deploy.
Per-agent detail:
- Expert from paste — the agent-neutral prompt
- Using Cubby with Codex
- Using Cubby with Claude — adds an optional MCP path
- Using Cubby with Cursor
If you are bringing an existing app
Use Cubby when your app can run as a web process and expose a health endpoint. Before deploying, confirm:- The app has a deterministic build command.
- The app listens on the port Cubby provides.
- Required environment variables are documented.
- Secrets are configured through Cubby, not committed to git.
- The app has a route you can use to confirm it is live after deploy.
After your first deploy
- Share the app with teammates or friends: Sharing
- Make it feel native on phones and desktops: PWA support
- Understand authentication boundaries: Authentication
- Estimate plan limits and costs: Billing