# Livops vs Coolify: managed platform or self-hosted PaaS?

> Pick Coolify if you want to run your own platform for free on a server you control, with root, any region you can rent, and as many apps as the machine holds. Pick Livops if you would rather not look after a server at all, and want servers in Uzbekistan, nightly backups and payment through Payme or Click, with no card.

Source: https://livops.dev/en/compare/livops-vs-coolify

By Livops team, the people who build and run Livops. Updated 20 November 2026.

Coolify is software: you install it on a server you own or rent, and it turns that server into a platform that deploys your apps and databases. Livops is a service: the servers are ours, in Uzbekistan, and you hand over the code. The choice is less about features than about who looks after the machine. This page compares the two with Coolify's own documentation and ends with the steps to move a project across.

## Livops and Coolify at a glance

| | Livops | Coolify |
| --- | --- | --- |
| Pricing model | A fixed monthly price per project, paid in credits | Self-hosted: free forever[1]. Cloud: $5 a month for 2 servers, $3 per extra server[1]. Plus the servers |
| Smallest always-on service | A bot: 19 credits (19,000 so'm) a month | Whatever you run on your server; Coolify itself needs 2 CPU cores, 2 GB of memory and 10 GB of disk[2] |
| Free tier | Static sites free; one 500 MB database and one 1 GB bucket per team; bots and apps paid | The self-hosted version, on a server you pay for[1] |
| Server locations | Tashkent, Uzbekistan | Wherever your servers are; Coolify Cloud's dashboard runs in Falkenstein, Germany[3] |
| Payment | Payme or Click, in so'm; no card | For Cloud, not listed |
| Telegram bot | Its own service type: always on, polling or a webhook set up for you | Any app you deploy from Git, a Dockerfile, an image or Docker Compose[5] |
| Databases | PostgreSQL, MySQL, MongoDB, Redis; backed up every night | PostgreSQL, MySQL, MariaDB, MongoDB, Redis, Dragonfly, KeyDB, ClickHouse; scheduled backups for most, not for Redis[4] |
| AI assistant and MCP | An assistant in the cabinet and in Telegram; an MCP server | An MCP server, off by default when self-hosted[6] |
| Self-hosting | No | Yes; that is the product[1] |

Coolify's facts are from its own pages, read on 20 November 2026; "Not listed" means the pages we read do not mention it. Livops prices are the ones the cabinet bills today.

## Where Coolify is better

- **Root and your own machine.** You install Coolify on your server over SSH[2], so everything on it is yours to change. Livops gives you no root.
- **Any location.** Your apps run wherever your server is[3], including a VPS in Tashkent: SmartCloud's 2-core, 2 GB plan is 126 000 so'm a month[7], enough for Coolify's minimum[2].
- **Cost that does not grow per app.** Self-hosted Coolify is free[1], so ten small apps on one server cost the server. On Livops each bot or app has its own monthly price.
- **More database engines.** MariaDB, Dragonfly, KeyDB and ClickHouse besides the usual four[4]. Livops offers PostgreSQL, MySQL, MongoDB and Redis.
- **Docker Compose.** A Git application can deploy from a Compose definition in the repository[5]. Livops does not read a Compose file.
- **Finer MCP keys.** A Coolify token is given exactly the scopes it needs: read, deploy, write, delete[6]. A Livops `lvp_` token is one fixed set: deploy and read.

## Where Livops is better

- **No server to look after.** Coolify is installed on your own Linux server over SSH[2], so that server is yours to keep running: its operating system, its updates, its disk. On Livops you push code and the rest is ours. If a site stops answering, we notice and message you in Telegram within three minutes.
- **Backups off the machine, Redis included.** Every database is backed up every night to a separate location and kept 7 daily, 4 weekly and 3 monthly; a restore never overwrites the original. Coolify's Redis, Dragonfly and KeyDB have no scheduled backups, and the other engines back up on a schedule you set, optionally to S3[4].
- **An assistant, not just an API.** Next to a failed build one button explains it, and the fix comes as a button. A deploy you ask it for starts on its own; everything else waits for your press unless you turn on auto mode for small reversible steps. It never deletes anything.
- **Paying from Uzbekistan.** Credits in so'm through Payme or Click, no card; static sites free.
- **MCP sign-in through the browser.** A client signs in with OAuth and gets a key that lasts an hour and renews itself. Coolify's MCP clients use a token you create and paste[6].

## Moving from Coolify to Livops

1. **Create the project.** In the cabinet, **New project → Connect GitHub**, and choose the repository. A `Dockerfile` is used if there is one; a container runs as user 1000, so an image built with `USER root` will not start. An image Coolify pulled can run directly if it is public on docker.io, ghcr.io or quay.io.
2. **Split the Compose file.** Add each service on its own, with `livops.json` to set the type:

   ```json
   {
     "kind": "worker",
     "start": "node worker.js"
   }
   ```

3. **Add the databases** on the project; `DATABASE_URL`, `MYSQL_URL`, `MONGO_URL` or `REDIS_URL` is written into every service. Copy the data with `pg_dump`, `mysqldump` or `mongodump` over the SSH tunnel the database page shows.
4. **Move the files.** A volume's contents go on the project's disk: `/data` for a Dockerfile project, with the path in `DATA_DIR`.
5. **Copy the variables** under **Variables**, marking secrets, or with `livops env set <service> --secret KEY=value`.
6. **Deploy, then move the domain.** Add it under **Domains** and point the record Livops shows at it; the certificate is issued once it resolves. For a polling bot, stop the Coolify copy first: two copies polling one token conflict.

The deploy sources are in [Ways to deploy](https://livops.dev/en/docs/deploy); backups in [Databases](https://livops.dev/en/docs/databases).

## Questions

**Is Coolify free?**

The self-hosted version is free; you pay for the server it runs on. Coolify Cloud, where Coolify's team runs the dashboard for you, is paid per connected server, and you still bring your own servers.

**Can I run Coolify on a server in Uzbekistan?**

Yes, on any Linux server you rent, as long as it has the 2 CPU cores, 2 GB of memory and 10 GB of disk Coolify asks for. You then look after that server yourself.

**What do I maintain on Livops?**

Your code. There is no server to set up, no Nginx config and no certificate to obtain, and databases are backed up for you. You do not get root, so if you need system software of your own, a server with Coolify or a plain VPS is the better fit.

**Are Livops databases backed up?**

Yes. PostgreSQL, MySQL, MongoDB and Redis are backed up every night to a separate location and kept 7 daily, 4 weekly and 3 monthly. A restore opens as a new database next to the original.

**Can I pay for Livops without a card?**

Yes. Credits are bought in so'm through Payme or Click, and no card has to be linked.

**Does Livops run my docker-compose.yml?**

Not as a file. Each service is added on its own: from the repository, from a Dockerfile, or as a public image from docker.io, ghcr.io or quay.io, and a database is added on the project. When one repository holds a bot, an API and a site, Livops can start them together.

**Who wrote this comparison?**

The Livops team. Every fact about Coolify on this page links to Coolify's own page, with the day we read it.

## Sources

1. [Coolify — Pricing](https://coolify.io/pricing). Checked 20 November 2026.
2. [Coolify — Installation](https://coolify.io/docs/get-started/installation). Checked 20 November 2026.
3. [Coolify — Coolify Cloud](https://coolify.io/docs/get-started/cloud). Checked 20 November 2026.
4. [Coolify — Databases](https://coolify.io/docs/databases). Checked 20 November 2026.
5. [Coolify — Applications](https://coolify.io/docs/applications). Checked 20 November 2026.
6. [Coolify — Set up MCP](https://coolify.io/docs/mcp/setup). Checked 20 November 2026.
7. [SmartCloud — VDS plans](https://smartcloud.uz/cloud-services/vds/). Checked 20 November 2026.
