---
source_url: "https://simple-auth.zdyn.net/?utm_source=openai"
title: "Simple Auth | Simple Auth"
mirrored_at: 2026-08-22T03:02:45.848Z
host: simple-auth.zdyn.net
cited_in_42a: true
mirror_canonical: "https://index.42a.ai/simple-auth.zdyn.net/index__q__utm_source_openai"
---

> **Original source:** https://simple-auth.zdyn.net/?utm_source=openai

 

_Simple-Auth_ is a designed to be an easy way to manage your site's users. Unlike large complex solutions, it aims to provide **simple login and user-management to a small or medium site**. It doesn't try to replace global authentication providers or enterprise user management (kerberos, active directory, etc...)

      ![GitHub go.mod Go version](https://img.shields.io/github/go-mod/go-version/zix99/simple-auth) ![Coverage](https://simple-auth.zdyn.net/assets/img/coverage.f9882014.svg)

![Simpleauth](https://simple-auth.zdyn.net/assets/img/simpleauth.df5b2079.png)

**Features include:**

-   Local user management (create account, login, [TOTP two-factor](https://simple-auth.zdyn.net/login/local#totp-2fa))
-   [Credential validation via API](https://simple-auth.zdyn.net/authenticators/simple) and [OAuth2 / OIDC](https://simple-auth.zdyn.net/authenticators/oauth2)
-   Reverse proxy to downstream service blocked by login ([gateway](https://simple-auth.zdyn.net/access/gateway))
-   Per-request [vouching](https://simple-auth.zdyn.net/authenticators/vouch) (eg. for NGINX `auth_request` to act as a validator for login), to act as an authentication portal
-   [Same-domain/subdomain login](https://simple-auth.zdyn.net/access/cookie) provider via cookie validation
-   Various API implementations to [authenticate a user](https://simple-auth.zdyn.net/login) (Local username/password, third-party OIDC, etc)
-   [OpenID Connect Login](https://simple-auth.zdyn.net/login/oidc) (OIDC) eg. Google Auth
-   Optional [welcome email and email-verification](https://simple-auth.zdyn.net/email)
-   Forgot/lost password
-   Login/access-attempt auditing
-   [REST API](https://simple-auth.zdyn.net/apidocs) to all underlying functionality
-   Mobile friendly
-   White-label deployment using [customizations](https://simple-auth.zdyn.net/customization)

## [#](#why-not) Why Not...

There are plenty of other authentication providers out there. You can always roll your own or use another solution like [Okta (opens new window)](https://www.okta.com/), [Gluu (opens new window)](https://www.gluu.org/) or [Keycloak (opens new window)](https://www.keycloak.org/). While these services are perfectly fine (they're great, infact), _simple-auth_ tries to be _**simple**_. Our [quickstart](https://simple-auth.zdyn.net/quickstart) is incredibly short and the hosting modes allow **zero-to-fully setup in less than 5 minutes**.

Long story short, if you have the use case and time to look at another provider, please do! If you're looking for something simple and easy to get started with, _simple-auth_ may be for you.

## [#](#concepts) Concepts

### [#](#objects) Objects

At the root of the object representation sits the "Account". It is associated with a unique email. By itself, an account does not give access to login, it needs an authentication object associated with it.

graph TD A\[Account\] --> AA{User Authenticates} subgraph Authenticators AA --> B\[Local Auth\] B --> B2\[TOTP/2FA\] AA --> C\[OAuth2\] AA --> E\[One-Time Auth\] end A --> D\[Audit Log\]

By default, simple-auth is split into three layers:

1.  **Login Providers**: The mechanisms that allow creating an account object, and how a user logs in. For example, a Local account or OIDC (OAuth2)
2.  **Authenticators (API)**: How dowstream apps can authenticate with _simple-auth_. Usually via API or requests
3.  **Access Layer**: How web applications can authenticate with simple-auth

You can find more information on all three layers on the left. Not all 3 layers are required for a functional setup.

## [#](#next-steps) Next Steps

Try heading over to [Quickstart](https://simple-auth.zdyn.net/quickstart) and giving it a try!