Deploy
Database
Use the bundled Postgres, or a free Neon or Supabase project, and what Knotworking handles for you.
Options
Knotworking runs on PostgreSQL. Every option below is free for a test project or a small team, and you switch between them by changing DATABASE_URL.
| Option | Best for | Setup |
|---|---|---|
| Bundled Postgres | A self-hosted installation | Nothing: it's in the Compose stack |
| Neon | A hosted database that scales to zero | Copy the pooled connection string |
| Supabase | The same, if you already use Supabase | Copy the transaction pooler string |
| PGlite | Local development and demos | Leave DATABASE_URL unset |
A hosted database
Set the pooled string as DATABASE_URL, and a direct (non-pooled) string as MIGRATE_DATABASE_URL, which is more reliable for schema changes.
DATABASE_URL=postgresql://USER:PASSWORD@ep-xxx-pooler.REGION.aws.neon.tech/neondb?sslmode=require
MIGRATE_DATABASE_URL=postgresql://USER:PASSWORD@ep-xxx.REGION.aws.neon.tech/neondb?sslmode=require
On Supabase, use the pooler host for both: the transaction pooler (port 6543) for DATABASE_URL and the session pooler (port 5432) for migrations. The free plan's direct host is IPv6-only, which most networks can't reach.
With a hosted database the bundled db container still starts, and POSTGRES_PASSWORD is still required, but nothing uses it.
First run
A hosted database starts empty, and the API's first-run setup link creates your workspace and owner, as in the quickstart.
Connection handling
- Prepared statements are turned off automatically behind transaction-mode poolers. Override with
DATABASE_POOLED. ?sslmode=requireturns on TLS.- Neon's
channel_bindingparameter is removed for you. DATABASE_POOL_SIZEsets connections per API process (default 10). Keep it low on free tiers.- Migrations are plain SQL and run on any Postgres 14 or later.