Skip to content

Neon Postgres

Create a Neon Postgres project and wire its connection string into the OpenQuok CLI auth server.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start for $0

Overview

The OpenQuok CLI auth server (agent/server) stores short-lived OAuth device-flow state in Postgres. Neon is a good managed Postgres option for production deployments (including serverless hosts like Vercel).

Environment variables

  • DATABASE_URL — Neon Postgres connection string (recommended: include `sslmode=require`).

Common setup steps

Create a Neon project

In Neon, create a new project and choose:

  • Postgres version: 16 (matches local dev via `postgres:16-alpine`)
  • A region close to your deployed auth server (Vercel / host region)

Copy the connection string

From Neon’s connection details, copy the Postgres connection string. It should look like:

postgresql://<user>:<password>@<host>/<database>?sslmode=require

If Neon offers multiple strings, prefer a pooled/serverless-friendly option for high concurrency deployments (for example Vercel).

Set DATABASE_URL in production

Copy agent/server/.env.production.example to agent/server/.env.production.local (gitignored), then set:

DATABASE_URL="postgresql://<user>:<password>@<host>/<database>?sslmode=require"

If you deploy on Vercel, you can also set the same key in the Vercel project’s Environment Variables instead of using a local file.

Verify the auth server boots

Once deployed, hit the health check endpoint:

GET /health

On startup, the server will auto-create the device_requests table if it does not exist.

Search documentation
Find a docs page
Discord Support