Python hosting # Python hosting Run Django, FastAPI and Telegram bot workloads in isolated Python containers with deployment from Git. Configure external dependencies and choose a zone package that meets your resource needs. [Get started](https://panel.deplomo.com/signup)[View plans and pricing](/pricing) ## Why run Python apps on Deplomo? What engineering teams need for reliable deployments. ### Direct deployment from Git Connect a supported Python repository to use the platform’s build workflow. Dependency installation and web-server startup depend on project settings; interruptions during deployment depend on health checks and configuration. ### Package registries and external API access Install Python packages from the configured package index and connect to external APIs where available. Access depends on credentials, network routes, package configuration and third-party availability. ### WSGI and ASGI application support, subject to the supported runtime and configuration Run Python frameworks such as FastAPI, Django Channels and Flask with servers such as Uvicorn or Gunicorn, subject to runtime and configuration support. ### Containerized Python runtime CPU, RAM and storage depend on the selected package and its published limits. Check resource allocation and storage options before deployment. ## Frequently asked questions about Python hosting Answers to common technical questions about deploying web services, Telegram bots and databases. What is Python hosting in Europe, and how does it differ from cPanel shared hosting? Do I need a proxy to run a Telegram bot on Python hosting? Are background processes and libraries such as Celery and Redis supported? Which Python versions and frameworks are available? How are Django static and media files managed? How is Python hosting priced on Deplomo? ## Python hosting: cloud options for developers Choosing a Python host can be challenging for developers, data teams and bot builders. Frameworks and asynchronous services may need a long-running process, background tasks, database connections and external network access. Shared hosting options vary; Deplomo offers container-based deployment, while CPU, RAM, storage, runtime and process limits depend on the selected package and configuration. ### What is Python hosting, and how does it differ from traditional shared hosting? Many Python web apps built with Django, FastAPI or Flask run as long-lived application processes that handle requests and database connections. The exact setup depends on the framework and runtime. Some shared-hosting providers use Passenger or LiteSpeed modules. Support for persistent processes, long-running requests and WebSockets depends on provider limits; shared resource use can also affect performance. Python hosting with managed deployment options ### A VPS gives you root access but also requires server administration. Typical tasks include configuring Nginx as a reverse proxy, creating systemd services, setting firewall rules with UFW, configuring Gunicorn and Certbot, and monitoring availability. A managed Python platform may reduce server-administration work. If GitHub or GitLab deployment is available, connect a repository to use the configured build workflow. Dependency installation and rollout behavior depend on settings; deployments may interrupt service. A managed Python platform may reduce server-administration work. If GitHub or GitLab deployment is available, connect a repository to use the configured build workflow. Dependency installation and rollout behavior depend on settings; deployments may interrupt service. ### Python hosting for Telegram bots: connection requirements Telegram bots and automation apps use Telegram’s API. Libraries such as aiogram and python-telegram-bot need valid credentials and outbound network access. A Telegram bot needs valid credentials, outbound API access and appropriate timeout and retry settings. Test the connection from your chosen zone, monitor failures and follow Telegram’s policies. Hosting does not guarantee uninterrupted access to a third-party API. #### Why do Telegram bots need a long-running process? Bots using Long Polling keep a connection open to receive updates. The runtime must allow the process to run and reconnect; restart behavior depends on the deployment and health-check configuration. Monitor the bot to detect missed updates or failures. #### Webhook hosting with a custom domain and automatic SSL Telegram webhooks generally require a publicly reachable HTTPS endpoint with a valid certificate. Connect a custom domain where supported; SSL certificates are issued and renewed automatically via ACME. Configure DNS and the webhook endpoint, and verify current service availability. ### Python bot hosting with databases and application logs More complex bots may need to store conversation state, application data and transaction records. Review the available services and configure database access, logging and retention for your workload. - Redis for application state: Redis can store FSM data and conversation state when available and configured for your app. Performance and persistence depend on workload and service settings; arrange separate backups. - PostgreSQL and MySQL can store member, order and message records. Capacity, persistence and backup options depend on the selected database service and its configuration. - Store Telegram bot tokens and service keys in the dashboard’s `Environment Variables` settings where available. Do not commit secrets to Git, and review who can access them. - Review application output and debug messages in the console where logging is available. Logs can help you investigate errors; they do not identify or fix every issue automatically. ### Python hosting for Django, FastAPI and Flask Python web apps can use the WSGI or ASGI interface, depending on the framework and server configuration. #### Deploying Django applications Django apps can use Gunicorn where supported. Configure `collectstatic` as part of the build, and use a persistent volume for the `media` directory where available. Check storage, backup and update behavior; Django Channels support depends on the runtime and configuration. #### Running FastAPI applications FastAPI apps commonly use Uvicorn and an event loop. The number of concurrent requests a deployment can handle depends on the app, package resources, worker configuration and workload. #### Flask for focused web services Flask can suit focused services, text-processing tasks and web scraping. Choose a package based on its published resource limits and your workload. ### Background tasks with Celery Applications can move work such as email delivery, image processing or model tasks to a background queue. Celery can schedule and distribute those jobs when configured with a supported broker and worker. Where supported by the runtime and package, you can configure separate web, Celery worker and Celery Beat processes. These may connect to Redis or another supported broker; resource use and process behavior depend on configuration and workload. ### Troubleshoot pip install and external service access Packages such as PyTorch, TensorFlow, OpenCV, NumPy and Cryptography can require substantial downloads or native compilation. Check the Python version, platform compatibility and build resource limits. External AI APIs also require valid credentials and supported access. Configure the package registry, lockfile and credentials needed by your project. Inspect build logs for download or compilation failures, and verify external API connections separately in the running application. Provider policies and service availability still apply. ### Compare cloud Python hosting, shared hosting and VPS The table summarizes common operational differences. Actual features, limits and requirements depend on the provider, package and project configuration.
| Technical feature | Cloud Python hosting on Deplomo | Python shared hosting (cPanel) | Unmanaged VPS |
|---|---|---|---|
| Isolation and resource allocation | Container-based deployment; CPU and RAM depend on the selected package | Shared resources; limits depend on the provider and package | Virtual machine; resources and isolation depend on the provider and package |
| Telegram bot process availability | Configure and test the bot’s API connection | Processes may be stopped when provider runtime or resource limits are reached | An external server or proxy may be needed, depending on network and API access policies |
| ASGI server compatibility | FastAPI, Uvicorn and Django Channels, subject to runtime and configuration compatibility | Passenger support and persistent-process limits vary by provider | Compatibility depends on the host, supported version and configuration |
| Installing large pip packages | Package downloads from the configured registry | Package access and shell tools depend on the host | Manual proxy or DNS configuration may be needed, depending on the host and network requirements |
| Deployment method | Git-based deployment may be available; check current integration and configuration | Manual upload of files via FTP or a file manager | May require shell scripts and manually configured webhooks |
| Background tasks and Celery | Celery Worker and Beat processes can run where supported; runtime, resource and availability limits apply | Processes may stop when the provider’s runtime or resource limits are reached | May require a process-management tool such as Supervisor |
| SSL certificate | Free, automatic issuance and renewal | May require paid plugins or manual configuration, depending on the provider | VPS setup may require configuring and maintaining Certbot or another certificate tool |
| Pricing model | Fixed monthly EUR package pricing | Contract terms and refund conditions vary by provider; review them before subscribing | A fixed monthly charge applies to the selected package, regardless of actual usage |