Skip to main content
NocoDB is a self-hosted Airtable alternative — it turns a database into a smart spreadsheet with grid, gallery, kanban, and form views. You manage everything from its web UI, served at your *.suji.fr address. This guide covers configuring NocoDB on Suji. Check the version and release notes shown in the marketplace before installing or upgrading. NocoDB is maintained upstream; Suji provides the marketplace packaging.

​
Before you install

Nothing to prepare. NocoDB stores its data in a local database inside the install, and you’ll create your admin account in the browser on first run.
NocoDB has no generated password and no credentials file — the first person to sign up becomes the super-admin. Create your account immediately after install.

​
Install

Dashboard → Apps → NocoDB → Install: The current template declares 1 GiB minimum and 2 GiB recommended memory, with a 2 GiB container limit. A Small VPS is a starting point if it has enough spare capacity. See Recommended size. Click Deploy. Once the install is running, open its assigned URL, for example https://nocodb-<random>.suji.fr, served over HTTPS through the tunnel.

​
First connection — create your super-admin account

  1. Open the install URL (https://nocodb-<random>.suji.fr).
  2. NocoDB shows a Sign Up screen on first run.
  3. Enter your email and a password. The first account created is the super-admin.
  4. You land in the NocoDB dashboard.
The URL is public the moment the install is running. Until you sign up, anyone who reaches it can claim the super-admin account. Do it right after deploy.
On later visits the URL shows Sign In instead.

​
Build your first base

Inside the dashboard:
  1. Click Create Base (NocoDB’s term for a workspace/database).
  2. Add tables and columns, or import from CSV/Excel.
  3. Switch between Grid, Gallery, Kanban, and Form views.
  4. Invite collaborators from Team & Settings (email features depend on an SMTP provider — not configured by default).
External database connections and advanced features depend on the installed edition and version. Check NocoDB’s documentation before planning around a specific connector or paid feature.

​
Day-to-day management

​
Troubleshooting

Auth tokens are signed with the JWT secret. If it changed, existing sessions are invalidated and everyone has to sign in again — the data itself is untouched.
NocoDB needs an SMTP provider for outbound email, which isn’t configured by default. Use your mail provider’s documented SMTP settings; port 587 with STARTTLS is a common option. Check outbound connectivity from your VPS. Add the SMTP env vars to the install yourself in the install’s Variables tab, then click Apply changes to redeploy.
NocoDB isn’t reachable through the tunnel yet — usually still starting (wait ~30 s, especially after an upgrade). If it persists, the Logs tab shows why the container isn’t up.

​
Where things live

NocoDB keeps its metadata in a local database in /usr/app/data — there’s no separate database container. Uninstalling deletes the volume by default; choose keep data during uninstall to preserve your bases.
  • Allow for the current template’s 1 GiB stated minimum, 2 GiB recommendation and 2 GiB container limit. These do not guarantee capacity for your tables or other apps sharing the VPS.
  • Pressure scales with table size, attachments, and concurrent editors. Large bases or many users → size up.
  • If you run other apps on the same VM, remember the VM’s total CPU/memory is shared.

​
Reporting issues