Skip to main content
Use your own Neon account for PostgreSQL projects. Neon bills you directly and applies its own quotas. Workspace Connections protects your provider key; the separately installed Neon database plugin attaches existing databases to a Spitzli Cloud project. Saving a key alone does not install the plugin or attach a database. You need workspace owner or administrator access, or authorized platform operator access. Read-only customer preview cannot change the connection or refresh provider inventory.
1

Create a Neon project and key

In your Neon account, create or select the project you need. Create a dedicated API key with the narrowest suitable scope. For a project-scoped key, keep its exact Neon project ID.
2

Open Connections

In Console, select the workspace and open Connections.
3

Connect the key

Enter the key in Neon API key. For a project-scoped key, also fill Neon project ID (optional) with that project’s exact ID. Account or organization keys can leave the project ID blank to list their available projects. Fill Organization ID (optional) if you need to restrict that inventory to an organization. Select Connect Neon.
4

Read your inventory

Select Refresh projects. Check the project name, ID and region. Use Next project page if available. Seeing a project here confirms inventory access, not database deployment or application readiness.
The key is stored encrypted on the server and is never displayed again. The form clears it after every submission. Enter provider credentials only in the protected form.

​
Attach a database to a project

An operator must install the reviewed Neon plugin and enable Connect Neon databases for your workspace. If that option is missing, ask your operator to check the installation and your plan’s resource limit.
  1. Create or select a Neon project in Frankfurt, Germany (aws-eu-central-1). Other regions can appear in inventory but cannot be attached in this release.
  2. Open your Spitzli Cloud project and choose the Neon database offering.
  3. Enter a display name, then select the Neon project, branch, database, role and endpoint. Select Connect database.
  4. Review Connection settings and Neon branches. The compute state comes from Neon; an idle endpoint is not reported as a healthy running application.
Workspace owners, administrators and authorized operators can browse provider inventory and manage attachments. Read-only customer preview can see permitted settings without provider-wide inventory or credential controls. Ordinary workspace members do not gain Neon actions merely because the plugin is installed: the existing database-management permission remains required.

​
Use connection credentials

Reveal URI requires write access. Choose pooled or direct mode before revealing. The URI starts hidden, stays outside shared Console caches, and disappears after one minute, when the tab is hidden, or when you leave the resource. Copy does not extend that time. Paste credentials only into the application’s protected server-side environment configuration. This release does not run SQL, create paid Neon capacity, change branches, or automatically inject credentials into application deployments. Neon Auth, Storage, Realtime, Functions and AI Gateway are future capabilities, not actions provided by this database plugin. Plugin actions currently require a browser session; automation through API tokens or MCP is not supported for this release.

​
Detach an attachment

Use Detach database, then review Confirm detach. This removes the local Spitzli Cloud attachment and releases its resource allocation. It does not delete the Neon project, database or role, revoke a provider key, or stop provider charges. Detach remains available to an authorized administrator if provider inventory is unavailable or new attachments have been disabled.

​
Optional: use the Neon CLI

You can create a project key with the official Neon CLI on your own computer:
The localhost login callback belongs to that same computer. Use the same project ID in Console and paste only the resulting project API key into the protected form. Do not upload credentials.json or share login callback URLs or codes. Spitzli Cloud does not run this login for you or provide a hosted Neon OAuth connection.

​
Replace a key or recover a failed request

Use Replace connection key to submit a replacement. If Console reports an uncertain result, follow Retry same connection with the same key and project scope. If another administrator changed the connection, review the refreshed status first. An invalid or revoked key, insufficient scope or Neon outage can prevent inventory access. Check the key and project ID, then refresh. Spitzli Cloud does not fall back to a platform provider key or allocate paid capacity automatically.

​
Disconnect

In Workspace Connections, select Disconnect Neon, review the confirmation and select Confirm disconnect. This removes the Spitzli Cloud connection’s stored key; attached resources cannot make new provider requests until an authorized connection is restored. Your Neon projects and data remain intact. Revoke the key separately in Neon when it should no longer work elsewhere.