Managed backends: run Go, Node, Python, or any Dockerfile on the edge

A managed backend runs your server-side application on the ngris edge at a public HTTPS URL, behind the same policy engine as the rest of your account. Managed backends are available on paid plans.

What you can run

• Auto-detected runtimes — bring a Go, Node, or Python app and ngris detects the runtime and builds it for you.
• Any Dockerfile — if you have a Dockerfile, ngris builds that image and runs it as your backend, so anything that packages into a container works.

Your app runs as a long-running managed service that ngris keeps online and serves over HTTPS. There is no per-request serverless / FaaS model — these are persistent backends, not functions.

Deploy a backend

In the dashboard, create an application and choose a git repository (or connect one). ngris inspects the repo: if it finds a supported runtime or a Dockerfile, it builds and runs it as a managed backend and returns a public URL.

# Point ngris at a repo that contains, for example, a Dockerfile
# or a Go / Node / Python project. Push to deploy:
git push origin main
# ngris builds the image and runs it as a managed backend on the edge

Environment variables and secrets

Set per-app environment variables and encrypted secrets in the application settings; they are injected into your backend at runtime. Values marked as secrets are masked in the UI.

Add a database

If your backend needs storage, attach a managed database and ngris wires a dedicated MariaDB in as {DATABASE_URL}. See Managed database.

Policy and custom domains

A managed backend is served from the ngris edge, so it inherits your firewall, WAF, rate limits, and traffic policies, and can be published on a custom domain.