Livops vs PythonAnywhere: where to host a Python bot or Django app in 2026
Pick PythonAnywhere if you want a free account to learn on, a browser console and editor, and one $10 plan that covers a web app, an always-on task and 20 scheduled tasks, paid by card. Pick Livops if your users are in Uzbekistan, you deploy from Git, and you want to pay through Payme or Click, with no card: 19 credits a month for a bot, 39 for a Django or Flask app.
By Livops team, the people who build and run LivopsUpdated
PythonAnywhere is where a lot of people put their first Python project: a Flask or Django site, a Telegram bot, a script that runs every night, with a console in the browser. Livops takes a repository and runs the same things as separate services, from servers in Uzbekistan, paid in so’m. This page compares the two with PythonAnywhere’s own numbers, says where PythonAnywhere is the better choice, and ends with the steps to move a bot or a Django app across.
Livops and PythonAnywhere at a glance
| Livops | PythonAnywhere | |
|---|---|---|
| Pricing model | A fixed monthly price per service, paid in credits | A plan: Beginner $0, Developer $10 a month, Custom $10 to $500 a month[1] |
| Smallest always-on process | A bot or worker: 19 credits (19,000 so’m) a month | One always-on task on Developer, $10 a month; Beginner has none[1] |
| A web app | 39 credits (39,000 so’m) a month, custom domain with HTTPS | Developer: 1 web app with 3 web workers and a custom domain[1] |
| Free tier | Static sites free; one 500 MB database and one 1 GB bucket per team; bots and apps paid | Beginner: 1 web app on a pythonanywhere.com address, 100 CPU-seconds a day, 512 MB disk, internet only to allowlisted sites[1] |
| Scheduled jobs | A cron service, standard cron down to every minute, in UTC |
20 tasks on paid plans, hourly or daily[1] |
| Server locations | Tashkent, Uzbekistan | The US, and an EU system in Frankfurt[8] |
| Payment | Payme or Click, in so’m; no card | Not listed |
| How code arrives | git push to GitHub, a folder upload or a public Docker image |
Not listed |
| Browser console | No | Up to 2 consoles on Beginner, unlimited on paid; SSH on paid[1] |
| Databases | PostgreSQL, MySQL, MongoDB, Redis; backed up every night | MySQL on paid plans; Postgres as a paid add-on on a Custom plan[1][7] |
| AI assistant and MCP | An assistant in the cabinet and in Telegram; an MCP server | Not listed |
PythonAnywhere’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 PythonAnywhere is better
- A free account to learn on. Beginner costs nothing and runs a web app at
your-username.pythonanywhere.com, with two consoles[1]. Livops has nothing free for bots and apps beyond one 15-minute demonstration. - Everything in the browser. Consoles on every plan and SSH on paid ones[1] mean you can run and fix code from a browser, without a computer of your own set up for it. Livops has no console: code comes from Git, a folder upload or an image.
- One plan, many processes. Developer is $10 a month for one web app, one always-on task, 20 scheduled tasks and 5 GB of disk[1]. On Livops the same three things are three services, each with its own monthly price.
- Easy to try paid. Paid plans have a 30-day money-back guarantee, and paying for a year costs ten months[1].
- Regions abroad. Besides the US servers there is an EU system, in AWS’s Frankfurt region[8]. Livops has one location, Tashkent; for users in Europe or America, PythonAnywhere is closer.
Where Livops is better
- A bot that stays up without a paid plan to unlock it. A bot is its own service type: always on, polling by default or a webhook the platform registers with Telegram for you. On PythonAnywhere always-on tasks are for paid accounts only[3], and its own tutorial notes that a bot started from a console stops when the server is restarted for maintenance and does not come back[9].
- Priced by type and memory, not by CPU-seconds. A service’s monthly price is set by its type and memory tier. On PythonAnywhere every plan has a daily CPU allowance, and an always-on task that uses it up is stopped and restarted until the allowance renews the next day[3].
- No proxy and no allowlist to ask for. Free PythonAnywhere accounts reach the internet only through a proxy, and only sites on its allowlist[4].
api.telegram.orgis on that list[5], but any other API your bot calls has to be too. - Nothing expires while it is paid for. A bot or app with credits behind it runs until you stop it. A free PythonAnywhere web app expires after a month[2], and free accounts created on or after 15 January 2026 (8 January on the EU system) get no scheduled tasks and no MySQL[2].
- Django set up for you. Livops runs
migratebefore every start andcollectstaticduring the build, and setsALLOWED_HOSTSto the project’s addresses. Python 3.10 to 3.14 are available;.python-versionorruntime.txtpicks one. - Cron by the minute. A
cronservice takes a standard five-field schedule, as often as every minute. PythonAnywhere’s scheduled tasks run hourly or daily[1], and a free account gets one daily task only if it was created before 15 January 2026[6]. - Four database engines, backed up every night. PostgreSQL, MySQL, MongoDB and Redis, kept 7 daily, 4 weekly and 3 monthly; one 500 MB database is free per team. PythonAnywhere offers MySQL, and Postgres only as a paid Custom-plan option[7].
- Paying from Uzbekistan, servers in Tashkent. Credits are bought in so’m through Payme or Click, no card linked. Measured from Tashkent, a site on Livops answers in 10-20 ms; the same request to a site in Frankfurt takes 80-100 ms.
- Watching and explaining. We open your site every minute, and if it stops answering you get a Telegram message within three minutes. Next to a failed build, one button reads the log and says what broke.
Moving from PythonAnywhere to Livops
-
Get the code out. Push it to a GitHub repository, or, if it lives only on PythonAnywhere, download the folder and drop it (or a
.zip) into New project in the cabinet: up to 200 MiB and 5000 files, withvenv,.venvand__pycache__dropped for you. Make surerequirements.txtlists every package the code imports. -
Remove the proxy. If you set
proxy.server:3128for a free account[4], delete it: it exists only on PythonAnywhere. -
Say what each process is. An always-on task becomes a bot or a worker, a scheduled task a cron job. Livops detects a Python Telegram bot or a Django, Flask or FastAPI app by itself; to set it yourself, put
livops.jsonin the repository root:{ "kind": "bot", "start": ".venv/bin/python bot.py" }A scheduled task is
"kind": "cron"with a"schedule"such as"30 4 * * *". The schedule is in UTC: Tashkent is UTC+5, so 09:00 in Tashkent is0 4 * * *. -
For Django or Flask, a web app must listen on the port in
PORT. Insettings.py, readALLOWED_HOSTSfrom the environment:ALLOWED_HOSTS = os.environ.get("ALLOWED_HOSTS", "").split(","). WithDEBUG = False, add WhiteNoise for static files and setSTATIC_ROOT. -
Move the data. A SQLite file goes on the project’s disk at
/app/data(theDATA_DIRvariable), which survives restarts and deploys; a file whose name is written in the code is put there for you. For MySQL, add MySQL on the project:MYSQL_URLand theMYSQL*variables are written into every service. Restore yourmysqldumpover the SSH tunnel the database page shows. -
Copy the secrets under Variables, marking each as secret, or with
livops env set <service> --secret KEY=value. -
Deploy, then switch over. The log shows the build; the app gets
<name>.livops.appwith HTTPS. For a polling bot, stop it on PythonAnywhere first: two copies polling the same token conflict. For your own domain, add it under Domains and put the record Livops shows at your DNS provider.
A bot, a worker and a cron job are 19 credits a month each, a web app 39; see Pricing. Service types are in Frameworks, schedules in Cron and workers.
Questions
Can I run a Telegram bot on a free PythonAnywhere account?
Only with limits. Free accounts have no always-on tasks, reach the internet only through a proxy to allowlisted sites, and a free web app expires after a month. A bot that must run around the clock needs a paid account there. On Livops a bot is always on and costs 19 credits a month (19,000 so'm).
Is Livops cheaper than PythonAnywhere?
For several processes, usually not in dollars: PythonAnywhere's $10 Developer plan covers one web app, one always-on task and 20 scheduled tasks together. On Livops each service has its own monthly price: a bot, worker or cron job 19 credits, a web app 39 credits. Livops is paid in so'm through Payme or Click, with no card.
Does Livops have a free plan like PythonAnywhere's Beginner account?
Not for bots and apps. Static sites are free, and one 500 MB database and one 1 GB storage bucket are free per team. An account that has not paid yet can run its first bot or app for 15 minutes, once, to see it work.
Do I have to change my code to move?
Usually only a little. Remove any proxy setting you added for PythonAnywhere's free accounts, make sure requirements.txt lists everything, and for Django read ALLOWED_HOSTS from the environment. A web app must listen on the port in the PORT variable.
What happens to my SQLite file?
It goes on the project's own disk, which survives restarts and deploys. A SQLite file whose name is written in the code is put there for you; otherwise take the path from the DATA_DIR variable.
Is there an in-browser console on Livops?
No. You deploy by pushing to GitHub or by uploading a folder, read logs in the cabinet or with livops logs, and reach a database from your computer over an SSH tunnel. If you want to run code from a console in the browser, PythonAnywhere has that.
Who wrote this comparison?
The Livops team. Every fact about PythonAnywhere on this page links to PythonAnywhere's own page, with the day we read it.
Sources
- PythonAnywhere — Plans and pricing (pythonanywhere.com). Checked .
- PythonAnywhere help — Free accounts features (help.pythonanywhere.com). Checked .
- PythonAnywhere help — Always-on tasks (help.pythonanywhere.com). Checked .
- PythonAnywhere help — 403 Forbidden errors and the free-account allowlist (help.pythonanywhere.com). Checked .
- PythonAnywhere — Allowlisted sites for free users (pythonanywhere.com). Checked .
- PythonAnywhere help — Scheduled tasks (help.pythonanywhere.com). Checked .
- PythonAnywhere help — Can I use Postgres on PythonAnywhere? (help.pythonanywhere.com). Checked .
- PythonAnywhere blog — Announcing eu.pythonanywhere.com (blog.pythonanywhere.com). Checked .
- PythonAnywhere blog — Building a simple Telegram bot using PythonAnywhere (blog.pythonanywhere.com). Checked .
Put your project online today
Connect GitHub or drop a folder. No card is asked for.
Move your Python project to LivopsRelated
- python-telegram-bot hosting: deploying a v22 botA python-telegram-bot bot runs as one Application: run_polling() for polling, run_webhook() with the webhooks extra for a webhook. Both stop cleanly on SIGTERM. On Livops it runs from a push with bot.py and requirements.txt for 19 credits a month (19,000 so'm).
- aiogram bot hosting: how to deploy an aiogram 3 botAn aiogram 3 bot needs one process that never stops, the token in an environment variable, state kept outside memory and a clean exit on SIGTERM. On Livops you push a repository with bot.py and requirements.txt, and it runs for 19 credits a month (19,000 so'm), polling or webhook.
- Django hosting in 2026: how to deploy a Django app, and whereA Django app in production needs a WSGI or ASGI server instead of runserver, DEBUG off, ALLOWED_HOSTS set, collected static files and migrations on every deploy. On Livops a repository with manage.py and requirements.txt gets all of that from a push, for 39 credits a month (39,000 so'm). Here is how Render, Railway, Fly.io and a VPS compare.
- Flask hosting in 2026: how to deploy a Flask app, and whereA Flask app in production runs on a WSGI server such as Gunicorn, never on flask run, and is told it sits behind a proxy. On Livops a repository with app.py and requirements.txt that lists gunicorn starts on Gunicorn from a push, for 39 credits a month (39,000 so'm). Here is how Render, Railway, Fly.io and a VPS compare.
- Livops vs Render: which one to deploy on in 2026Pick Render if your users are in the US, Europe or Singapore, you pay by card, and you want free web services to start with, autoscaling and larger managed Postgres. Pick Livops if your users are in Uzbekistan and you want to pay through Payme or Click, with no card, at 19 credits a month for a bot or 39 for an app.