A clear runtime model for your Python backend.
Separate your FastAPI, Django or Flask backend into HTTP serving, data access and background work.
What matters for your application
FastAPI REST APIs for mobile / web clients
Define Python and package versions in project files.
Django consoles and business applications
Specify the WSGI / ASGI entry point, port and start command.
HTTP interfaces for data-processing services
Move long analysis tasks to workers and separate temporary from persistent files.
Where it fits
Separate your FastAPI, Django or Flask backend into HTTP serving, data access and background work. The correct runtime command depends on your framework.
- FastAPI REST APIs for mobile / web clients
- Django consoles and business applications
- HTTP interfaces for data-processing services
Its place in your application
A Python application handles requests through a WSGI or ASGI server. Long data-processing work belongs outside HTTP requests. Package and system dependencies should install reproducibly.
Before you begin
Choose services around the actual needs of your application. Include these points in your development and release plan.
- Define Python and package versions in project files.
- Specify the WSGI / ASGI entry point, port and start command.
- Move long analysis tasks to workers and separate temporary from persistent files.
Common questions
Can I use a development server in production?
Development servers are for local debugging. Prepare a framework-appropriate WSGI / ASGI server, process supervision and health checks for production. Live Python execution is not available yet.
Can I provision a live resource now?
Not yet. New registration and customer allocation are closed on the live site. Product guides are published; local development simulation does not create real services.