The mantis needs a public-reachable URL. Pick the option that matches where you want to run it. For any public option, also see public edge limits for rate-limit and DDoS guidance, and backups for Postgres backup strategies.

​
Quick-pick: A vs B vs C

Both B and C give you a public HTTPS URL for mantis running on your own hardware. The differences:

​
Edge variant

The stateless mantis-edge Cloudflare Worker is a separate concept. It runs on Cloudflare’s edge with no DB, and URLs decrypt purely from the Worker’s secret. See mantis-edge deployment for the Worker setup.

Local Docker

Run Mantis locally with Docker for evaluation or development.

Deploying Mantis with Tailscale

Expose Mantis through Tailscale Funnel with simple or split public routes.

Deploying Mantis with Cloudflare Tunnel and Access

Expose a local Mantis instance through Cloudflare Tunnel and optional Access SSO.

Railway deploy

Deploy Mantis on Railway with a long-running container and Postgres add-on.

Fly.io

Deploy Mantis to Fly.io with one command, Postgres, and safe proxy defaults.

Render

Deploy Mantis on Render with a Blueprint and managed service.

Public edge limits

Recommended edge URL, body, and rate limits for public Mantis routes.

Backups and retention

Back up and restore the Postgres database that stores Mantis data.

Deploying mantis-edge

Deploy the stateless Cloudflare Worker version of Mantis.