Do I need to have an account on a cloud provider to use Wodby?

You can connect your own managed Kubernetes provider or use one dedicated server for self-hosted Kubernetes. Alternatively, you can use Wodby Cloud when you do not want the cluster in your own cloud account or on your own server.

Can I use Wodby with a dedicated server?

Yes. Wodby supports budget single-server self-hosted Kubernetes setups with K3s, a lightweight open-source Kubernetes distribution, when you do not need Kubernetes scaling.

I couldn't find my specific application stack, how do I start?

Start with the closest pre-configured stack and customize it, or build a stack from managed services. You can also contact Wodby to request a new stack.

Will I be vendor locked-in to Wodby?

No. Wodby is built on open standards like Kubernetes. You can disconnect your cluster and keep running your apps, but Wodby-managed tasks stop.

I have a small website (PHP, MySQL). How much would it cost? What if I deploy 10 of them?

Pricing is based on total app services. One site with Nginx, PHP-FPM, and MySQL is 3 services and falls under the $48/month minimum tier. Ten such sites total 30 services and cost $60/month. Extra CI/CD minutes and registry storage are billed separately.

Deploy Django

Deploy Django applications with Wodby’s managed Django stack. Start from a reusable application setup, keep environments consistent, and ship Python web apps, APIs, and background tasks without rebuilding the delivery platform around each project.

Start with Wodby View Django stack

Start with a managed Django stack

Use a ready-to-run Django stack and boilerplate instead of assembling the runtime, supporting services, and deployment workflow from scratch.

Keep application services organized

Run Python web apps, APIs, and background tasks 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.

A modern deployment model for Django

Django 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 Django project.

A practical fit for Django workloads

Deploy Python web apps, APIs, and background tasks 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 Django 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 Django 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 Django 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 product teams, API developers, and SaaS projects

This setup is designed for teams that want to ship Django applications with repeatable environments and less platform work around every project.

Wodby provides the managed Django stack and delivery workflow while preserving Kubernetes-based infrastructure choices as requirements grow.

View pricing Explore infrastructure features

Start deploying

Want to launch Django with less setup overhead?

Start with Wodby's managed Django stack, connect your repo, and handle deployments, environments, and operations in one place.

Start with Wodby View Django stack

Stack-specific feature

Start from the Wodby Django boilerplate

The Django boilerplate provides a working project baseline for the managed stack, so teams can begin with repository structure and deployment wiring already in place.

Django, PostgreSQL, and Valkey are enabled by default, with database and Celery broker connections supplied through stack service links.

View the Django boilerplate on GitHub

Hosting options

Choose the hosting model that fits your team

Run Wodby on your own managed Kubernetes, on a budget self-hosted Kubernetes server, or on fully managed Wodby Cloud.

Managed Kubernetes in your cloud account

Connect AWS, GCP, DigitalOcean, Azure, or another supported provider and let Wodby provision and manage the cluster setup in your own account.

View managed Kubernetes

Budget self-hosted Kubernetes

Run a single-server self-hosted Kubernetes setup with K3s when budget hosting matters more than Kubernetes scaling.

Explore self-hosted Kubernetes

Fully managed Wodby 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 Cloud

Integrations

Keep third-party integrations organized and under control across all of your apps and environments

Connect popular services once, attach them where they are needed, and manage configuration centrally instead of chasing secrets and variables across projects.

Control integrations without losing flexibility

Organize third-party connections in one place across all of your apps.
Keep credentials out of repositories and under tighter operational control.
Override values per environment without rebuilding or reworking each app.

See all integrations

OpenAI

View integration

Bring API keys and model settings into your apps without scattering secrets.

Anthropic

View integration

Standardize AI credentials once and reuse them across environments.

Intercom

View integration

Manage customer messaging credentials centrally and reuse them across environments.

Sentry

View integration

Attach monitoring variables cleanly to services without editing code.

Stripe

View integration

Keep payment-related secrets controlled and consistent per environment.

Mailchimp

View integration

Keep email marketing keys and audience settings consistent without scattering config.

Stack-specific feature

Celery workers and post-deploy tasks included

A Celery service runs the same application image as the web service, keeping asynchronous tasks separate without introducing another build.

Post-deploy actions run database migrations and collect static files, while the Django secret key is generated per app and debug mode is limited to development environments.

Stack preview

Django stack preview

Stack service	Base service	Role
Python Celery	Python (Django)	Primary
Valkey	Valkey	Required
PostgreSQL	PostgreSQL	Required
Mailpit	Mailpit	Disabled by default
Cloud PostgreSQL	Cloud PostgreSQL	Disabled by default
OpenSMTPD	OpenSMTPD	Disabled by default
Gotenberg	Gotenberg	Disabled by default

See full stack service table

Keep moving

Explore the Django setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch Django, connect your repository, and keep delivery inside the same workflow.

Create account Check pricing

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 Miller
Eighty 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 Lund
Ramsalt Lab

FAQ

Frequently Asked Questions

Have questions? We've got answers. If you don't see your question here, feel free to reach out.

Alternatives

Comparing Wodby with alternatives

Wodby is usually the stronger fit when you need complete application stacks, persistent workloads, integrated operations, and flexibility across Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes.

Get started

Ready to deploy Django?

Choose Wodby Cloud, managed Kubernetes, or K3s, 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 K3s
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

No credit card required

$0/month

10 app services
30 minutes of integrated CI
5 GB of private registry
Stacks & integrations
Technical domains with SSL

Create free account

Upgrade when you need more capacity