Quickstart
The Quickstart is the fastest way to try NocoDB locally. One command downloads the installer and makes a Compose stack (NocoDB, a worker, Postgres and Redis). Then it starts the stack on http://localhost:8080. It works on Mac, Windows and Linux.
Before you begin
You need Docker Desktop (Mac/Windows) or Docker Engine (Linux). Install it from docker.com before you run the command below.
1. Run
curl -fsSL https://install.nocodb.com/noco.sh | bash -s -- --quickThis command writes a ready-to-run stack into nocodb/ and starts it. The first run pulls the images, so it can take a few minutes.
2. Open NocoDB
- Open http://localhost:8080.
- Sign up with an email and password. The first user becomes super admin.
What this runs
| Container | Image | Purpose |
|---|---|---|
nocodb | nocodb/nocodb:latest | The web app and API |
worker | nocodb/nocodb:latest | Background jobs (imports, exports, automations) |
db | PostgreSQL | Stores metadata and your data |
redis | Redis | Caching and job queue |
Docker keeps the data in named volumes (postgres_data, redis_data, nocodb_data). The data stays after restarts and after docker compose down. To list the volumes, run docker volume ls.
Common operations
The installer writes all files into nocodb/. Run these commands from that directory:
cd nocodb
# Tail logs
docker compose logs -f nocodb
# Stop everything (keeps your data)
docker compose down
# Start again
docker compose up -d
# Update to the latest version
docker compose pull && docker compose up -dPrefer not to run a script?
Get the same four-container stack from the quickstart-demo example on GitHub. It is a plain Compose file that you can read before you run it.
- Copy its
docker-compose.ymlinto an empty directory. - Start it:
docker compose up -dIt is the same stack, without the installer. Run the operations above from that directory.
Next steps
- Deploying to a server? Refer to Single-server install. It uses the same single command, and adds automatic Traefik + Let's Encrypt SSL.
- Need managed Postgres, custom SSL, or your own infrastructure? For example configurations, refer to Custom infrastructure.
- Want enterprise features? Purchase a license, then activate it.
- Something not working? For startup, network, SSL and attachment problems, refer to Troubleshooting.
Last updated on