Lakebase Postgres

Local Scope and Authorization

Use existing authorized Neon connections and the user's supplied DATABASE_URL or linked .neon project first. Do not create a second project, replace an ORM, install a CLI, or start an authentication flow merely because this skill was loaded. Use tools actually available in the current host; optional neon, neon-auth, and branch skills are separate capabilities, not assumed installed dependencies. Installer commands below are examples only for an explicitly requested setup.

Lakebase Postgres is the database at the core of Neon. It runs on the lakebase architecture — OLTP built directly on cloud object storage — which decouples storage from compute to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.

It is the same database whether you reach it through Neon or through Databricks; this skill covers the Neon access path.

Login, users, sessions, and @neondatabase/auth belong in neon-auth.

Setup Flow

1. Select the organization and project

If a DATABASE_URL is already supplied (prompt, environment, or repo) or a .neon file points at a project, use it. Do not list organizations or create a second project for schema work.