Documentation
Build with confidence from your first connection.
Practical guidance for creating a database, selecting a cloud region, funding a wallet, retrieving connection details, monitoring infrastructure, and integrating the SaveOn API.
Start with the account workflow
Create an account, verify your email, and fund the wallet using an instant deposit secured by Kora or a manual deposit through a configured digital bank. The billing record and transaction state remain visible in the account.
Connect an application safely
Use the database workspace to reveal connection details only when needed. PostgreSQL clients usually take a host, port, database name, user, password, and SSL configuration. Store these values in server-side environment variables and use a connection pool appropriate for your application.
Operate the database after creation
Use the workspace to inspect current service state, endpoint information, cloud region, reservation status, and provider-backed monitoring signals. Build a small operational routine around backups, migrations, connection limits, and renewal warnings rather than waiting for an incident.
Troubleshooting guide
If a connection fails, check the database status, endpoint state, credentials, network restrictions, and recent application changes. If provisioning fails, check verification status, wallet balance, package allowance, selected region, and the transaction state. Never retry destructive actions without checking whether the first request completed.
API and integration resources
The developer portal documents the current v1 API paths, authentication headers, request bodies, response examples, error statuses, API-key lifecycle, and secure integration patterns. Keep your API key on a trusted server and use separate keys for development and production.
Frequently asked questions
Which languages can connect to a PostgreSQL database?
Any language with a maintained PostgreSQL driver can connect. Use the driver’s standard environment-variable and SSL configuration patterns.
How do I prepare for a migration?
Test an export and restore before it is urgent, record schema and extension requirements, and maintain a rollback plan for production changes.
Where should API keys live?
On a trusted server or deployment secret manager, never in browser code, public repositories, screenshots, or support tickets.
Continue exploring SaveOn
Choose the next resource for your project, from practical documentation to pricing, security, and support.