> ## Documentation Index
> Fetch the complete documentation index at: https://developers.authlete.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sample Server

> After the tutorials, try Authlete with a runnable sample authorization server. A Java reference implementation is available, with more languages planned.

Once you have worked through the [OAuth 2.0](/get-started/quickstarts/oauth-2-0-basics) and [OpenID Connect](/get-started/quickstarts/oidc-basics) tutorials, the next step is to see Authlete working inside an actual authorization server.

Authlete is the backend that handles the OAuth 2.0 and OpenID Connect protocol logic — it does not expose endpoints to clients or end users directly. To run real flows end to end, you pair it with an authorization server *frontend* that calls the Authlete APIs. To make this easy to try, Authlete publishes runnable **sample servers** that you can deploy and exercise against your own service.

## Java

The Java reference implementation, [`java-oauth-server`](https://github.com/authlete/java-oauth-server), is a full-featured authorization server. Beyond the basic OAuth 2.0 / OpenID Connect flows, it supports advanced specifications including **FAPI** (1.0 and 2.0), **OpenID Federation**, and **OpenID for Verifiable Credential Issuance** (OID4VCI), as well as CIBA (Client-Initiated Backchannel Authentication), the OAuth 2.0 Device Authorization Grant (Device Flow), Pushed Authorization Requests (PAR), Grant Management, and Dynamic Client Registration.

To set it up and run OAuth 2.0 / OpenID Connect flows against it, see [**Using Demo Authorization Server**](/get-started/quickstarts/using-demo-authorization-server).

## Other languages

Sample servers for other languages are planned, and will be listed here as they become available.