# Livops vs DigitalOcean App Platform: which one to deploy on in 2026

> Pick DigitalOcean App Platform if your users are in North America, Europe or Asia, you pay by card or PayPal, and you want autoscaling, regions to choose from and managed databases with failover. Pick Livops if your users are in Uzbekistan and you want to pay through Payme or Click, with no card, with a free 500 MB database and 19 credits a month for a bot or 39 for an app.

Source: https://livops.dev/en/compare/livops-vs-digitalocean-app-platform

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

DigitalOcean App Platform and Livops work the same way: you point them at a repository or an image, they build it and run it as components (web services, workers, jobs, static sites) with databases beside them. App Platform has regions around the world, autoscaling and a full range of managed databases; Livops has servers in Uzbekistan, payment in so'm and a free starter database. This page compares the two with DigitalOcean's own numbers and ends with the steps to move an app across.

## Livops and DigitalOcean App Platform at a glance

| | Livops | DigitalOcean App Platform |
| --- | --- | --- |
| Pricing model | A fixed monthly price per service, paid in credits | A monthly price per container instance, by its size[1] |
| Smallest always-on service | A bot or worker: 19 credits (19,000 so'm) a month | $5 a month: 1 shared vCPU, 512 MiB, 50 GiB of transfer[1] |
| Free tier | Static sites free; one 500 MB database and one 1 GB bucket per team; bots and apps paid | 3 apps with static sites, 1 GiB of transfer each; more at $3 a month[1] |
| Server locations | Tashkent, Uzbekistan | 12 regions for dynamic apps, from Frankfurt, London and Amsterdam to Bangalore, Singapore and Sydney[2] |
| Payment | Payme or Click, in so'm; no card | Credit and debit cards, PayPal, Google Pay, Apple Pay and others; no prepaid cards[8] |
| Telegram bot | Its own service type: always on, polling or a webhook set up for you | A worker: not routable, no external URL[4] |
| Scheduled jobs | A `cron` service, standard cron down to every minute, in UTC | A scheduled job, at most every 15 minutes, with a time zone you set; billed only while it runs[5] |
| Databases | PostgreSQL, MySQL, MongoDB, Redis; one 500 MB database free; backed up every night | A $7 development PostgreSQL[1]; managed PostgreSQL, MySQL, Valkey, MongoDB, Kafka and OpenSearch from $15[6] |
| Scaling | Four memory tiers, the largest 2 GB | Autoscaling on CPU (dedicated instances) or requests[3]; shared instances do not autoscale[1] |
| AI assistant and MCP | An assistant in the cabinet and in Telegram; an MCP server | An MCP server, OAuth or an API token[9] |

DigitalOcean's facts are from its own pages, read on 20 November 2026. Livops prices are the ones the cabinet bills today.

## Where DigitalOcean App Platform is better

- **Regions abroad.** Dynamic apps run in 12 regions, among them Frankfurt, London, Amsterdam, New York, San Francisco, Toronto, Bangalore, Singapore and Sydney[2]. Livops has one location, Tashkent; for users in those places App Platform is closer.
- **Scaling.** Dedicated instances autoscale on CPU, and any app on request metrics; you can also scale by hand, across and up[3]. Shared instances go up to 2 vCPUs and 4 GiB[1]. A Livops service picks from four memory tiers, the largest 2 GB, and the docs describe no autoscaling.
- **Production databases.** Managed PostgreSQL takes a full backup every day and restores to any point in the previous seven days; with a standby node it fails over automatically, and the Advanced Edition adds connection pools[7]. Kafka and OpenSearch are offered too[6]. A Livops database goes up to 5 GB, PostgreSQL takes 20 connections at once, and a built-in pooler is not offered yet.
- **More ways to pay by card.** Seven card brands, PayPal, Google Pay, Apple Pay, Alipay and Link[8]. If you have an international card, that is easy; Livops takes only Payme and Click.
- **More kinds of component.** Functions run on demand in response to requests[3], and jobs can run before every deploy or after a failed or successful one[5].
- **Schedules in your time zone.** A scheduled job takes a `time_zone`[5]. A Livops `cron` schedule is always read in UTC.

## Where Livops is better

- **Paying from Uzbekistan.** Credits are bought in so'm through Payme or Click, and no card is linked. DigitalOcean does not accept virtual, electron or prepaid cards[8].
- **Servers in Tashkent.** Measured from Tashkent, a site on Livops answers in 10-20 ms; the same request to a site in Frankfurt, one of App Platform's regions[2], takes 80-100 ms.
- **A database that starts free.** One 500 MB PostgreSQL, MySQL, MongoDB or Redis database is free per team, and larger ones start at 9 credits a month. On App Platform the development database is $7 a month and PostgreSQL only[1]; managed MySQL, Valkey and MongoDB start at about $15[6].
- **Nightly backups for every engine.** All four engines, Redis included, 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.
- **Cron by the minute.** A `cron` service runs as often as every minute. App Platform's scheduled jobs run at most every 15 minutes[5].
- **A Telegram bot as a first-class service.** A bot is its own type: polling by default, or a webhook the platform registers with Telegram for you. A bot that exits is started again, and one that keeps crashing is stopped and you are told why, in the cabinet and in Telegram.
- **An assistant that explains the failure.** Next to a failed build, one button reads the log and says what broke; 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.
- **A CI token that cannot do damage.** An `lvp_` API token deploys and reads through MCP, and cannot delete, reveal a password or pay. If a site stops answering, you get a Telegram message within three minutes.

## Moving from App Platform to Livops

1. **Create one service per component.** In the cabinet, **New project → Connect GitHub**, and choose the same repository and branch; GitLab works through a webhook. The app spec is not read: a web service becomes `web`, a worker `worker` (or `bot` for a Telegram bot), a scheduled job `cron`. Put `livops.json` in the repository root, or the component's folder in a monorepo:

   ```json
   {
     "kind": "cron",
     "start": ".venv/bin/python job.py",
     "schedule": "*/15 * * * *"
   }
   ```

2. **Convert schedules to UTC.** An App Platform job may have had a `time_zone`[5]; Livops reads the `schedule` in UTC. Tashkent is UTC+5, so 09:00 in Tashkent is `0 4 * * *`.
3. **Check the image source.** A `Dockerfile` in the repository is built as before; a container runs as user 1000, so an image built with `USER root` will not start. An image you ran directly must be public on docker.io, ghcr.io or quay.io; one kept only in DigitalOcean Container Registry is built from its `Dockerfile` instead.
4. **Move the databases.** Add PostgreSQL, MySQL, MongoDB or Redis on the project; `DATABASE_URL`, `MYSQL_URL`, `MONGO_URL` or `REDIS_URL` is written into every service. Restore a `pg_dump`, `mysqldump` or `mongodump` over the SSH tunnel the database page shows. PostgreSQL accepts 20 connections at once, so keep the pool small.
5. **Copy the variables** under **Variables**, marking secrets, or with `livops env set <service> --secret KEY=value`. A web app must listen on the port in `PORT`.
6. **Deploy, then move the domain.** The app gets `<name>.livops.app` with HTTPS. Add your domain under **Domains** and put the record Livops shows at your DNS provider (a subdomain is a `CNAME` to `cname.livops.app`); the certificate is issued once it resolves. For a polling bot, stop the App Platform worker first: two copies polling one token conflict.

Service types are in [Frameworks](https://livops.dev/en/docs/frameworks); databases and backups in [Databases](https://livops.dev/en/docs/databases).

## Questions

**Is DigitalOcean App Platform cheaper than Livops?**

In dollars, its smallest container is $5 a month for 1 shared vCPU and 512 MiB. On Livops a bot is 19 credits a month (19,000 so'm) and an app 39 credits (39,000 so'm), paid in so'm. The bigger difference is the database: one 500 MB database is free per team on Livops, while App Platform's development database is $7 a month and a managed one starts at about $15.

**Are static sites free on both?**

Yes. App Platform gives three free apps with static sites, with 1 GiB of transfer each, and charges $3 a month for each one after that. On Livops static sites are free, and the number you can have is set by the plan.

**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. Bought credits never expire.

**How does a Telegram bot run on each?**

On App Platform a polling bot is a worker, a component with no public URL, billed as a container instance. On Livops a bot is its own service type: always on, polling by default or a webhook the platform registers with Telegram for you.

**Does Livops read the App Platform app spec?**

No. Livops reads livops.json, a Procfile, a Dockerfile, .nvmrc, .node-version, .python-version and runtime.txt, and detects the rest from the repository. Each component of the app spec becomes a service of its own.

**Where are the Livops servers?**

In Tashkent, Uzbekistan, and only there. If your users are in North America, Europe or Asia, one of App Platform's regions will be closer to them.

**Who wrote this comparison?**

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

## Sources

1. [DigitalOcean — App Platform pricing](https://www.digitalocean.com/pricing/app-platform). Checked 20 November 2026.
2. [DigitalOcean Docs — App Platform regional availability](https://docs.digitalocean.com/products/app-platform/details/availability/). Checked 20 November 2026.
3. [DigitalOcean Docs — App Platform features](https://docs.digitalocean.com/products/app-platform/details/features/). Checked 20 November 2026.
4. [DigitalOcean Docs — How to manage workers in App Platform](https://docs.digitalocean.com/products/app-platform/how-to/manage-workers/). Checked 20 November 2026.
5. [DigitalOcean Docs — How to manage cron jobs and deployment jobs in App Platform](https://docs.digitalocean.com/products/app-platform/how-to/manage-jobs/). Checked 20 November 2026.
6. [DigitalOcean — Managed databases pricing](https://www.digitalocean.com/pricing/managed-databases). Checked 20 November 2026.
7. [DigitalOcean Docs — PostgreSQL features](https://docs.digitalocean.com/products/databases/postgresql/details/features/). Checked 20 November 2026.
8. [DigitalOcean Docs — How to manage payment methods](https://docs.digitalocean.com/platform/billing/manage-payment-methods/). Checked 20 November 2026.
9. [DigitalOcean Docs — Configure remote MCP](https://docs.digitalocean.com/reference/mcp/configure-mcp/). Checked 20 November 2026.
