Provider · Database

Neon — Ashlr Stack Provider

Neon: Serverless Postgres. Creates a project and pools the connection string. Wire it into your project with one command via Ashlr Stack.

Database · PAT

Neon — Serverless Postgres. Creates a project and pools the connection string.

Dashboard ↗

One command

Add Neon to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add neon

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "serverless postgres for a B2B SaaS"

Auth flow

Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Paste a personal API key from https://console.neon.tech/app/settings/api-keys.

Secret slots

stack add neon writes these 2 secret slots into your Phantom vault:

NEON_API_KEY
DATABASE_URL

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

MCP wiring

Neon ships an MCP server. stack add neon auto-wires it into .mcp.json so your Claude Code / Cursor / Windsurf session can use it immediately.

@neondatabase/mcp-server-neon with NEON_API_KEY piped from Phantom — branch, migrate, and query from the agent.

Starter templates that include Neon

Apply a pre-wired stack with one command:

stack init --template nextjs-neon-vercel-sentry

Supabase — Postgres + Auth + Storage. Full upstream provisioning via the Management API.
Turso — Edge SQLite (libSQL). Creates a database in your default org.
Convex — Reactive backend-as-a-service. Deploy key stored in Phantom.
Upstash — Serverless Redis + Kafka. Management token stored in Phantom.
Firebase — Realtime DB + Auth. Service-account JSON stored verbatim in Phantom.

FAQ

Do I need a Neon account to use it with Stack?

Yes — Stack provisions Neon on your behalf, but it authenticates as you. Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://console.neon.tech and paste it once.

Where does Stack store my Neon credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (NEON_API_KEY, DATABASE_URL) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove neon` to pull the Neon service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Neon credentials in their dashboard — https://console.neon.tech — and Stack's next `doctor --fix` will pick up the new values.