Deploy Flask on Kubernetes

Deploy Flask applications on Kubernetes with Wodby’s managed Flask stack. Start from a reusable application setup, keep environments consistent, and ship lightweight Python web apps, APIs, and internal tools without rebuilding the delivery platform around each project.

Start with a managed Flask stack

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

Keep application services organized

Run lightweight Python web apps, APIs, and internal tools 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 Flask deployment does on Wodby

A Flask deployment builds your repository, or the Flask boilerplate, with the service's Dockerfile and starts it under Gunicorn. Flask itself is not part of the image, so the build relies on your requirements file.

Application factories are supported

Which application Gunicorn loads is set on the app service. Change it when the application object is not where the default expects it, for instance to call an application factory.

A repository Dockerfile replaces the default

If the repository ships a Dockerfile, the build uses it in place of the one the service provides. From that point your file is responsible for installing every dependency.

Debug only in dev environments

The Flask debug flag is set in dev-type environments and nowhere else. Wodby sets no other Flask variable, so all remaining configuration comes from your code or from variables you add.

Code reads the connection details

Flask never picks up the database, Valkey, or mail variables automatically. Your code reads them, and it has to cope with one being absent while its link or service is turned off.

Saving reloads in a workspace

Within a development workspace Gunicorn reloads as soon as a Python file is saved. A change to the dependencies needs workspace preparation to be run once more.

Read the Flask stack guide for setup steps, settings, and limits.

Bring an existing application

Plan your Flask 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.

Flask migration planning prompt
Load Wodby’s migration guidance. Inspect this Flask 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 Flask

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

A practical fit for Flask workloads

  • Deploy lightweight Python web apps, APIs, and internal tools 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 Flask 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 Flask deployment works on Wodby

  1. 1

    Choose Wodby Cloud, managed Kubernetes, or a self-hosted Kubernetes setup on your own servers.

  2. 2

    Create a new app from the Flask stack and its boilerplate, then connect your repository.

  3. 3

    Configure services, domains, environment variables, persistent volumes, and databases as needed.

  4. 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, internal tool teams, and small services

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

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

Still choosing where to run it? Compare the options on the Flask hosting page.

Start deploying

Want to launch Flask with less setup overhead?

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

Stack-specific feature

Start from the Wodby Flask boilerplate

The Flask boilerplate gives small Python projects a working baseline for the Wodby stack, including the repository and deployment setup needed to get started.

The primary Python service serves Flask with Gunicorn, providing a production-oriented runtime without adding framework complexity.

Hosting options

Run your apps where it suits you

In your own cloud account, on a server you already rent, or on Wodby Cloud. The stacks and the deployment workflow are the same on all three, and Wodby maintains the cluster.

Lowest cost

Kubernetes on your own server

Use a dedicated server or VM you already rent, from Hetzner, OVH, or any other host. Wodby installs Kubernetes on it, keeps it up to date, and deploys your apps.

  • No managed control plane to pay for
  • One command installs Kubernetes on the server
  • Join more servers as worker nodes when you need capacity
  • Operating system updates install when you choose
Explore self-hosted Kubernetes

We handle everything

Wodby Cloud

Deploy without a cloud account or a server of your own. Wodby creates and operates the cluster, and you pay for the nodes and storage you run.

  • Nothing to connect or set up before your first deploy
  • A free demo cluster to try the workflow first
  • Scales between the node counts you set
  • The same stacks and deployment workflow as your own cluster
See Wodby Cloud

Connect the services your apps already use

An integration links Wodby to an account you already have, such as your Git provider, a storage bucket for backups, or an API your app calls.

Connected once
Set up a service once and reuse it across your apps.
Out of your code
Credentials stay out of your repositories and are managed in one place.
Per environment
Override any value for each environment.
Stack preview

Flask stack preview

Stack serviceBase serviceRole
Python
Python (Flask)Primary
PostgreSQL
PostgreSQLDisabled by default
Valkey
ValkeyDisabled by default
Mailpit
MailpitDisabled by default
OpenSMTPD
OpenSMTPDDisabled by default
Gotenberg
GotenbergDisabled by default
Cloud PostgreSQL
Cloud PostgreSQLDisabled by default
OpenTelemetry Collector
OpenTelemetry CollectorDisabled by default

Keep moving

Explore the Flask setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch Flask, 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 Miller
    Eighty Options
    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
    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.

Get started

Ready to deploy Flask?

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

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