Ngris vs Netlify
Deploy from Git with previews and rollbacks, as on Netlify, and run more than the front end: backend containers, server-side rendering, WordPress and functions, with a managed database. Every app sits behind a WAF, bot protection, rate limits and edge login. An honest comparison: we only claim what our code ships today.
- Push to deploy
- SSR, Docker and functions
- Tunnels on the same edge
Choose ngris if you want
- Any Dockerfile, or a Go, Node or Python backend, next to your front end
- A managed database, backups and cron in the same app
- A login with user accounts and roles, without writing auth code
- Tunnels to your laptop or cluster through the same edge
- WordPress in one click
Where ngris is still maturing
- Edge locations in the EU and the US; apps run in our EU region
- Static builds don’t use a build cache yet
- Fewer plugins and integrations than Netlify
More than the front end
Netlify made git-push deploys of front ends easy. Ngris matches that workflow and runs the rest of the app behind a security edge.
Push, build, live
Connect GitHub or GitLab; every push builds, with preview URLs, promote and rollback.
App hosting →One URL, two origins
/api goes to your backend container, the rest is static at the edge, with a MariaDB database.
A security edge on every app
WAF, bot protection, rate limits and a login for your users, set per app, with no code changes.
Edge login →Ngris vs Netlify, feature by feature
A mark for ngris means it ships today. For Netlify we mark only facts from its own documentation, and the rows where Netlify is broader are marked too.
| Feature | Ngris | Netlify |
|---|---|---|
| Build and deploy | ||
| Framework builds with auto-detection | ||
| Deploy on push from GitHub or GitLab | ||
| Deploy a folder from the CLI | Drag and drop too | |
| Preview URLs, also per branch | ||
| Promote and instant rollback | ||
| Monorepo root directory and build overrides | ||
| Env vars and encrypted secrets | ||
| Build cache | Container builds | |
| Run the app | ||
| Server-side rendering: Next.js, Nuxt, SvelteKit, Remix, Astro | As a container | |
| Long-running backends: any Dockerfile; Go, Node, Python | Functions only | |
| Serverless functions that scale to zero | ||
| Edge functions | Beta | |
| Managed database | MariaDB | Netlify Database |
| Cron jobs | ||
| One-click WordPress | Not built in | |
| Performance and insights | ||
| Image optimization | ||
| Cookie-free web analytics | ||
| Speed Insights (Core Web Vitals) | Check planReal User Monitoring on Pro and Enterprise | |
| Skew protection | All plans | |
ISR-style edge caching (s-maxage) | ||
| Security at the edge | ||
| WAF with your own rules | Plus a built-in baseline | Check plan |
| Rate limiting | ||
| IP and geo rules | Firewall traffic rules | |
| Bot score and JA3/JA4 fingerprints | Check plan | |
| Under attack challenge | Check plan | |
| Private production and preview URLs | Password protection | |
| Login for your users: OAuth/OIDC, accounts, roles | No code changes | Netlify IdentityAdd its widget to your site |
| Mutual TLS (client certificates) | Check plan | |
| Beyond hosting | ||
| Tunnel a service you run yourself | Dev sessions onlynetlify dev --live | |
| Request inspector with replay | Check plan | |
| Kubernetes operator | 10 custom resources | Not built in |
| AI drafts firewall rules | Iris | Not built in |
| AI drafts every edge rule: firewall, rate limits, traffic policy, routing, alerts, error pages, edge functions | All 7 rule types | Via coding agents only |
| AI assistant that reads your account and applies changes after you confirm | Iris; can also add firewall rules by itself, with auto‑rollback | Code changes only |
| MCP server for AI assistants | 340+ tools | Netlify MCP |
| Edge locations worldwide | EU and US | |
| Plugins and integrations | Fewer | |
Ships today“Check plan”: we don’t claim a yes or a no. Netlify’s features and tiers change, so check netlify.com.
Move a project in a few minutes
Connect the same repository; the build is detected for you.
Create an app from your repo
Connect GitHub or GitLab in the dashboard or from the CLI. Use --type static for a static site and managed for server-side rendering.
ngris apps create shop --type managed --repo https://github.com/acme/shopCopy your environment variables
Add --secret and the value is stored encrypted and never printed back.
ngris apps env set STRIPE_KEY=sk_live_… --secretPoint your domain
Connect your DNS provider and ngris writes the record and a wildcard certificate, or add a CNAME to cname.ngris.io and upload your own. Every deploy still gets its own preview URL. Domains
Turn on the edge
Attach a WAF or rate limit, turn on bot protection or edge login, or ask Iris to write the rule.
Frequently asked questions
Is Ngris a good Netlify alternative?
Yes, if you want more than a front end. Ngris deploys from Git with previews and rollbacks, as Netlify does, and also runs long-running backend containers, server-side rendering, WordPress and functions, with a managed MariaDB database. Every app sits behind the same WAF, bot protection, rate limits and edge login as an ngris tunnel.
Can Ngris run a long-running backend?
Yes. Bring a Dockerfile, or a Go, Node or Python project, and Ngris builds it, scans and signs the image, and runs it as a container behind the edge. A full-stack app puts it behind your static front end on the paths you choose, /api by default.
How do I move a site from Netlify to Ngris?
Create an app and connect the same GitHub or GitLab repository, or upload the built folder with ngris deploy. Ngris detects the framework and runs the build. Copy your environment variables with ngris apps env set, adding --secret for secrets, then point your domain at the app with a CNAME to cname.ngris.io.
Does my site get a WAF and bot protection?
Yes. A hosted app is an ngris endpoint, so the Coraza WAF with its built-in baseline and your own rules, a bot score with an Under attack challenge, rate limits and edge login all work in front of it, set per app.
Where do Ngris apps run?
Static sites are served straight from the edge. Managed apps run in gVisor sandboxes in our EU region and are served from every edge region, in the EU and the US, over HTTP/1.1, HTTP/2 and HTTP/3.
Can I also expose services I run myself?
Yes. The ngris agent exposes a service on your laptop, a server or in Kubernetes through the same edge, and every rule you can put in front of a hosted app works in front of it too.
Related comparisons and guides
Ngris vs Vercel
The other front-end host, compared: builds, previews, backends and the security edge.
Deploy a React or Vite app
A head-to-head walkthrough: build from Git, preview URLs, env vars, rollback and the edge.
App hosting on ngris
The five app types, Git deploys, previews and everything built in next to the deploy button.
Your whole stack behind a security edge. Free to start.
Deploy a site, a backend or a function in minutes. No card needed.