Database Detail
Database overview, connection strings, roles management, and scaling configuration
Overview
The database overview page displays real-time status, usage metrics, and connection information.
Status and metadata
- Database name: Instance identifier
- Health status: Healthy/Unhealthy indicator
- Engine: PostgreSQL version (e.g., PostgreSQL 17)
- Region: Deployment location
Usage metrics
Three metric tiles display current billing period consumption:
| Metric | Unit | Description |
|---|---|---|
| Compute | CU-hrs | Total compute time consumed |
| Storage | GB | Current storage usage |
| Network Transfer | GB | Data egress volume |
Configuration
| Property | Description |
|---|---|
| Compute | Current CU range (min — max) with vCPU/RAM tooltip |
| Region | Deployment region |
| Engine | PostgreSQL version |
| Created | Database creation timestamp |
| Maintenance Window | Scheduled maintenance window (day, time UTC) |
Connection strings
Generate connection strings by selecting a role and database from the dropdowns.
Connection URL format
postgresql://[role]:[password]@[host]/[database]?sslmode=requireComponents:
role: Database role/user namepassword: Role password (masked by default)host: Neon endpoint hostnamedatabase: Logical database namesslmode=require: SSL is mandatory
Output formats
Toggle between formats using the content switcher:
psql (Connection URL):
postgresql://neondb_owner:****@ep-xxx.region.aws.neon.tech/neondb?sslmode=requireParameters (Environment Variables):
PGHOST='ep-xxx.region.aws.neon.tech'
PGDATABASE='neondb'
PGUSER='neondb_owner'
PGPASSWORD='****'
PGSSLMODE='require'Next.js (.env.local):
DATABASE_URL="postgresql://neondb_owner:****@ep-xxx.region.aws.neon.tech/neondb?sslmode=require".NET (appsettings.json):
{
"ConnectionStrings": {
"DefaultConnection": "Host=ep-xxx.region.aws.neon.tech; Database=neondb; Username=neondb_owner; Password=****; SSL Mode=Require;"
}
}Java (JDBC URL):
jdbc:postgresql://ep-xxx.region.aws.neon.tech/neondb?user=neondb_owner&password=****&sslmode=requirePassword visibility
- Click the eye icon to reveal/hide the password
- Click the copy icon to copy the full connection string (with password)
Access & Databases
Manage PostgreSQL roles and logical databases within your instance.
Roles
Roles control database authentication and permissions.
| Column | Description |
|---|---|
| Name | Role identifier |
| Status | Protected (system) or Custom (user-created) |
| Created | Creation timestamp |
Create role:
- Click Create Role
- Enter role name (2–63 chars, lowercase, alphanumeric + hyphens)
- Must start with a letter
Delete role:
- Click overflow menu → Delete
- Protected roles (e.g.,
neondb_owner) cannot be deleted - Roles owning databases must have those databases deleted first
Databases
Logical databases within the PostgreSQL instance.
| Column | Description |
|---|---|
| Name | Database identifier |
| Owner | Role that owns the database |
| Created | Creation timestamp |
Create database:
- Click Create Database
- Enter database name (2–63 chars, lowercase, alphanumeric + hyphens)
- Select owner role from dropdown
Delete database:
- Click overflow menu → Delete
- Type the database name to confirm (destructive action)
Settings
Scale
Configure compute autoscaling and idle behavior.
Compute Units (CU)
Allowed values:
0.25, 0.5, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56Step increments:
- 0.25 → 16: step of 1
- 18 → 56: step of 2
Configuration:
| Setting | Description |
|---|---|
| Min CU | Baseline compute when active but idle |
| Max CU | Maximum compute under load |
RAM allocation: Each CU provides 4 GB of RAM.
| CU | RAM | Use case |
|---|---|---|
| 0.25 | 1 GB | Development, testing |
| 1 | 4 GB | Small production workloads |
| 4 | 16 GB | Medium production workloads |
| 8 | 32 GB | Large production workloads |
| 16+ | 64+ GB | High-performance requirements |
Constraint: Max CU cannot be less than Min CU.
Suspend timeout
Configure how long the database waits before suspending after inactivity:
| Option | Description |
|---|---|
| Never | Always running, no cold start, continuous cost |
| 1 minute | Quick suspend, frequent cold starts |
| 5 minutes | Recommended balance |
| 10 minutes | Moderate delay |
| 30 minutes | Extended sessions |
| 1 hour | Long-running applications |
Cold start latency: ~500ms on first connection after suspend.
Network
Network settings control database accessibility. Available on Enterprise plans.
Visibility
| Setting | Description |
|---|---|
| Public Access | Database accessible via public endpoint |
| Internal Access | Database accessible from cluster services |
Disable public access to restrict connections to internal services only.
IP Whitelist
When enabled, only specified IP addresses can connect.
Supported formats:
- IPv4:
192.168.1.100 - IPv6:
2001:db8::1 - CIDR:
192.168.1.0/24,10.0.0.0/8
Actions:
- Add IP/CIDR to whitelist
- Remove IP from whitelist
Danger zone
Delete database instance
Permanently removes the entire database instance including:
- All roles
- All logical databases
- All data
Deletion process:
- Navigate to database settings
- Click Delete Database Instance
- Type the database name to confirm
- Click Delete
This action is irreversible and cannot be undone.
Activity
The activity table shows recent events for the database:
| Column | Description |
|---|---|
| Date | Event timestamp |
| Action | Event description |
| Resource | Affected entity |
Features:
- Search events by keyword
- Paginate through history (5, 10, 20 items per page)
- Sort by any column