To deploy a database with Coolify, attach an SSH-capable VPS to Coolify, create a database resource inside a project and environment, verify the generated persistent volume, and start the resource. Coolify acts as the control plane; Docker on the selected server runs the database container. Applications on the same destination should use the generated internal URL, while outside clients require deliberate network exposure, firewall rules and, where supported, TLS.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
The important operational distinction is between persistent storage and backup. A named volume keeps data when a container is recreated, but it does not protect you from disk loss, a damaged host, an operator mistake or an unusable database. Configure database-aware, off-server backups and test restoration before treating the deployment as dependable.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What you need before creating the database
Coolify does not provide the compute or disk for the database. You supply a VPS or another SSH-capable server, and Coolify installs and manages the deployment there. Before opening the database wizard, confirm the following:
- An SSH-reachable server that Coolify can connect to and control.
- Enough CPU, memory and fast disk capacity for the database, its indexes, temporary files and growth.
- A Coolify project and environment in which the resource will live.
- A plan for application connectivity: an internal-only connection, external clients, or both.
- A separate backup destination, preferably an S3-compatible bucket or another location that is not the VPS itself.
- Firewall access limited to the administrators, application networks and clients that genuinely need the service.
The database engine should be selected for the workload and for what the application already supports. A relational schema, a document model, a cache and an analytical column store have different operational requirements; choosing an engine only because it is available in a menu can create compatibility and backup problems later.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Choose the Coolify database engine
Coolify provides one-click resources for the engines below. The listed port is the engine’s default internal port in Coolify. It is not a reason to expose that port publicly; most applications should connect over the private destination network.
| Engine | Best fit | Default internal port | Coolify backup capability |
|---|---|---|---|
| PostgreSQL | Relational applications, transactional data and SQL workloads | 5432 | Scheduled database-aware backups |
| MySQL | Relational applications that require MySQL compatibility | 3306 | Scheduled database-aware backups |
| MariaDB | MySQL-compatible relational workloads | 3306 | Scheduled database-aware backups |
| MongoDB | Document-oriented applications | 27017 | Scheduled database-aware backups |
| Redis | Caches, queues, streams and key-value data | 6379 | Persistent storage, but no standalone scheduled database-backup workflow |
| Dragonfly | Redis-compatible cache and key-value workloads | 6379 | Persistent storage, but no standalone scheduled database-backup workflow |
| KeyDB | Redis-compatible workloads needing that engine’s feature set | 6379 | Persistent storage, but no standalone scheduled database-backup workflow |
| ClickHouse | Analytical and columnar workloads | 9000 | Scheduled database-aware backups |
Redis, Dragonfly and KeyDB can persist their data to disk, but persistent files are not equivalent to a scheduled, database-aware dump and an independently stored copy. If losing the data is unacceptable, design and test a backup method appropriate to the specific engine rather than relying on the volume alone.
Step-by-step: create and start the resource
1. Connect the VPS to Coolify
Add the VPS as a server in Coolify using its SSH connection details. Coolify is the management plane; Docker on that connected server performs the actual container deployment. Check that the server is online and that the destination you intend to use is available before creating the database resource.
2. Open the project and environment
Choose the project and environment where the database belongs. Keeping the database and its application in the intended environment makes network discovery and lifecycle management predictable. Confirm the selected server and destination before proceeding, because the volume and container will be created there.
3. Create a new database resource
- Choose Create New Resource.
- Select the database engine that matches the application’s data model.
- Select the connected server and destination.
- Review the generated database name, user, password, port and other settings before starting.
Coolify generates credentials and configuration values for the resource. Save the credentials in your secret-management process; do not paste them into source control or share them in ordinary chat. If your application expects a particular database name, username or authentication option, reconcile that requirement with the generated values before the first start.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
4. Verify persistent storage before the first start
Open the resource’s Configuration > Persistent Storage section. A generated named volume should be mounted at the data directory expected by the selected image. Do not remove that mount merely to simplify the configuration, and do not change its target path without understanding the image’s storage layout. An incorrect mount can make a populated database appear empty or prevent the container from starting.
Free tools Windows power users keep installed
One-click scans. No signup required.
5. Start the database
Select Start. Creating the resource prepares its configuration; the start operation actually launches the database container. Wait for the container to become healthy, then inspect the resource’s connection information and logs for initialization errors, permission problems or an incompatible configuration.
6. Record the connection details
Keep the generated internal URL, credentials, database name and port with the application’s deployment secrets. Treat the internal URL as the normal application endpoint. It resolves over the Coolify/Docker network when the client runs on the same destination and avoids exposing the database to the public internet.
Persistent storage: how data survives a redeploy
A container is replaceable; the named volume is the durable part of this deployment. Coolify can recreate the container while retaining that volume, so ordinary redeploys, image recreation and container replacement do not have to delete the database files. This protection applies only while the volume remains attached to the same intended data path on the deployment server.
Coolify’s documented default data paths are engine- and version-specific:
Recommended Free Tools
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
| Engine | Expected data path | Qualification |
|---|---|---|
| PostgreSQL | /var/lib/postgresql/data |
PostgreSQL versions before 18 |
| PostgreSQL | /var/lib/postgresql |
PostgreSQL 18 and later |
| MySQL | /var/lib/mysql |
Engine default |
| MariaDB | /var/lib/mysql |
Engine default |
| MongoDB | /data/db and /data/configdb |
Both paths are used by the database image |
| Redis | /data |
Engine default |
| Dragonfly | /data |
Engine default |
| KeyDB | /data |
Engine default |
| ClickHouse | /var/lib/clickhouse |
Engine default |
The PostgreSQL path change is particularly important when selecting an image version. A volume mounted for a pre-18 layout is not automatically correct for PostgreSQL 18 or later. Confirm the image’s documented path and the Coolify-generated mount before changing versions or restoring data.
What a persistent volume does not cover
- Failure or loss of the VPS disk.
- Deletion or corruption of the named volume.
- A bad migration, accidental data deletion or compromised credentials.
- Damage that is replicated to every local copy.
- Recovery if the server itself is unavailable.
Storage is local to the deployment server unless you provide shared storage. Therefore, a volume is a persistence mechanism, not a database-aware backup.
Connect an application to the database
Applications on the same Coolify destination
Use the generated Internal URL in the application’s environment variables. This is the preferred route because traffic remains on the private deployment network. Copy the complete URL or the individual host, port, database, user and password fields exactly as Coolify presents them. After redeploying the application, run an application-level migration or a simple read/write check so that you verify more than network reachability.
Clients outside the destination
External access is an explicit configuration choice, not a side effect of creating the resource. If an administrator, reporting system or remote application must connect:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Configure the database resource with a public port mapping or the documented public-access option.
- Allow that port only from the required source addresses in the VPS and provider firewalls.
- Use strong, unique credentials and rotate any credential that has been exposed.
- Enable SSL/TLS when the database engine and client support it, and validate the certificate rather than disabling verification.
- Test the connection from the real external network, then remove any temporary broad firewall rule.
Do not assume that a mapped port is protected by the VPS firewall. The container, host firewall and provider firewall are separate controls and should be reviewed together.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Backups and restoration
Enable database-aware backups
Configure Coolify’s scheduled database-aware backup feature for PostgreSQL, MySQL, MariaDB, MongoDB and ClickHouse. Send copies to an S3-compatible bucket or another destination separate from the VPS. An off-server copy is what allows recovery when the deployment host, its disk or its local volume is lost.
For Redis, Dragonfly and KeyDB, Coolify provides persistent storage but no standalone scheduled database-backup workflow in the documented database feature. Choose an engine-specific export or snapshot process, store the result away from the VPS and document how it will be restored. A file sitting beside the live data does not satisfy that separation requirement.
Set a recovery policy
- Decide how much recent data the application can afford to lose and schedule backups accordingly.
- Retain multiple restore points so one corrupted or accidentally deleted dump is not the only copy.
- Restrict access to the backup bucket and encrypt data in transit and at rest according to your risk model.
- Record the engine version, database names and credentials or secret references needed for a restore.
- Test a restore on a separate resource instead of assuming that a successful upload means a usable backup.
Restore without overwriting the only copy
- Stop writes from the application or place it in maintenance mode.
- Provision a separate target database resource, preferably with the same engine major version as the backup.
- Restore the dump or export using that engine’s supported restore procedure.
- Check tables or collections, row or document counts, indexes, permissions and application migrations.
- Run representative application reads and writes against the restored target.
- Only after validation, repoint the application and retain the original resource until the rollback window has passed.
The exact export and import command depends on the engine and backup format. Follow that engine’s documented procedure rather than treating a copied data directory as a portable backup.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Health checks and routine operations
Interpret the health status correctly
A Coolify database health check is a Docker readiness or liveness probe. It indicates that the container meets the probe’s condition; it does not prove that application queries work, replication is current, data is logically consistent or a backup can be restored. Investigate application logs and run an authenticated query when you need those stronger assurances.
Recreate a container safely
Container recreation can be normal maintenance when the named volume and its mount remain unchanged. Before confirming a destructive action, verify the resource’s persistent-storage mapping and ensure that a recent off-server backup exists. Never select a new empty volume simply because the existing container is unhealthy; that can hide the real problem and present an empty database to the application.
Handle image and major-version changes
Changing a major database image version is not, by itself, a safe upgrade procedure. Take and verify a backup, read the engine’s upgrade requirements, check data-directory compatibility and follow the supported migration path. Plan downtime or a controlled cutover when the engine requires it. A container that starts after an image change is not proof that the data upgrade was correct.
Choose the VPS and destination deliberately
The database’s reliability depends heavily on the server beneath Coolify. Compare candidate VPS infrastructure using the factors that affect this workload:
- SSH access: Coolify must be able to connect and manage Docker on the server.
- CPU and memory: size for concurrent queries, background jobs, indexes, cache and the application workloads sharing the host.
- Disk performance and capacity: databases are sensitive to latency and sustained write throughput; leave room for growth, temporary files and backups.
- Region: place the database near the application and users that need low latency, while considering jurisdiction and recovery geography.
- Network limits: check transfer quotas and throughput if clients or backup jobs move substantial data.
- Firewall controls: require host- and provider-level rules that can restrict database ports.
- Snapshots: useful as an additional infrastructure recovery measure, but not a substitute for database-aware, independently stored backups.
- Independent backup destination: keep recovery data outside the server whose failure you are planning for.
Coolify’s server model supports VPS and other SSH-capable infrastructure without requiring a particular provider. The appropriate choice depends on your workload, region, storage and recovery requirements.
Troubleshooting common failures
The database starts with no data after a redeploy
First inspect Configuration > Persistent Storage. Confirm that the original named volume is still attached and that its target path matches the image version. An accidentally changed mount, a new volume name or the PostgreSQL pre-18 versus 18-and-later path difference can make an existing installation look empty. Do not initialize the empty instance or delete the old volume until you have identified which volume contains the data.
The container will not start
Check the resource logs for permission errors, invalid environment values, a port conflict, insufficient disk space or an incompatible data directory. Verify that the selected image expects the mounted path and that the server has enough capacity. If the issue followed an image-version change, revert only with a verified backup and follow the engine’s documented downgrade or upgrade rules; do not repeatedly switch tags against the live volume.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe application cannot connect
For an application on the same destination, replace a public hostname with Coolify’s generated internal URL and confirm that both resources are attached to the expected network. Check the database name, user, password and port separately. For an external client, verify the public mapping, both firewall layers and TLS settings, then test from the actual client network rather than from the VPS itself.
The health check is green but requests fail
Run an authenticated application query and inspect application logs. A Docker health probe can pass while credentials, schema migrations, permissions, replication state or application-specific queries are wrong. Treat health status as one signal, not as evidence of data integrity or recoverability.
A backup exists but cannot be restored
Test the restore procedure on an isolated target and record the failure. Confirm that the dump is complete, the target engine version and extensions are compatible, and that required users, permissions and indexes are recreated. Update the backup process only after a full restore test succeeds; a file that cannot produce a working database is not a usable recovery point.
Quick Recap
Production readiness checklist
- The VPS is connected through SSH and the correct server and destination are selected.
- The engine matches the application’s data model and compatibility requirements.
- Generated credentials are stored securely and are not committed to source control.
- The named volume is mounted at the image’s documented data path.
- The application uses the internal URL unless external access is genuinely required.
- Any public port is restricted by VPS and provider firewall rules and protected with TLS where supported.
- Database-aware backups, or an engine-specific export process for Redis-compatible engines, run to a location separate from the VPS.
- A restore has been completed successfully on a separate target.
- Health checks are supplemented with application queries and operational monitoring.
- Major image-version changes follow the database engine’s upgrade procedure and a verified-backup plan.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →
