Frameworks

Python on Stackap

Stackap has no Python support of its own: it generates images only for Node-based projects and static sites, so a Python app can run only from a Dockerfile you provide.

How Stackap recognizes Python

Detection reads package.json and the files at the root of the repository. There is no check for requirements.txt, pyproject.toml or any Python framework, so a Python project without a Dockerfile is refused with a stated reason, and whatever was live keeps serving.

What Stackap builds

If your repository contains a Dockerfile, Stackap builds and runs it instead of generating anything. A Python web app can therefore run, in principle, as long as the image starts a server that listens on the port in the PORT environment variable, runs as an unprivileged user, and answers a health request.

Everything else on the platform is language-neutral: the database, the environment variables, the domains, the logs, the backups and the rollbacks do not depend on what the container runs.

We have not built a Python app on Stackap, so this is a description of how the Dockerfile path works for any language, not a tested Python recipe.

What a Python project needs

• A Dockerfile at the root of the repository.
• An image that listens on PORT, not a fixed number.
• A route that answers a health check, with the port and path set in project settings if they differ from the defaults.
• Database access through DATABASE_URL.

Verification status

Not tested with Python. The Dockerfile path itself is exercised: a repository that brings its own Dockerfile is built from it, and this very site is deployed that way.

Early-access scope

• Python is not a supported language today, and we will not list it as one until a real app has been served.
• No generated image means no dependency caching and no help from detection when a build fails.
• The container has no persistent disk and no second process alongside the first.
• Workers with no HTTP port cannot pass a health check yet.

Questions

Last updated 2026-10-03.