# ZevAuth developer documentation

> ZevAuth is authentication as a service: sign-up, sign-in, sessions and organizations, delivered as drop-in React components, a JavaScript client, or a REST API. This file is a curated index of every doc page — follow the `.md` link beside any title to grab that page's clean markdown body for AI integration.

Drop the whole site into one context window with `https://docs.zevauth.com/llms-full.txt`, or fetch any single page's markdown by appending `.md` to its URL (e.g. `https://docs.zevauth.com/api/authentication.md`).

## Getting started

- [Introduction](https://docs.zevauth.com/guide.md)
- [Quickstart](https://docs.zevauth.com/guide/quickstart.md): A working sign-in, in about five minutes.
- [Keys and environments](https://docs.zevauth.com/guide/keys.md): Which key goes where, and which one must never reach a browser.
- [Development and production](https://docs.zevauth.com/guide/environments.md): Two environments, deliberately unlike each other.

## Building with the SDK

- [React](https://docs.zevauth.com/sdk/react.md): Hooks, control components and the provider.
- [Next.js](https://docs.zevauth.com/sdk/nextjs.md): Components, server helpers and route protection.
- [JavaScript](https://docs.zevauth.com/sdk/javascript.md): The framework-agnostic client.
- [Backend](https://docs.zevauth.com/sdk/backend.md): Manage users and organizations from your server, with a secret key.
- [Components](https://docs.zevauth.com/sdk/components.md): The drop-in UI, and how it picks up your brand.
- [Organizations](https://docs.zevauth.com/sdk/organizations.md): Teams, roles, and the session acting as one.

## Concepts

- [Sessions and tokens](https://docs.zevauth.com/concepts/sessions.md): What a session is made of, and how it stays alive.
- [Verifying tokens](https://docs.zevauth.com/concepts/verifying-tokens.md): Checking an access token on your backend, in any language.
- [Hosted pages](https://docs.zevauth.com/concepts/hosted-pages.md): The screens your users reach from an email.
- [Branding](https://docs.zevauth.com/concepts/branding.md): Making every screen look like your product.

## API reference

- [Overview](https://docs.zevauth.com/api.md)
- [Authentication](https://docs.zevauth.com/api/authentication.md): Signing people in and keeping them signed in.
- [Users](https://docs.zevauth.com/api/users.md): Reading your userbase, and what a person may change themselves.
- [Organizations](https://docs.zevauth.com/api/organizations.md): Creating teams from your backend, and managing them from your app.
- [Errors](https://docs.zevauth.com/api/errors.md): The error envelope, and the codes worth branching on.