Getting Started
FASTBASE takes a project folder and makes it live. It works out the framework, the runtime, whether a database or storage is needed, and which settings are missing — then builds, starts, health-checks and serves the app on its own address.
You do not write a Dockerfile, create a database, issue a certificate or configure a proxy.
The fastest path
In your project folder:
fastbase login
fastbase deploy
FASTBASE
Analyzing project...
✓ Next.js
✓ PostgreSQL required
✓ PostgreSQL database created.
✓ Generated secrets: SESSION_SECRET.
✓ Build finished in 41s.
✓ Migrations applied.
LIVE
https://myproject.<your-fastbase-domain>
Other ways to deploy
| Method | When to use it |
|---|---|
| Upload folder / ZIP | In the dashboard: New project. Nothing to install. |
| CLI | fastbase deploy from a terminal or a script. |
| Claude Code, Cursor, Codex | Add the MCP server and say “Publish this project”. |
| GitHub | Connect a repository and deploy a branch. See GitHub. |
| API | One HTTP request with a ZIP body. See API. |
What FASTBASE understands today
| Project type | How it runs |
|---|---|
| Next.js | Built, then next start (or static hosting for output: "export") |
| Vite, Create React App | Built, served as a single-page app |
| Node.js, Express, Fastify, NestJS | Installed, built if there is a build script, started |
| Static HTML | Served directly |
| Dockerfile only | Needs the Docker compute provider — see Troubleshooting |
Nuxt, SvelteKit, Astro, Python, Go, PHP and Ruby are not detected yet.
Simple first, Advanced when needed
The dashboard shows Database: Healthy, not connection pools. Every page with more to show has an Advanced toggle: build commands, the SQL editor, connection details and raw logs live there.
Next steps
- Deploy your first app
- Environment variables — what FASTBASE manages and what you provide
- SDK — auth, data, storage and realtime from your code