Deploy FastAPI on Your Own Server
Deploy FastAPI applications with Uvicorn ASGI server and managed PostgreSQL. Your OpenAPI docs and Swagger UI work out of the box.
Quickstart
From your project root, deploy with your preferred package manager:
npx @temps-sdk/cli up
Temps detects your requirements.txt and installs dependencies. There is no FastAPI-specific handling and no Uvicorn command is generated for you — the build starts python main.py if a main.py is present, or the entry point declared in pyproject.toml. Put your Uvicorn call in one of those, or set the start command explicitly on the deployment. Once running, your /docs (Swagger UI) and /redoc endpoints are accessible immediately.
What Temps handles automatically
| Feature | How Temps handles it |
|---|---|
| Install | pip install -r requirements.txt |
| ASGI server | Uvicorn with multiple workers |
| OpenAPI | /docs and /redoc served automatically |
| Migrations | Run alembic upgrade head via deploy hook |
| HTTPS | Let's Encrypt certificate, auto-renewed |
| Port | PORT env var injected, defaults to 8000 |
| WebSockets | Fully supported via Uvicorn |
Procfile
Define your start command in a Procfile at the project root:
web: uvicorn main:app --host 0.0.0.0 --port $PORT --workers 4
Alembic Migrations
To run migrations on every deploy, add a deploy hook in Project → Settings → Deploy Hooks:
alembic upgrade head
Environment Variables
npx @temps-sdk/cli environments vars set DATABASE_URL "postgresql+asyncpg://user:pass@host/db" -e production npx @temps-sdk/cli environments vars set SECRET_KEY "your-secret-key" -e production
Managed PostgreSQL and Redis
Add services from Project → Services → Add Service. Temps injects connection strings as environment variables automatically.
Platform behavior
These rules apply to every app deployed on Temps, regardless of framework.
The one requirement: your app must listen on the port in the PORT environment variable and bind to 0.0.0.0 — not localhost or 127.0.0.1. Temps runs your app in a container and routes traffic from the host, so an app bound to localhost only accepts connections from inside the container and will fail its health check.
Health checks
After your container starts, Temps sends HTTP GET requests to verify it is healthy before routing traffic to it.
- Path:
/(the root of your application) - Success: 2 consecutive responses with a 2xx or 3xx status code
- Timeout: 300 seconds (5 minutes) for the app to become healthy
- Retry interval: every 5 seconds
Connection errors while the app is still starting are retried without penalty. If the app returns 4xx or 5xx errors for 60 consecutive seconds, the deployment fails. Customize the check by adding a .temps.yaml to your repository root:
health:
path: /health
status: 200
interval: 30
timeout: 5
retries: 3/health endpoint that returns a simple 200. This avoids issues where / requires authentication or returns a redirect.Auto-injected environment variables
Temps injects these variables into every deployment automatically:
| Variable | Value | Description |
|---|---|---|
PORT | Resolved port | The port your app must listen on |
HOST | 0.0.0.0 | Bind address |
SENTRY_DSN | Auto-generated | Error tracking endpoint |
TEMPS_API_URL | Your Temps URL | Platform API endpoint |
TEMPS_API_TOKEN | Deployment token | Authentication for Temps SDKs |
OTEL_EXPORTER_OTLP_ENDPOINT | Your Temps OTLP URL | OpenTelemetry trace collection |
OTEL_SERVICE_NAME | Project name | Service identifier for traces |
You do not need to configure these manually. They are available in process.env (Node.js), os.environ (Python), os.Getenv (Go), and the equivalent in other languages.