Running on Vercel

Hypercube runs well on Vercel: it is a single Next.js app, and the instance database can live on any managed Postgres (Supabase, Neon, and similar).

Setup

1. Import the repository into Vercel and set Root Directory to apps/console.
2. Add DATABASE_URL and BETTER_AUTH_SECRET as environment variables.
3. Deploy, then visit /signup. The first account becomes the admin.

Migrations run automatically on boot; an empty database is fine. With the Git integration set up, pushes to main deploy automatically.

Choosing the connection string

• Use a transaction-mode pooler: serverless runs many concurrent instances, each with its own connection pool. On Supabase that is the Transaction Pooler (port 6543). Session mode gives every client a dedicated slot and concurrent instances exhaust its pool_size cap.
• Use an endpoint reachable over IPv4. Vercel functions cannot reach IPv6-only hosts such as Supabase's direct db.<ref>.supabase.co address — connections fail with ENOTFOUND.

The same applies to databases you connect as dynamic resources: give Hypercube pooled, IPv4-reachable connection strings.