Clusterward creates Scaleway database instances without a public endpoint, sets up a dedicated database with its own role and password for each service, and backs up every database before it is deleted.
A managed database is a Scaleway RDB instance for managed PostgreSQL or MySQL that Clusterward creates in your project and manages via the Scaleway API. The instance is attached exclusively to the cluster’s private network; a public endpoint is never created. On the instance, Clusterward creates one database per service with its own owner role and, on request, additional login users with graded privileges. Databases, users and privileges remain visible in the Scaleway console because Clusterward takes no side routes via SQL.
Choose engine, name and network; the instance is created with a private endpoint only.
On the service page: name derived from the domain, role and password included.
The database is assigned to the service immediately; nothing is left half-created.
Copy the connection details and DATABASE_URL in the cockpit and set them as variables.
Additional users, import, metrics and backups on the instance page.
Everything between “instance created” and “application connected” is handled by the cockpit.
The instance gets an endpoint in the Private Network only. Applications in the cluster can reach it, the internet cannot.
Name, role and password are derived from the service’s first domain and stored once. Renaming the service later changes nothing about the database.
A read user for BI or backups, a write user for a worker. Privileges are revoked first, then granted, and also apply to tables the app creates later.
Copy schema and data from an external Postgres or MySQL source into a database on the instance. The application is paused meanwhile, and a non-empty target asks before proceeding.
When a tenant is offboarded, every database is backed up first and uploaded to your bucket. Without a secured dump, nothing is deleted.
The instance’s CPU, connections and memory live from Scaleway Cockpit, without opening the console.
When the last automatic snapshot ran, how often it runs and how long it is kept – configurable in the cockpit. You can start a backup of a single database at any time.
A backup is prepared for download and fetched via a short-lived link, as a compressed SQL file.
A backup is restored into a new database with its own user and password. You switch over when you are ready; the old one stays until you delete it.
Instances, databases, users and privileges via the RDB API, visible in the console.
Dumps in pg_dump format, restore with pg_restore.
Dumps as SQL, restore with the mysql client.
Instance and cluster in the same network, no public route.
Whether an order arrived or which value a setting holds: the SQL console answers it in the browser. It connects with its own read-only login, runs every query in a read-only transaction and writes it to the audit log. On the instance page, ⋯ → “Query data” opens it with the database already selected.
There is deliberately no instance-admin level. A leaked application password never reaches beyond its own database.
| Level | May | Typical use |
|---|---|---|
| read | Read all tables, including future ones | BI tools, reporting, backups |
| readwrite | Read and write | Worker, second application |
| all | All privileges within the database | Migration tools |
| Owner role | Owner of the database | The application itself |
The instance is attached to the private network created during Cluster provisioning. The connection details go into the service’s encrypted variables, as described under Deployments.
In a pipeline, the database building block creates a dedicated database for each tenant and hands host, user and password to the workload only at runtime, see Tenant pipelines.
All the ways back – database, volume, earlier version – are brought together in Backups & recovery.
Kapsule clusters secure by default, with Private Network and gateway.
Go to Cluster provisioningCustomer onboarding from building blocks, live in under a minute.
Go to Tenant pipelinesPersistent data with a snapshot before every deletion.
Go to Volumes & snapshotsCan’t find your question? Write to us – we usually reply on the same business day.
Ask a questionWe create a private instance and a database for your service, and connect the application – in just a few minutes.
