New — Iris AI drafts your firewall, routing & rate-limit rules. Explore AI features →
Expose · Deploy · Protect

Ship anything to the edge. Secure every request.

Tunnel a service from your laptop or Kubernetes, or deploy the whole app — static, full-stack, Docker, WordPress, functions. Every request passes the same edge: WAF, bot protection, edge login and rate limits, drafted by Iris AI and approved by you.

Zero inbound ports EU & US edge HTTP/3 Iris AI & MCP
# a service on your laptop, a server or Kubernetes
$ ngris http 3000
✓ online → https://calm-fox.ngris.dev → localhost:3000
# every request, live
GET/20011ms
POST/webhooks/stripe20042ms
GET/api/orders?page=220023ms
POST/login4034ms
no inbound ports · HTTP, TCP & UDP · replay any request
# or deploy the whole app
$ git push origin main
  Next.js (SSR) detected → runs as a managed backend behind the edge
✓ Built · ✓ Live → https://shop.ngris.dev
# every branch gets a preview
$ git push origin feature/checkout
✓ Preview → https://feature-checkout-a1b2c3.ngris.dev
# bad deploy? one command back
$ ngris apps rollback 91ad…
static · full-stack · Docker · WordPress · functions
# one rule in front of a tunnel or an app
rule_type: challenge  # Under Attack mode
config: { mode: smart, interaction: checkbox }
# what each visitor gets
95Chrome, home networkpass
65Chrome on a cloud VMcheck
5python-requests403
15Googlebot, verified IPpass
bot score · JA3/JA4 · WAF · edge login · rate limits
edge · EU · USHTTP/1.1 · HTTP/2 · HTTP/3

Runs your stack

Next.jsNuxtSvelteKitAstroReactViteNodePythonGoDockerWordPressKubernetes

Every request takes the same path.

Expose a service you already run, deploy the next one, and protect both on the same edge.

01 · EXPOSE

Tunnel what you run today

One outbound connection from your laptop, server or cluster. Nothing to open, nothing to forward.

visitors · HTTPSngris edgeTLS, HTTP/3your policyinspectortunnel · agent dials outyour network · no open portsngris agentlocalhost:3000k8s svc/web Tunnels →
02 · DEPLOY

Deploy what you build next

Push a repo or a folder. Ngris builds it and serves the front end and the backend on one URL.

git push origin mainbuild · Next.js detectedimage scanned & signedngris edgepreview URLsrollbackyour domain//api/*your app · one URLstatic front endbackend container App hosting →
03 · PROTECT

Decide every request at the edge

One policy checks each request before it reaches you, whether it goes to a tunnel or an app.

every requestngris edgebot scoreWAFedge loginrate limits200to origin302to sign-in403blockedsame rules for a tunnel or an app Security at the edge →

Every request passes the same edge.

Security runs before your origin sees a byte, the same way for a tunnel to your laptop and for an app on ngris.

  • Bot protection. A bot score on every request and an Under Attack challenge that verified crawlers pass. More
  • WAF & firewall. A built-in WAF baseline plus your own rules; allow, block or challenge by IP, country or ASN.
  • Edge login. OAuth/OIDC, user accounts with roles, JWTs, API keys and mTLS, with no code changes. More
  • Rate limits. Per IP, header, cookie or JWT claim, per route or account-wide.
edge decisions · shop.example.com
GET/admin no session302edge login
POST/search?q=' OR 1=1--403WAF
GET/products bot score 3403bot
POST/api/cart 601st req/min429rate
GET/products bot score 96200origin
GET/robots.txt Googlebot, verified200origin

Debug in minutes, not days.

The Request Inspector captures inbound traffic with searchable payloads and lets you replay with overrides. Built-in redaction keeps secrets safe.

Full-text search

Search across headers and JSON bodies with regex support.

GDPR-friendly redaction

Automatic secret masking and retention controls (7–30 days).

Replay to dev/staging

Editable payloads and headers — replay to any environment.

Alerts to Slack & Discord

Get notified when requests fail or spike unexpectedly.

Request Inspector
POST/api/webhook200128ms
POST/api/data20164ms
GET/api/users?page=220031ms
PATCH/api/config42912ms
DELETE/sessions/8f2a2049ms
GET/healthz2003ms

An AI that runs your edge — with you in charge.

Ask Iris in the dashboard, or drive everything from Claude Code and any MCP client. Writes always wait for your OK.

Iris in the dashboard

Describe the rule; Iris drafts it, shows what it would have blocked in your real traffic, and applies it only when you approve.

you  block SQL injection and rate-limit /api to 100/min
iris  WAF · block SQLi  +  rate-limit /api → 100/min
      last 24h: 2 requests would be blocked · 0 legitimate
[ Approve & apply ] [ Cancel ]

Your AI assistant, over MCP

340+ tools over the public API: expose a port, deploy, add a rule, find and replay a failed request — never more than you could do yourself.

$ claude mcp add --transport http \
    ngris https://mcp.ngris.com/mcp
# then just ask
› why is checkout returning 502? replay the last one

The edge underneath.

Built and run by us, from the proxy up: every protocol in, your code wherever it runs.

browsersAPIs & webhooksTCP / UDP clientsngris edgeEU · US regionsTLS · HTTP/1.1, 2, 3TCP · UDP · WebSocketyour policy · inspectorto your codelaptopagentserveragentKubernetesoperator + agentapps on ngrisgVisor sandboxwhere your code runswho connectsbrowsersAPIsTCP/UDPngris edgeEU · US · HTTP/1.1, 2, 3 · TCP · UDPwhere your code runslaptopagentserveragentKubernetesoperator + agentapps on ngrisgVisor sandbox

Runs everywhere you deploy.

One egress-only agent for every OS and runtime, plus a REST API and OpenAPI spec to drive it from code.

macOS
brew install ngris-edge/homebrew-tap/ngris
Native binary for Apple Silicon & Intel.
Linux
curl -fsSL https://ngris.com/install.sh | sh
Static binary; systemd unit for long-running tunnels.
Windows
winget install Ngris
Signed installer, or a portable single executable.
Docker
docker pull ghcr.io/ngris-edge/ngris
Sidecar image — drop the agent into any compose stack.
Kubernetes
helm install ngris-operator oci://ghcr.io/ngris-edge/charts/ngris-operator
Operator & CRDs — egress-only tunnel from your cluster, zero inbound ports.
REST API
https://api.ngris.com
Versioned REST API — manage endpoints, domains & firewall as code.

Everything else, answered.

Still stuck? The docs go deeper, or reach the team at sales@ngris.com.

The ngris agent on your machine, server or cluster opens an outbound, encrypted connection to the ngris edge, so you never open a firewall port. Visitors reach a public HTTPS URL; the edge terminates TLS, applies your policy and sends each request down the tunnel to your local service.

Yes. Deploy a static site, a full-stack app, a Docker or Go, Node or Python backend, WordPress or a serverless function from GitHub, GitLab or the ngris CLI. Ngris detects the framework and builds it, every deploy can get a preview URL, and you can promote or roll back with one command.

Yes. Export a standard (request) => Response handler on Node.js 24. The function scales to zero when idle and the edge starts it again on the next request. Separately, edge functions (in beta) run small JavaScript handlers on the edge itself, in front of any endpoint.

An API gateway sits between clients and your services and handles routing, authentication, rate limits and observability. Ngris does that per endpoint, for tunnels and hosted apps alike, and adds a WAF, bot protection, edge login, a request inspector with replay, and Iris, an AI that drafts rules for you to approve.

Traffic between the agent and the edge is encrypted, and the edge can check every request before it reaches you: WAF, bot score, IP and geo rules, rate limits and edge login. Hosted apps run in gVisor sandboxes, captured traffic can be redacted, and account actions are written to an audit log.

A live view of every request to an endpoint, with headers and body. Search and filter it, and replay a request, edited if you like, to check a fix.

Yes. Connect Cloudflare, Route 53, DigitalOcean, Namecheap, cPanel or Virtualmin and Ngris creates the records and issues and renews a wildcard certificate. With any other DNS host, add a TXT record and a CNAME to cname.ngris.io and upload your own certificate.

Yes. Ngris serves production traffic from edge regions in the EU and the US over HTTP/1.1, HTTP/2 and HTTP/3, with automatic TLS, health checks, alerts and the same security edge on every endpoint.

Ship anything to the edge. Secure every request.

Create an account and launch your first endpoint in under a minute. No config files, no credit card, no friction.

Sign Up Free View Docs
Ask an AI to summarise this page