# Pricing

> Every price is in credits. 1 credit is 1,000 so'm. Static sites are free, a Telegram bot is 19 credits/mo, an app 39 credits/mo. A plan gives credits for less.

Source: https://livops.dev/en/docs/pricing

On Livops every price is in **credits**. **1 credit is 1,000 so'm.** Money only buys credits; a running project takes its price off the balance once a month. Static sites are free.

## Buying credits

- In the cabinet, **Billing → Buy credits**: type how many you need (10 to 5,000) and the price in so'm shows under the box. Quick picks: 50/100/300/1,000.
- Payment through **Payme** or **Click**, in so'm. No card needs to be linked.
- Once paid, the credits land on the balance. Bought credits never expire.
- Sometimes there is a campaign that adds a percentage bonus to every purchase. A promo code gives credits or a bonus on the next purchase — enter it on the Billing page.

## What a project costs

| What | A month |
| --- | --- |
| Static site | Free |
| Telegram bot | 19 credits (19,000 so'm) |
| Web app or server | 39 credits (39,000 so'm) |
| Database 500 MB | Free — one per team |
| Database 1 GB / 3 GB / 5 GB | 9 / 19 / 29 credits |
| Storage 1 GB | Free — one per team |
| Storage 5 GB / 25 GB / 100 GB | 15 / 49 / 149 credits |

Each project is charged once a month from the day it was added. Staging and other environments cost half. Current prices are always in the cabinet.

## Plans

A plan is a monthly price that gives you **more** credits than it costs. So the same usage is always cheaper on a plan.

| | **Free** | **Hobby** | **Pro** | **Team** |
| --- | --- | --- | --- | --- |
| Price, a month | 0 | 49 credits | 179 credits | 459 credits |
| In so'm | 0 | 49,000 so'm | 179,000 so'm | 459,000 so'm |
| Credits it gives a month | — | 75 | 300 | 900 |
| Static sites | 30 | 50 | 100 | 300 |
| Team members | 3 | 5 | 10 | 30 |
| Builds at once | 2 | 3 | 4 | 6 |
| Builds a day | 30 | 60 | 100 | 200 |
| Builds a month | 40 | 150 | 400 | 1,000 |
| Assistant questions a month | 20 | 100 | 300 | 1,000 |
| Form submissions a month | 100 | 5,000 | 5,000 | 5,000 |
| Full analytics | — | yes | yes | yes |

- A plan's month is paid from **bought** credits — never from the plan's own credits or from gifted ones.
- The plan's credits are spent first. What is left lasts **one more month**, then expires.
- Moving up works at once. Mid-month, the price difference for the days left is charged and the same share of the credit difference is added.
- Moving down happens when the paid month ends.
- If a plan's month goes unpaid, after the grace period the account moves to Free. Nothing is switched off: projects keep running on credits.
- If a plan's price goes up, an account that chose it before keeps the old price and still gets the full credits.
- An account that paid without a plan keeps Hobby's limits.

## Past the limits

If a plan's allowance runs out before the month does, the next ones come off the credits:

- 5 assistant questions — 1 credit;
- each build — 1 credit;
- 100 form submissions — 1 credit.

With no credits left these stop: "Out of credits — top up". Free things keep working.

## When credits run out

- If a running project's month cannot be taken because the credits are short, we wait **3 days** as before, then the project is stopped. Databases are not deleted.
- Buy credits and stopped projects start again by themselves — no rebuild needed.
- When the credits will last about a week, you get a notification and a Telegram message.

## No trial period

There is **no** free trial period. Static sites are always free; bots and applications run once there are credits.

## The 15-minute demonstration

On an account that has not paid yet, the **first** paid app (a bot or an application) runs for **15 minutes** even on a zero balance — so you can see it work. It is not a trial: once, for one app.

- The project page shows "Demonstration mode" and the time left; at the start and about 3 minutes before the end you get a notification and a Telegram message.
- Buy credits in that time and the app keeps running without a stop.
- If not, after 15 minutes the app stops and waits — when credits arrive it starts by itself, no rebuild needed.
- Databases and storage are not part of the demonstration: they start once there are credits.
- Ready-made apps from templates (n8n, Ghost, Umami…) are not part of it either: they are known to work and most need a database, so they start after the first payment. They do not use up your demonstration.

## Old balances

A so'm balance from before October 2026 was converted to credits exactly: **1 000 so'm = 1 credit**, remainders kept (12 345 so'm became 12.345 credits). A plan price agreed earlier is kept.

Need many projects or have a question? Write to [@livops_uz](https://t.me/livops_uz).
