You can deploy PostgreSQL, MySQL, MariaDB, MongoDB, Redis, Dragonfly, KeyDB, or ClickHouse on a VPS through Coolify without manually assembling Docker commands. Coolify acts as the control plane; Docker on the server you connect runs the database container. The safe workflow is to select the right engine, verify the generated persistent volume and mount path, start the resource, connect applications over Coolify’s internal URL, and configure off-server, database-aware backups.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
The crucial distinction is that a persistent volume protects data when a container is replaced, but it is not a backup. Treat storage, network exposure, credentials, upgrades, health checks, and restore testing as separate operational tasks.
As an Amazon Associate I earn from qualifying purchases.
Crashes, 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 minutePC 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 & 11What a Coolify database deployment actually does
Coolify does not provide a separate hosted database service in this setup. It deploys a standalone database as a container on the server and Docker network you select. Your VPS supplies the CPU, memory, disk, network connection, and operating-system resources; Coolify supplies the deployment interface, generated configuration, service lifecycle controls, internal connection details, and backup options for supported engines.
When you create a database resource, Coolify prepares the container configuration. The container is not running until you select Start. The generated credentials and connection settings should be reviewed before the first start, because changing them after an application has begun writing data can cause authentication failures or an apparent loss of access.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
A database resource has four independent concerns:
- Engine: the database technology your application supports.
- Persistent storage: a named Docker volume mounted at the path expected by the image.
- Network access: an internal URL for services on the same destination, or deliberately configured public access for outside clients.
- Recovery: database-aware backups stored somewhere other than the VPS, plus a restore procedure you have actually tested.
Requirements before you begin
Prepare these items before opening Coolify:
- An SSH-capable VPS or other server that Coolify can connect to.
- Administrative access sufficient for Coolify to install or use Docker and manage containers on that server.
- A Coolify installation with permission to create resources in the target project and environment.
- The database engine and major version supported by your application.
- A plan for disk capacity, memory, firewall rules, credentials, and off-server backups.
- An application deployment target, if the database will be used by a service managed by the same Coolify destination.
Estimate storage from the database’s current data, indexes, transaction logs, temporary files, backup retention, and expected growth. Leave operating-system and Docker headroom rather than allocating the entire disk to database files. A persistent volume does not protect you from a full disk, filesystem corruption, accidental deletion, or a failed VPS.
Choose the database engine
Choose based on the application’s data model and compatibility, not on the shortest setup form. Coolify’s documented one-click database resources have these default internal ports, data paths, and backup capabilities:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Engine | Best fit | Default internal port | Default data path | Coolify database-aware backups |
|---|---|---|---|---|
| PostgreSQL | Relational workloads, transactional applications | 5432 | Before version 18: /var/lib/postgresql/data; version 18 and later: /var/lib/postgresql |
Yes |
| MySQL | Relational workloads and applications requiring MySQL compatibility | 3306 | /var/lib/mysql |
Yes |
| MariaDB | MySQL-compatible relational workloads | 3306 | /var/lib/mysql |
Yes |
| MongoDB | Document-oriented workloads | 27017 | /data/db and /data/configdb |
Yes |
| Redis | Cache, queues, streams, and key-value data | 6379 | /data |
No standalone scheduled database-backup workflow |
| Dragonfly | Redis-compatible cache and key-value workloads | 6379 | /data |
No standalone scheduled database-backup workflow |
| KeyDB | Redis-compatible workloads needing its feature set | 6379 | /data |
No standalone scheduled database-backup workflow |
| ClickHouse | Analytical and columnar workloads | 9000 | /var/lib/clickhouse |
Yes |
The port in this table is the container’s normal internal port. It does not mean the database is automatically reachable from the public internet. For an application on the same Coolify destination, use the generated internal URL instead of hard-coding a host IP and published port.
Deploy the database in Coolify
1. Connect the VPS
Add the VPS, or another SSH-capable server, to Coolify. Coolify uses the connected server as the workload host; it is not a proxy that moves the database to a separate managed service. Confirm that the server appears available and that Docker can run containers on it before creating the resource.
2. Open a project and environment
Choose the project and environment where the database belongs. Keeping the database and its consuming application in an intentional environment makes network discovery, access control, backups, and later maintenance easier to audit.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
3. Create a database resource
- Select Create New Resource.
- Choose the required database engine.
- Select the connected server and its Docker destination.
- Review the generated username, password, database name, image or version, port, and other settings before confirming creation.
Coolify generates credentials and connection settings for the selected engine. Save the final values in your secret-management process rather than copying passwords into source code or public issue trackers.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute4. Verify persistent storage before starting
Open the resource’s Configuration > Persistent Storage section. Confirm that the generated named volume is still mounted at the path expected by the selected image. Do not remove the mount, rename it casually, or point it at a different directory while trying to troubleshoot an empty database.
For PostgreSQL, pay particular attention to the image generation: versions before 18 use /var/lib/postgresql/data, while PostgreSQL 18 and later use /var/lib/postgresql. A volume mounted at the wrong path can make a real existing database look empty because the container is reading a new directory.
5. Start the resource
Select Start. Creating the resource prepares its configuration; the start operation launches the database container. Watch the deployment output and container logs for initialization errors, permission problems, an invalid environment variable, or a storage mount failure.
6. Check readiness, then test a real login
Wait for the container to report healthy or ready, then connect with a database client using the generated credentials. A successful Docker health state is not proof that your application can authenticate, run its migrations, execute queries, or recover from a backup. Run a small, non-destructive connection test and, where appropriate, a transaction or schema check.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
7. Connect an application on the same destination
Use Coolify’s generated Internal URL when the application and database run on the same destination network. Put the URL and credentials in the application’s environment variables or secret settings. Do not use localhost: inside an application container, localhost refers to that application container, not the database container.
Use the engine’s expected connection format. For example, a PostgreSQL client normally needs a host, port 5432, database, username, and password; a MySQL-compatible client normally uses port 3306; MongoDB uses port 27017; Redis-compatible clients use port 6379; and ClickHouse’s native interface uses port 9000. Let the application’s own driver determine the exact URL syntax.
8. Expose it externally only when necessary
External administration tools or applications outside the Coolify destination require deliberate public access or a port mapping. If you enable one, restrict the VPS and provider firewall to known source addresses, use strong credentials, and enable SSL or TLS where the engine and client support it. Publicly publishing a database port without source restrictions turns a private service into an internet scanning target.
Persistent storage: keeping data after a redeploy
Container filesystems are disposable. Coolify can recreate a database container while retaining its named volume, which is why a correctly mounted persistent volume normally survives ordinary redeploys, restarts, and container replacement.
Free tools Windows power users keep installed
One-click scans. No signup required.
Storage remains local to the deployment server unless you deliberately provide shared storage. A VPS failure, disk loss, accidental volume deletion, ransomware, or an operator mistake can therefore destroy both the running database and its persistent files. Persistence is an availability measure for routine container operations, not a recovery plan.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Protect the mount
- Keep the generated named volume attached to the engine’s expected data path.
- Do not initialize a new empty volume while attempting to fix a startup problem unless you have identified and preserved the original volume.
- Record the volume name, mount path, engine version, and server location as part of your deployment inventory.
- Before changing image versions or storage settings, take and verify a backup.
If a redeployed database appears empty, stop and compare the current volume and mount path with the previous configuration. Do not immediately create tables or restore over the running container; doing so can overwrite evidence of the original data location.
Backups and restore planning
Coolify explicitly distinguishes persistent storage from a database-aware backup. A volume copy may capture files while the engine is changing them, whereas a database-aware dump or backup uses the engine’s own consistency mechanisms. Configure scheduled database-aware backups for PostgreSQL, MySQL, MariaDB, MongoDB, and ClickHouse.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Send backups off the VPS
Store backup files in an S3-compatible bucket or another location separate from the deployment server. A second directory on the same VPS is not an independent failure domain. Choose retention based on how far back you may need to recover, and protect the bucket with separate credentials and access controls.
Backups consume storage and bandwidth. Monitor successful completion, object size, retention expiry, and available space rather than assuming that a scheduled job ran correctly.
Redis-compatible engines require a different plan
Redis, Dragonfly, and KeyDB have persistent storage but no standalone scheduled database-backup workflow in Coolify’s documented database resources. Decide whether the data is disposable cache state or must be recoverable. If it must be recovered, use the engine’s supported persistence and export mechanisms, copy the resulting files or snapshots off the VPS, and document how to restore them. Do not call a retained Docker volume a backup.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Test a restore
- Provision a temporary server or isolated destination with enough disk space.
- Deploy the same engine family and a compatible image version.
- Restore one backup to the isolated resource, never directly over production.
- Verify that expected databases, collections, tables, indexes, users, and representative records exist.
- Run an application-level smoke test, such as login, a read query, and a write transaction where safe.
- Record the elapsed time, missing prerequisites, and exact commands or Coolify settings needed to repeat the restore.
A backup that cannot be restored within your required recovery window is not a useful backup. Repeat the test after major engine, schema, storage, or backup-policy changes.
Health checks, upgrades, and daily operations
Understand what the health check proves
Coolify’s database health check is a Docker readiness or liveness probe. It can show that a process responds as expected, but it does not validate application queries, replication, data integrity, or backup recoverability. Keep separate checks for application connectivity, error rates, disk space, memory pressure, replication where applicable, and backup success.
Do not treat a new image tag as an upgrade plan
Changing a major image version is not automatically a safe database upgrade. Before a major-version change, take a verified backup, read the engine’s upgrade requirements, check extension or compatibility constraints, and follow the engine-specific migration procedure. Keep the old volume intact until the upgraded instance has passed functional checks and the rollback decision is clear.
Watch resource pressure
- Disk: database files, indexes, logs, temporary files, and backup staging can grow at different rates.
- Memory: caches improve performance but can compete with the VPS operating system and other containers.
- CPU: migrations, index builds, analytical queries, and compaction can affect neighboring game services.
- Network: off-server backups and external clients consume bandwidth and may be limited by the VPS provider.
Schedule heavy maintenance outside peak game traffic when possible, and avoid placing a production database on an undersized server shared with build jobs or unrelated workloads.
Troubleshooting common failures
| Symptom | Likely cause | Safe response |
|---|---|---|
| Database starts with no tables or users | Wrong volume, removed mount, or incorrect engine data path | Stop writes, compare the current named volume and mount path with the previous configuration, and preserve the original volume before changing anything. |
| Container exits during startup | Invalid settings, permissions, incompatible files, insufficient disk, or an interrupted initialization | Read the deployment and container logs, check free disk and the mounted path, and do not delete the volume as a first step. |
| Application cannot resolve the database host | Incorrect hostname, wrong network, or use of localhost inside the application container |
Use the generated Internal URL and verify that both resources are on the intended Coolify destination network. |
| External client times out | No public mapping, blocked firewall, wrong port, or a service intentionally limited to the internal network | Prefer an internal connection; if external access is required, configure the mapping and restrict firewall source addresses. |
| Authentication fails after redeploy | Changed generated credentials, stale application secrets, or an application connecting to a different resource | Compare the resource credentials with the application’s secret values and rotate them through a planned change rather than editing random container variables. |
| Health check is green but the app fails | Docker process is ready while migrations, permissions, schema, or queries are broken | Run an application-level connection and query test; inspect migration and application logs separately from the container health state. |
| Restore produces an unusable database | Untested backup, incompatible engine version, missing extensions, or incomplete export | Restore into isolation, match the required version and dependencies, and verify representative application operations before declaring recovery successful. |
How to evaluate the VPS for Coolify databases
Coolify’s documentation names VPS and other SSH-capable infrastructure but does not endorse a particular provider. Compare infrastructure using the workload rather than a brand name:
- SSH and administration: reliable access, supported operating system, and firewall controls.
- CPU and RAM: enough capacity for the database plus Coolify, the application, backups, and the operating system.
- Disk performance and capacity: databases are sensitive to latency and sustained write performance, not only advertised storage size.
- Region: place the server near the users or application services that need low latency, while considering data-residency requirements.
- Network limits: account for application traffic, external administration, and off-server backup transfers.
- Snapshots: useful for server-level rollback, but not a replacement for a consistent, database-aware backup.
- Independent backup destination: ensure the backup location remains available if the VPS disappears.
Production launch checklist
- Engine and major version match the application’s support matrix.
- Server, project, environment, and destination are recorded.
- Generated credentials are stored securely and application secrets match them.
- Persistent Storage shows the intended named volume and engine-specific mount path.
- Database starts successfully and a real client login works.
- Application uses the generated Internal URL when running on the same destination.
- No database port is public unless external access is required.
- Firewall rules restrict every exposed port to known sources.
- TLS is enabled for supported external connections.
- Database-aware backups are scheduled for supported engines and stored off the VPS.
- Redis-compatible data has a documented export or persistence plan if it is not disposable.
- A restore has been tested in an isolated destination.
- Disk, memory, CPU, health, query, and backup monitoring are separate checks.
- Major-version upgrades have a verified backup and an engine-specific migration plan.
With those controls in place, Coolify provides a practical deployment layer for databases on your own VPS: the container can be recreated without discarding its named volume, applications can use an internal network address, and recovery can be handled independently of the server that runs production.
Quick Recap
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.
