Introducing Databases as a Service on Clever Cloud

French version below

server

Another kind of ‘external’ DBs

Until now, databases hosted on Clever Cloud were only available from within the hosted apps. Since it was impossible to use external DB management software, it was a bit cumbersome to import or export data.

This era is over: right now, the services are available from outside!

Indeed, it means you will be able to use your favorite DB management tool. If you want to use our platform simply for host a database or if you have to access to your db for initial setup or migration, you can.
It also means you can use Clever Cloud as a pure Database as a Service (DBaaS) provider.

The current form (only available from within Clever Cloud apps) is
"dbname.engine.internal" (eg "customers.my.internal").

The new domain names will follow this pattern:
"dbname.engine.clvrcld.net" (eg "customers.mysql.clvrcld.net").

As for the ports, they stay the same (3306 for MySQL, 5432 for PostgreSQL).

Old domain names remain active for now (no sunset date is planned yet), but we strongly encourage you to make the switch.

We will indicate a date for the end of the internal databases services later.

The support remains at your service to help you tomigrate from .internal to clvrcld.net in your code.

Don't hesitate ton contact the support for more precisions 😉


Version française

Lancement des Databases as a Service sur Clever Cloud

Jusqu'ici les bases de données hébergées dans Clever Cloud n'étaient utilisables que depuis l'application hébergée. Il était alors impossible d'utiliser un outil de gestion de base de données externe, ce qui était fastidieux notamment pour les imports/exports.

Cette ère est révolue: désormais, les services sont accessible depuis l'extérieur !

Concrètement, cela signifie qu'il sera possible d'utiliser l'outil de management de votre choix. Si vous souhaitez utiliser notre plateforme uniquement pour héberger une base de données ou si vous devez accéder à votre base depuis l’extérieur pour l'amorçage ou la migration de vos données, c'est désormais possible.
Clever Cloud devient donc aussi fournisseur Database as a Service (DBaaS) !

La forme actuelle (seulement accessible depuis les applications Clever Cloud) est:
"dbname.engine.internal" (ex "clients.my.internal").

Les nouveaux noms de domaine adopteront désormais cette forme:
"dbname.engine.clvrcld.net" (ex "clients.mysql.clvrcld.net").

En ce qui concerne les ports, ils restent les même (3306 for MySQL, 5432 for PostgreSQL).

Nous préciserons une date de fin des services des bases de données internes ultérieurement.

Le support reste à votre service pour vous aider à migrer de .internal vers le clvrcld.net dans votre code.

N'hésitez pas à contacter le support pour plus de précisions 😉

Blog

À lire également

UP Program: Clever Cloud announces its fifth startup selection

With this new batch, Clever Cloud welcomes four startups to the UP Program: Sentibee, Pictaderm, Legaia and Cockpit Agriculture.
Company

Sōzu 2.0 — turning a reverse proxy into a programmable edge

Sōzu is the reverse proxy that sits in front of every application running on Clever Cloud. After eighteen months of work — first the HTTP/2 multiplexer, built on our existing kawa pivot, then almost every other layer of the proxy, and finally a long run in production on the cleverapps.io load balancers — Sōzu 2.0 is out.
Engineering

K3s vs K8s: What Are the Differences and Which One Should You Choose in 2026?

Kubernetes has become the standard for container orchestration. But depending on your infrastructure constraints (limited resources, edge computing, IoT, or large-scale enterprise clusters), the distribution you choose can radically change the operational experience. K3s and K8s (upstream Kubernetes) address different needs, even though both share the same CNCF-certified foundation.
Engineering Features