Skip to main content
Pxxl databases run outside your application container and are ready for your deployed services to use. Choose an engine, connect it through environment variables, then use the database workspace to monitor, visualise, back up, and manage the instance. Open Database in the Pxxl workspace to see your instances.

​
Supported engines

The engines and advanced tools available to you depend on your plan. PostgreSQL and MySQL are available on the Free plan.

​
Create a database

1

Choose an engine

Select the database type that matches your application. The engine sets the connection format and default port.
2

Name the instance

Use a name that describes the workload, such as orders-production or analytics.
3

Choose backup protection

Turn on daily encrypted backups when the database needs recovery points. You can keep them in Pxxl-managed storage or use a custom S3-compatible destination.
4

Wait for a healthy status

A new instance is not ready while it is provisioning. Connect the application after the database shows a healthy or running status.

​
Database workspace

Connection

Get the host, port, user, password, and database URL your application needs.

Monitoring

Check health, connections, storage, transfer, latency, and resource usage.

Visualise

Inspect tables, columns, keys, relationships, and database structure.

Backups

Create recovery points, choose a destination, download, restore, or delete them.

Settings

Manage resources, networking, ownership, and database lifecycle actions.

​
Connect a project

There are two parts to connecting a database:
  1. Link the database to the project so the resources are visible together.
  2. Add the connection values to the project’s environment variables so the runtime can connect.
When you create a database from a project, enable Add DATABASE_URL to save the generated URL to the project’s global environment variables. Redeploy after changing environment values because a running container does not reload them.

​
API

The Database API can create instances, read metadata, inspect metrics, and control the database from a server-side workflow. Keep the API key on the server and grant only the database access it needs.

​
Where to go next

  • Start with Connection when an application needs database credentials.
  • Open Monitoring when a workload is slow or unhealthy.
  • Read Backups before enabling recovery protection.