Framework Frankfurt, Germany
Nodion recognizes FastAPI or Starlette in your dependencies, installs them with its Python buildpack and starts Uvicorn on your main.py or app.py. Migrations can run as a release step before each new version goes live, and the API runs in Frankfurt, next to a managed PostgreSQL database if you need one.
uvicorn main:app, one processfastapi[standard] includes it; with plain fastapi, add uvicorn yourself. Pin the Python version in .python-version, because a range picks the newest release. requirements.txt fastapi[standard] main.py and app.py contains FastAPI or Starlette and runs uvicorn main:app or uvicorn app:app on 0.0.0.0 and the PORT it sets. Answer / with a 200: it is the default health check path. main.py from fastapi import FastAPI
app = FastAPI()
@app.get("/")
def root():
return {"status": "ok"} app/main.py, there is no root file to find. Name the module yourself in a Procfile; the line replaces the default start command. Procfile web: uvicorn app.main:app --host 0.0.0.0 --port $PORT release: line runs once per build, after the build and before the new version starts. If it fails, the deploy stops and the running version stays live. Procfile release: alembic upgrade head DATABASE_URL on the next deploy. Mark API keys as secret, then push. allowed_hosts, so the middleware answers 400 and the release never goes live. Add an @app.middleware("http") function after it that returns 200 for /healthz (Starlette runs the middleware added last first), and set /healthz as the health check path in the app settings.web: uvicorn main:app --host 0.0.0.0 --port $PORT --workers 2 in a Procfile, or run more instances of the web process.DATABASE_URL starts with postgres://, which SQLAlchemy 1.4 and newer do not accept. Replace the scheme before you pass it on, for example with postgresql+psycopg:// for psycopg 3, which works for sync and async engines.DATABASE_URL, REDIS_URL or CLICKHOUSE_URL. release: line runs with every new build. Dockerfile apps, and redeploys or rollbacks to an earlier image, use a release command set on the app itself, which also takes precedence over the Procfile line. On static sites a release step runs in an image that holds only the built files. Not by default: Nodion starts one Uvicorn process. Add --workers 2 or more to your own web: line, or scale the web process to more instances.
The health check needs a 2xx or 3xx on /. An API without a root route answers 404, and TrustedHostMiddleware answers 400 to the internal address. Add a route, or set a path such as /healthz in the app settings and answer it before the host check.
Yes. Starlette in your dependencies gets the same Uvicorn default, which looks for app in main.py or app.py.
In the EU Central region in Frankfurt, Germany. Build, registry, the app and its databases, volumes, buckets, logs and metrics stay in that region, and Nodion's API and control plane are hosted in Germany. Nodion GmbH is based in Stuttgart.
Nodion provides the basis for it: Nodion GmbH is based in Stuttgart, Germany, in the Frankfurt region the app, its databases and volumes run in Germany, and you conclude the data processing agreement (DPA) under Art. 28 GDPR electronically in the dashboard. Whether your setup complies also depends on how you configure and use the app.
An app instance starts at 1 EUR per month. The setup in the cost box costs 3.50 EUR per month: App 2 EUR, PostgreSQL 1.50 EUR. Prices are net and billed per second, and you pick bigger sizes or more instances whenever you need them.
Yes. Every app gets a default hostname with HTTPS. Add your own domain on the app's Domains tab; the TLS certificate is issued and renewed automatically.
Earn up to 15 € in credit when signing up.
or with email
Product news, no spam. Unsubscribe anytime.
Successfully subscribed.