Affordable Python bot hosting

Your Python bot.Beyond your terminal.

You wrote the bot. Give it somewhere to run. Bring your Python project and manage deployments, tokens, and logs without setting up a VPS.

  • Keep your Python stack
  • No VPS setup
  • Zip, Git, or Docker

Your code. Your tokens. One place to run it.

Bring what you already use
  • aiogram
  • python-telegram-bot
  • discord.py
  • Your own worker

Less setup. More building.

Your project has a job to do.
We give it a place to run.

01

Keep the code you already have

Bring your source, dependency files, and startup command. Use Docker if you need custom system packages.

02

Stop babysitting a terminal

Run your worker in an always-on container with automatic restart when the process crashes.

03

Debug from one place

Read Python output, manage environment variables, and open a shell from the panel.

From your machine to the cloud

Bring your project. Make it available.

You handle what your application does. The panel handles where it runs.

  1. 1

    Package your Python project

    Include its source and dependency files, or build a Docker image for your runtime.

  2. 2

    Tell it how to start

    Set your entry-point command and add bot tokens as environment variables.

  3. 3

    Try the hosted version

    Send a message or trigger a task, then check its output in the logs.

What could you put online?

  • A Python chat bot you want to share
  • An API client that sends useful notifications
  • A background worker for your side project

A small project can start small

See your cost before you deploy.

Choose the CPU, memory, and storage your application needs. All allocated resources are billed per minute.

$1.90 / vCPU per month
0.15 vCPU
$1.95 / GB per month
0.15 GB
$0.25 / GB per month
0.0 GB
Your estimate
$0.58/mo

USD for a full month at these allocations. All allocated CPU, RAM, and disk across your applications are billed per minute.

Automatic HTTPSApplication logsWeb shellDeployment tools

This is a resource estimate, not a fixed plan. Your project may need more memory or storage. External model APIs and other third-party services are billed separately.

Built something? Give it a home.

Make your Python project useful beyond your laptop.

Create an account, choose your deployment method, and bring your project.

Host my Python bot

Before you deploy

A few things you might be wondering.

Have a different setup in mind?

Talk to support

Can I host a Python bot without Docker knowledge?

Yes. Zip and Git deployment are available alongside Docker. Your project still needs its dependencies and startup command. Docker is useful when you need custom system packages or a reproducible runtime image.

What command should start a Python bot?

Use the entry point your project defines. For a script named bot.py, python -u bot.py is a common example. Module-based applications may use python -m followed by the module name instead.

Why do Python bot logs appear late?

Python output can be buffered when it is not attached to an interactive terminal. The -u command-line option disables buffering for standard output and error. Also check your logging configuration.

Is Python bot hosting billed per bot?

JustRunMy.App aggregates allocated CPU, RAM, and disk across applications and bills per minute. Each additional application contributes its allocation; the number of bot tokens alone does not define the price.

Want the technical details?Read the full python hosting guide

Affordable Python bot hosting

JustRunMy.App can host container-compatible Python bots as continuously running applications. Deploy with Zip, Git, or Docker, configure credentials through environment variables, and allocate CPU, RAM, and disk for your actual dependency footprint.

A good fit for: aiogram, python-telegram-bot, discord.py, custom API clients, and Python automation workers.

Make dependencies part of the deployment

Include requirements.txt or the dependency and lock files used by your project. Use a Python version compatible with the bot library. Install dependencies in the deployment environment rather than uploading a virtual environment from your laptop, which may contain platform-specific files.

Use a Docker image when packages need native system libraries or a particular build setup. Keep runtime dependencies focused: development tools and unused machine learning packages increase the image size and may increase the memory needed to start.

Choose a command that keeps the bot process running

For a project whose entry file is bot.py, a typical command is python -u bot.py. Replace the filename with your own. The -u option makes standard output and error unbuffered, which helps status messages reach container logs promptly.

Your entry point must start the event loop, worker, or web server and remain running. If it exits immediately, check that you deployed the correct file and that required environment variables are present. Log errors without printing bot tokens or provider keys.

Plan for files, restarts, and concurrent tasks

A reminder bot needs durable schedules, while a notification relay may be nearly stateless. Put files that must survive restarts on persistent storage or use your chosen external database. Test recovery with realistic saved data rather than assuming process memory will survive.

Limit concurrent downloads and background jobs to fit the allocation. A busy bot can run out of RAM when several handlers process large files at once. Check the logs after a burst of messages and increase resources only when the workload needs them.

Deployment checklist

  1. Prepare a clean project

    Include source, dependency files, and the Python entry point. Exclude local virtual environments and secrets.

  2. Choose a deployment method

    Use Zip or Git for a straightforward project, or Docker when you need control over system packages and the runtime.

  3. Configure the process

    Set environment variables and a startup command such as python -u bot.py, adjusted for your project.

  4. Verify logs and saved data

    Send a real request, inspect output, and restart the app to test recovery and storage.

See supported Telegram bot workflows →

Example resource allocations

Monthly USD rates: $1.90 per vCPU, $1.95 per GB RAM, and $0.25 per GB disk. All allocated resources are billed per minute across applications, including idle allocations.

Measure Python plus all imported packages. Image tools, browser libraries, and local embedding models can outweigh the bot code itself; a text-only worker is a different workload.

Illustrative allocations in USD for a full month. These are estimates, not fixed plans or tested workload capacities.
ExamplevCPURAM (GB)DiskMonthly estimate
Minimal allocation example0.150.150 GB$0.58
Lightweight worker example0.250.250.3 GB$1.04
More memory for dependencies0.250.51 GB$1.70
Larger worker example0.511 GB$3.15

References and further reading