Authentication + authorization for Caddy

Your apps.
Your front door.

Give your applications a place to sign in.
Decide who gets through.

AuthCrunch connects your identity providers, login portal, and access policies at the edge. Built for Caddy. Open source from the start.

Ready-to-run distribution Your infrastructure

One identity. A decision for every app.AUTHCRUNCH
A sign-in portal sends an identity through a glass access-policy gateway. Two applications are allowed; a third is denied.
01 Establish identity02 Evaluate access03 Reach your application

Identity meets access

A login is a beginning.
Your policy takes it from there.

Bring the pieces together at your application’s front door. Keep the decisions in your hands.

Bring your identity provider
  • OpenID Connect
  • OAuth 2.0
  • SAML
  • LDAP
  • Local accounts

See the moving parts

Follow a request.
See the decision.

Signing in tells you who someone is. An access policy decides what they can do next.

Choose a visitor. Change the rule. Watch the outcome.

Try it in a real Caddy setup (opens in a new tab)Interactive explanation · no login or server request
GET /your-applicationREQUEST EXPLORER

01 / Who is visiting?

02 / Who may enter?

AliceAdministrator
Policy excerptallow roles authp/admin authp/user
Access allowed

Alice has a role accepted by this policy. The request reaches the app.

Build around your world

What are you protecting?

From a single service to a collection of apps.
Start with the flow that fits.

Personal infrastructure

Your services. One place to sign in.

Put a portal in front of your dashboards, files, and personal tools. Choose the identities that belong in your home lab.

  • Start with local users
  • Add your preferred identity provider
  • Give each service its own access policy
Protect your first app (opens in a new tab)
photos.home.exampleHTTPS
Identity → access policy
01PhotosAllowed
02FilesAllowed
03MonitoringRole required

One identity. Different rules for each application.

Built in the open. Used in the real world.

In good company.

Developers, infrastructure teams, and home lab builders share what AuthCrunch makes possible.

Caddy is the primary server technology I use for personal and professional projects and AuthCrunch is my favorite way to secure it.

Todd ChapmanCTOSnickerdoodle Labs

The Caddy security plugin allows us to use Caddy as a TLS web proxy and an authentication gateway with OAuth in one to control access to our infrastructure and operate it securely and efficiently.

René MoserCEO and Cloud Automation EngineerMoser Systems

Caddy Security a.k.a. AuthCrunch is a great open source addition to add authentication and authorization to Caddy. Its code is of great quality and the maintainer is very responsive and helpful to issues and questions. While these aspects make it a perfect technical choice for my organization, I also really like it on a personal level because Paul holds the values of open source software very high.

Moritz SchlarbDevOps - SREJohannes Gutenberg University Mainz
Using AuthCrunch at your company?

Open a pull request in authcrunch/authcrunch and add your story to ADOPTERS.md.

Share your adoption (opens in a new tab)

A commitment to open source

A maintainer.
A community.
A promise.

Paul Greenberg Maintainer, AuthCrunch

I, Paul Greenberg, as the maintainer of the open-source project AuthCrunch aka Caddy Security, hereby pledge my commitment to its continued development as a free and non-commercial project.

01

Open source license

The project will remain licensed under an OSI-approved open-source license. You have the freedom to use, modify, and distribute the code for any purpose, including commercial applications.

About open source licenses (opens in a new tab)
02

No commercial offerings

I will not offer any commercial products or services directly based on the codebase. This includes paid versions with additional features, support contracts, or hosted versions of the software.

The goal: a project that remains accessible and usable for everyone.

Make the next request count

Your first login is the next step.

Start local. Follow the request. Make the policy yours.

Build your first setup (opens in a new tab)