Security is friction. Let’s make it invisible.
Sunray identifies every visitor by passkey before letting them reach your applications: ERP, back offices, internal tools, APIs. No code to change, no client to install, no password, no VPN.
In production at Adekia, Mathon, Alter Eco Santé
“Security is friction, not a feature. So let’s make it affordable, usable and invisible.”
Affordable
Simple pricing, with no per-feature negotiation and no surprises. The core is free when self-hosted.
Usable
Passkeys first: no client to install, no password to remember. Signing in becomes a natural gesture, fingerprint or Face ID.
Invisible
ForwardAuth or a transparent reverse proxy: your applications are never modified, and the server stays out of the request path.
A worker decides. The server is only consulted in advance.
The worker in front of each application caches the configuration of the hosts it protects and answers from that cache. None of your users’ requests go through the Sunray server.
Passkeys, not passwords
Users and passkeys in Sunray’s directory, sign-in pages served on the application’s own hostname.
A server outage doesn’t cut access
Configuration cached for up to 24 hours, open sessions valid until they expire (1 h by default, adjustable per host, 24 h at most).
Your trusted addresses
Office, VPN or monitoring probe go through without signing in; an unreadable entry is flagged rather than ignored.
Everything you need to close the door, nothing more.
WebAuthn FIDO2 passkeys
Passkeys bound to each hostname, single-use enrolment tokens. Zero passwords.
Locked by default
All traffic is authenticated unless explicitly exempted: public rules, by address range or by token.
Transparent reverse proxy
ForwardAuth worker (Traefik, Nginx, Caddy) or Cloudflare Worker at the edge. No change to the application.
Offline resilience
While the server is down, workers serve from their cache: open sessions carry on until they expire (24 hours at most), only new sign-ins wait for it to come back.
Every access audited
Sign-ins, passkeys, sessions and violations logged server-side; every session can be listed and revoked.
Admin console
Users, hosts, rules, sessions and workers managed from a single interface, reachable from your office IPs.
Two ways to place the control point. One configuration.
| Mode | Where the check happens | For whom |
|---|---|---|
| A · ForwardAuth, self-hosted | A worker next to the application, queried by Traefik, Nginx or Caddy before each routing decision. | The control point stays inside your perimeter. |
| B · Sunray Serverless, at the Cloudflare edge | The worker is itself the reverse proxy, after Cloudflare’s security filters and before the cache. | Your applications are already behind Cloudflare. |
The Worker validates sessions from its local cache, with no call to the Server on the request path. If the Server cannot be reached, cached configuration is kept for up to 24 hours: existing sessions keep working until they expire, only new sign-ins wait for it to return. Your application never receives unauthenticated traffic.
Two Sunray servers, active and standby, state replicated by PostgreSQL. Never exposed directly to the Internet.
Muppy publishes the list of names to protect; Sunray re-reads it every 5 minutes, and Muppy never calls Sunray.
Every flow is documented with its protocol, port and opening direction, for your CISO’s review.
In four steps. Already built into Manganese and Odizy.
On our platforms, Sunray is switched on per application template: every name of an App Server is protected, including the IDE and your custom domain. For Muppy Enterprise, we recommend Sunray in front of the whole instance.
Deploy the Sunray server
The management plane: users, passkeys, hosts and access rules. A Sunray App Server template is available on Manganese.
Choose your worker
ForwardAuth next to your reverse proxy, or a Cloudflare Worker at the edge.
Register your passkeys
Your users receive an enrolment token and create their passkey on first access.
Your applications are protected
Every access is validated by passkey. Zero passwords, zero VPN.
We use it on ourselves first.
Muppy
Internal development infrastructure, daily traffic.
Manganese
Protects customers’ App Servers on the multi-tenant PaaS, daily traffic.
Adekia
First fully self-run external customer, on an environment independent of ours.



What CISOs ask
How is it different from a VPN?
No client to install and no tunnel to configure: your users sign in by passkey (fingerprint, Face ID) directly in the browser, hostname by hostname.
Do I need to change my application?
No. The reverse proxy asks the worker for authorisation before routing the request; the application simply receives it, with headers identifying the user and the session.
Do I need an identity provider?
No. Sunray has its own directory of users and passkeys. Nothing to plug in or maintain alongside it.
What happens if the Sunray server goes down?
Protection carries on: each worker decides from its cache, and open sessions remain valid until they expire, 24 hours at most. Only new sign-ins wait for the server to come back.
What licence?
The core is source-available under the FSL-1.1 licence, which converts to Apache 2.0 two years after each release. It is free when self-hosted.
Which of your applications can anyone reach today?
Let’s list them together. In 30 minutes, we identify your exposed applications, the right deployment mode and what it takes to protect them.
You describe your project
Four fields, no phone number required.
We talk it through for 30 minutes
Architecture, hosting constraints, security, taking over what you already run.
Prefer to try first? Try Manganese, free beta
Odizy Your Odoo ERP, from branch to production
Manganese Complete App Servers, any stack
Manganese DevFleet Agentic remote dev for large organisations