Supported stacks

Flask hosting
on Shipped.

Take the Flask app you built and make it available to real users. Keep the routes and extensions you chose, with infrastructure handled.

Turn your local app into a service

Package Flask with a production WSGI server and the application entry point or factory your project uses. Deploy it as a Shipped web service with production settings. Your server handles the Flask application, while Shipped connects the public URL, custom domain, and HTTPS around it.

Choose the pieces your app actually needs

Flask lets you choose database libraries, authentication, and other extensions for your application. Connect those pieces to PostgreSQL, object storage, or external services without adopting a new application framework. Use secrets for connection settings and a separate staging configuration for development data and integration credentials.

Keep longer jobs out of the response

A report, image conversion, or large import can continue in a worker after the web app accepts a request. Store progress and results where the Flask app can retrieve them. Logs from the web service and worker help explain failures without relying on a terminal on your own machine.

A little more detail

Questions about Flask?

Should I use flask run for the deployed app?

Use a production WSGI server. Flask’s built-in development server, debugger, and reloader are intended for development rather than public deployment.

Does a Flask app need a database?

Only if its behavior needs persistent data. A small integration endpoint may not need one; account records, saved reports, and durable job state usually do.

From your workspace to the web

Ready to ship your app?

Start shipping