Use your own database
Keep your app’s data on your own PostgreSQL server, self-hosted or in the cloud, for development, live data or both, and move back to Craftkite whenever you like.
Updated October 12, 2026
By default Craftkite runs a managed PostgreSQL database for your app: backed up every day, kept in your data region, nothing to set up. On plans that include it (see Pricing) you can use your own PostgreSQL server instead, for example a server in your company or a managed cloud database.

Before you start
- PostgreSQL 12 or newer, reachable from the internet (private addresses such as 10.x or 192.168.x are refused on Craftkite’s cloud).
- A database and a user that may create tables in its
publicschema. An empty database is best. - The connection details: host, port, database, user and password, or a connection string (
postgresql://…).
Steps
- Open Database → Server.
- Under Development data or Live data, click Use my own server.
- Enter the fields or paste the connection string. Choose the encryption: Verify certificate and host name suits most cloud databases; paste your provider’s certificate authority (PEM) if it is not a public one.
- Click Test connection. You see the time it took, the PostgreSQL version and whether tables can be created. Nothing is left behind by the test.
- Leave Copy the current data there on to take your data (members included) with you, then click Connect. The copy runs in the background.
- For live data, publish the app afterwards: the live app moves to your server with that publish.
The password and certificate are encrypted and never shown again; they are never given to the AI. To change them, click Change connection; leave the password empty to keep the saved one.
Publishing on your own server
Your app’s tables are created on your server with the same safe publishing as on Craftkite: every live schema change is shown first, a change that loses data waits for your confirmation, and Craftkite backs up your data before applying it when it can be read. If that backup is not possible (for example the data is too large), the publish goes on and the change is marked with a warning; keep your own server’s backups switched on.
Data residency
On your own server, where the data is stored, who can reach it, its backups and compliance (GDPR, KVKK) are your responsibility. Craftkite still never shows your data to its staff.
Going back to Craftkite
Click Back to Craftkite and keep Copy the data from my server on. Craftkite backs up its earlier copy, replaces it with your data and switches the app when the copy is done. Your server and its data stay as they are. Publish again to move the live app.
