Company sign-in for
your team's internal tools
Put Google, Microsoft, GitHub or your own OIDC sign-in in front of Metabase, Grafana, n8n… Read the quick start
Works with your sign-in and your tools. Google, Microsoft, GitHub or your own OIDC in front, any web app behind.
People sign in with Google, Microsoft, GitHub, Okta, Auth0, Keycloak, JumpCloud, Authentik or your own OIDC provider to reach Metabase, Grafana, Open WebUI, n8n, Superset, Umami or any web app on your server.
Add the whole company without counting seats
Priced per app, not per person
Bring in a client or your accountant too. Nobody costs a seat.
Keep your DNS where it is
One CNAME record at any DNS provider points your hostname at LocalCan. LocalCan gets the certificate.
Nothing to install for viewers
People open the app in a browser and sign in. A small connector next to the app holds the only connection.
Put sign-in in front of your first app
See DocsAdd the app in the dashboard
Pick a preset, a hostname and the app's address. You get a connector key.
- Preset
- Grafana
- Hostname
- grafana.example.com
- Upstream
- http://grafana:3000
Run the connector next to the app
One connector serves every app on its server. It holds the only connection, outbound.
docker run -d --name localcan-connector --restart unless-stopped \ --network <your app's network> \ -v localcan-connector:/data \ -v /etc/localcan/connector.key:/run/secrets/connector_key:ro \ -e LOCALCAN_CONNECTOR_KEY_FILE=/run/secrets/connector_key \ ghcr.io/localcan/connector:1Add one CNAME record
At any DNS provider. LocalCan gets the certificate from Let's Encrypt.
- Type
- CNAME
- Name
- grafana.example.com
- Target
- k3x9q2m7p4w8z1r5t6y0b2nd.cname.localcan.dev
Choose who may sign in
A new app lets nobody in. Add rules, up to 200 per app.
- Google Workspace domain
- example.com
- Email address
- accountant@example.org
- Group from your OIDC
- engineering
Open the app's address and sign in
People sign in with Google, Microsoft, GitHub or your own identity provider. Grafana then signs them in from the identity header.
Control for admins, privacy for viewers. Every tier includes all of it.
- Sign-in
- Google, Microsoft, GitHub, or your own identity provider over OIDC. Up to five methods per app.
- Rules
- Exact emails, a Google Workspace domain, a Microsoft tenant, or groups from your own OIDC. Up to 200 per app.
- Outside people
- Add their exact email. They sign in with their own Google, Microsoft or GitHub account.
- Blocking
- Block a person on every app. Their sessions end within 2 minutes.
- Sign-out
- Sign one person out of every app, or sign everyone out of an app.
- Sessions
- 1 to 168 hours, 24 by default.
- Admin changes
- Need two-factor sign-in on the admin's account.
- Identity header
- A signed JWT (RS256, keys per team) on every request. Grafana signs people in from it.
- Scripts and agents
- Service tokens for scripts and coding agents, up to 50 per team.
- Webhooks
- Public paths skip sign-in for the paths you list.
- Records
- An access log of sign-ins, kept 90 days, plus the team's audit log.
- Viewer privacy
- People who sign in with Google, Microsoft or GitHub see what the team will see before anything is shared.
- Data
- Stored in the EU, with a published DPA. Edges outside the EU relay requests.
- Connector
- Linux, with Docker, Compose or systemd. It holds the only connection, outbound.
Frequently asked questions
Do I need to move my DNS?
No. Add one CNAME record at your DNS provider and LocalCan gets the certificate for your hostname. Your domain stays where it is.
Is there a free plan?
No. You can set up three apps before you pay. They let nobody in until your team has LocalCan Access.
How is it priced?
Do viewers need a LocalCan account?
No. People open the app in a browser and sign in with their account at Google, Microsoft, GitHub or your own identity provider. They install nothing and create no LocalCan account.
Can people outside my company sign in?
Yes. Add their exact email to the app's rules. They sign in with their own Google, Microsoft or GitHub account, and nobody costs a seat.
Does it support SAML?
No. LocalCan Access signs people in with Google, Microsoft and GitHub, or with your own identity provider over OIDC, such as Okta, Keycloak, Authentik, Auth0 or JumpCloud.
Will people still log in to Metabase, n8n or Umami?
Yes. Metabase, n8n and Umami keep their own login behind LocalCan Access, so people sign in with your company account first, then in the app. Grafana and apps that check the signed identity header sign people in from the header instead.
What runs on my server?
One small connector next to your apps, on Linux, with Docker, Docker Compose or systemd. It holds the only connection, outbound to LocalCan, and one connector serves every app on its server.
Where is our data stored?
What happens if LocalCan can't be reached?
People already signed in keep working for up to 60 minutes after their last successful check. New sign-ins wait until LocalCan is back. The identity header stops when its token expires, within 10 minutes.