Deploy Python
Deploy Python applications with Wodby’s managed Python stack. Start from a reusable application setup, keep environments consistent, and ship WSGI web apps, APIs, and internal services without rebuilding the delivery platform around each project.
Start with a managed Python stack
Use a ready-to-run Python stack and boilerplate instead of assembling the runtime, supporting services, and deployment workflow from scratch.
Keep application services organized
Run WSGI web apps, APIs, and internal services with clear service boundaries and environment configuration that stays consistent across deployments.
Use one workflow for delivery and operations
Keep CI/CD, routes, certificates, backups, and scaling controls in the same Wodby workflow.
Build and release
What a Python deployment does on Wodby
A Python deployment turns your repository, or the Python boilerplate, into an image and starts it with Gunicorn. The service's Dockerfile only installs your requirements file, so everything else about the build is yours to define.
Name your WSGI callable
Tell the app service which module and callable Gunicorn should load. The default assumes one particular project layout, so most applications set this value once and leave it.
No start command to write
The container launches Gunicorn by itself, with a configuration generated at start. A Gunicorn config file committed to the repository is not read, and Gunicorn has to be listed in your dependencies.
Links add the connection variables
With the default selection no connection variables exist at all. Enabling a database, Valkey, or a mail service adds the variables for its link, and your code is what reads them.
Workspace installs from a lock file
In a development workspace, setup installs dependencies from a uv lock file when the repository has one and from the requirements file otherwise. One of the two files has to exist.
Reload during development
The workspace server runs Gunicorn in reload mode and does not use the generated configuration or the tuning variables. Changing variables or linked services still takes a deployment.
Read the Python stack guide for setup steps, settings, and limits.
Bring an existing application
Plan your Python migration with your agent
Give your coding agent access to your repository and connect Wodby through MCP. Ask it to map your app to maintained services and flag what needs to change before deploying.
Review the plan first, then approve an isolated staging deployment. Production data transfer and cutover need separate approval. MCP access does not itself grant access to your repository.
Use get_wodby_guidance to load the Wodby migration workflow. Inspect this Python application repository and propose a Wodby deployment plan. Identify the runtime, database, background jobs, persistent files, and required secret names without revealing values. List missing information and plan an isolated staging deployment. Do not create resources, transfer production data, change DNS, or deploy anything yet.A modern deployment model for Python
Python teams benefit from repeatable builds, predictable environment configuration, and a clean way to operate application and supporting services together.
Wodby packages that model as a managed stack on Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes, so teams can standardize delivery without maintaining a separate platform for every Python project.
A practical fit for Python workloads
- Deploy WSGI web apps, APIs, and internal services from a reusable stack and boilerplate.
- Keep application, worker, database, and cache services separated where the stack needs them.
- Use consistent configuration across development, staging, and production environments.
- Reduce custom work around releases, routes, certificates, backups, and scaling.
What you get with Wodby
- Managed Python stack for modern container-based deployments
- Built-in CI/CD with image builds, deployment history, and rollback attempts
- Controlled automatic updates for stack services, app environments, and infrastructure
- Automated backups and imports for safer releases and migrations
- Managed routes, endpoints, and domain setup
- App service controls for settings, resources, links, volumes, actions, and terminal access
- Open, portable infrastructure via Wodby’s platform model
How Python deployment works on Wodby
- 1
Choose Wodby Cloud, managed Kubernetes, or a single-server self-hosted Kubernetes setup.
- 2
Create a new app from the Python stack and its boilerplate, then connect your repository.
- 3
Configure services, domains, environment variables, persistent volumes, and databases as needed.
- 4
Deploy through the built-in CI/CD workflow and scale application or worker services when demand changes.
Read more about stack management in our documentation.
Suitable for Python developers, backend teams, and small product teams
This setup is designed for teams that want to ship Python applications with repeatable environments and less platform work around every project.
Wodby provides the managed Python stack and delivery workflow while preserving Kubernetes-based infrastructure choices as requirements grow.
Still choosing where to run it? Compare the options on the Python hosting page.
Start deploying
Want to launch Python with less setup overhead?
Start with Wodby's managed Python stack, connect your repo, and handle deployments, environments, and operations in one place.
Start from the Wodby Python boilerplate
The Python boilerplate is a working project for the Python stack, with the repository layout and requirements file the image build expects.
Deploy it first to see the workflow end to end, then connect your own repository and point the app service at your application.
Choose the hosting model that fits your team
Run Wodby on your own managed Kubernetes, on a budget self-hosted Kubernetes server, or on Wodby Cloud. Wodby maintains the cluster on all three.
Managed Kubernetes in your cloud account
Keep infrastructure in your own cloud account. Wodby provisions the cluster through AWS, GCP, DigitalOcean, Azure, or another supported provider and keeps it up to date.
View managed KubernetesKubernetes on your own server
Use your own dedicated server or VM for the lowest cost. Wodby installs Kubernetes, keeps it up to date, and deploys your apps; you keep the server’s operating system updated.
Explore self-hosted KubernetesWodby Cloud
Use Wodby Cloud when you want the cluster hosted by Wodby instead of in your own cloud account or on your own server.
See Wodby CloudIntegrations
Keep third-party integrations organized and under control across all of your apps and environments
Connect services once and reuse them across your apps. Keep credentials out of repositories, manage configuration centrally, and override values for each environment.
Connect the services your apps already use
Python stack preview
| Stack service | Base service | Role |
|---|---|---|
| Python | Primary | |
| PostgreSQL | Disabled by default | |
| Valkey | Disabled by default | |
| Mailpit | Disabled by default | |
| OpenSMTPD | Disabled by default | |
| Gotenberg | Disabled by default | |
| Cloud PostgreSQL | Disabled by default | |
| OpenTelemetry Collector | Disabled by default |
Keep moving
Explore the Python setup, then start your own deployment
Once you've reviewed the stack structure, create an account to launch Python, connect your repository, and keep delivery inside the same workflow.
Trusted by developers and businesses worldwide since 2015
Wodby is a reliable cloud infrastructure partner for your business.
See what our customers say about their experience with Wodby.
We moved our Drupal hosting to use Wodby and changed our development workflow to use Docker at the same time. Now we can concentrate on Drupal development and we're not losing time configuring servers etc. When a site needs additional resources or hosting in a different region we can be way more responsive as deploying a new instance takes no time at all.
Tony MillerEighty Options
Wodby’s innovative infrastructure helped us to increase the speed and simplify our app deployment, while also leaving us the freedom of handling our hosting and not locking us on a specific pattern. We are now much more robust for future growth and will be able to innovate faster.
Martin Normann LundRamsalt Lab
Frequently Asked Questions
Have questions? We've got answers. If you don't see your question here, feel free to reach out.
Get started
Ready to deploy Python?
Choose Wodby Cloud, managed Kubernetes, or your own server, then deploy stacks with CI/CD, backups, SSL, integrations, and environment management in the same platform.
- Run the same stack workflow on Wodby Cloud, managed Kubernetes, or your own server
- Deploy app environments for production, staging, previews, and development
- Use Wodby CI or your existing pipeline with the Wodby CLI
- Keep backups, certificates, integrations, and access control in the platform
Start for free
- 10 app services
- 30 minutes of integrated CI
- 5 GB of private registry
- Stacks & integrations
- Technical domains with SSL