Public | Automated Build

Last pushed: 3 days ago
Short Description
Scalable, security first OAuth 2.0 and OpenID Connect server
Full Description

<h1 align="center"><img src="./docs/images/banner_hydra.png" alt="ORY Hydra - Open Source OAuth 2 and OpenID Connect server"></h1>

<h4 align="center">
<a href="">Chat</a> |
<a href="">Forums</a> |
<a href="">Newsletter</a><br/><br/>
<a href="">Guide</a> |
<a href="">API Docs</a> |
<a href="">Code Docs</a><br/><br/>
<a href="">Support this project!</a>

ORY Hydra is a hardened, certified OAuth2 and OpenID Connect server optimized for low-latency, high throughput,
and low resource consumption. ORY Hydra is not an identity provider (user sign up, user log in, password reset flow),
but connects to your existing identity provider through a consent app.
Implementing the consent app in a different language is easy, and exemplary consent apps
(Go, Node) and
SDKs are provided.

Besides mitigating various attack vectors, such as database compromisation and OAuth 2.0 weaknesses, ORY Hydra is also
able to securely manage JSON Web Keys.
Click here to read more about security.

<p align="left">
<a href=""><img src="" alt="Build Status"></a>
<a href=""> <img src="" alt="Coverage Status"></a>
<a href=""><img src="" alt="Go Report Card"></a>
<a href=""><img src="" alt="CII Best Practices"></a>
<a href="#backers" alt="sponsors on Open Collective"><img src="" /></a> <a href="#sponsors" alt="Sponsors on Open Collective"><img src="" /></a>

<!-- START doctoc generated TOC please keep comment here to allow auto update -->


Table of Contents

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

What is ORY Hydra?

ORY Hydra is a server implementation of the OAuth 2.0 authorization framework and the OpenID Connect Core 1.0. Existing OAuth2
implementations usually ship as libraries or SDKs such as node-oauth2-server
or fosite, or as fully featured identity solutions with user
management and user interfaces, such as Dex.

Implementing and using OAuth2 without understanding the whole specification is challenging and prone to errors, even when
SDKs are being used. The primary goal of ORY Hydra is to make OAuth 2.0 and OpenID Connect 1.0 better accessible.

ORY Hydra implements the flows described in OAuth2 and OpenID Connect 1.0 without forcing you to use a "Hydra User Management"
or some template engine or a predefined front-end. Instead it relies on HTTP redirection and cryptographic methods
to verify user consent allowing you to use ORY Hydra with any authentication endpoint, be it authboss, User Frosting or your proprietary Java authentication.

OAuth2 and OpenID Connect: Open Standards!

ORY Hydra implements Open Standards set by the IETF:

and the OpenID Foundation:

OpenID Connect Certified

ORY Hydra is an OpenID Foundation certified OpenID Provider.

<p align="center">
<img src="./docs/images/oidc-cert.png" alt="ORY Hydra is a certified OpenID Providier" width="256px">

The following OpenID profiles are certified:

To obtain certification, we deployed the reference user login and consent app
(unmodified) and ORY Hydra v1.0.0.


This section is a quickstart guide to working with ORY Hydra. In-depth docs are available as well:

  • The documentation is available here.
  • The REST API documentation is available here.

5 minutes tutorial: Run your very own OAuth2 environment

The tutorial teaches you to set up ORY Hydra,
a Postgres instance and an exemplary identity provider written in React using docker compose.
It will take you about 5 minutes to complete the tutorial.

<img src="docs/images/oauth2-flow.gif" alt="OAuth2 Flow">

<br clear="all">


There are various ways of installing ORY Hydra on your system.

Download binaries

The client and server binaries are downloadable at releases.
There is currently no installer available. You have to add the ORY Hydra binary to the PATH environment variable yourself or put
the binary in a location that is already in your path (/usr/bin, ...).
If you do not understand what that all of this means, ask in our chat channel. We are happy to help.

Using Docker

Starting the host is easiest with docker. The host process handles HTTP requests and is backed by a database.
Read how to install docker on Linux, OSX or
Windows. ORY Hydra is available on Docker Hub.

You can use ORY Hydra without a database, but be aware that restarting, scaling
or stopping the container will lose all data:

$ docker run -e "DATABASE_URL=memory" -e "ISSUER=https://localhost:4444/" -d --name my-hydra -p 4444:4444 oryd/hydra

Note: We had to create a new docker hub repository. Tags prior to 0.7.5 are available here.

Using the client command line interface: You can enter into the ORY Hydra container
and execute the ORY Hydra command from there:

$ docker exec -i -t <hydra-container-id> /bin/sh
# e.g. docker exec -i -t ec91228 /bin/sh

root@ec91228cb105:/go/src/ hydra
Hydra is a twelve factor OAuth2 and OpenID Connect provider


Building from source

If you wish to compile ORY Hydra yourself, you need to install and set up Go 1.10+ and add $GOPATH/bin
to your $PATH as well as golang/dep.

The following commands will check out the latest release tag of ORY Hydra and compile it and set up flags so that hydra version
works as expected. Please note that this will only work with a linux shell like bash or sh.

go get -d -u
cd $(go env GOPATH)/src/
HYDRA_LATEST=$(git describe --abbrev=0 --tags)
git checkout $HYDRA_LATEST
dep ensure -vendor-only
go install \
    -ldflags "-X$HYDRA_LATEST -X`TZ=UTC date -u '+%Y-%m-%dT%H:%M:%SZ'` -X`git rev-parse HEAD`" \
git checkout master
hydra help


<a href="">
<img align="right" width="30%" src="docs/images/sec-console.png" alt="ORY Security Console">

ORY Security Console: Administrative User Interface

The ORY Security Console is a visual admin interface for managing ORY Hydra,
ORY Oathkeeper, and ORY Keto.

ORY Oathkeeper: Identity & Access Proxy

ORY Oathkeeper is a BeyondCorp/Zero Trust Identity & Access Proxy (IAP) built
on top of OAuth2 and ORY Hydra.

ORY Keto: Access Control Policies as a Server

ORY Keto is a policy decision point. It uses a set of access control policies, similar
to AWS IAM Policies, in order to determine whether a subject (user, application, service, car, ...) is authorized to
perform a certain action on a resource.


The ory/examples repository contains numerous examples of setting up this project
individually and together with other services from the ORY Ecosystem.


Why should I use ORY Hydra? It's not that hard to implement two OAuth2 endpoints and there are numerous SDKs out there!

OAuth2 and OAuth2 related specifications are over 400 written pages. Implementing OAuth2 is easy, getting it right is hard.
ORY Hydra is trusted by companies all around the world, has a vibrant community and faces millions of requests in production
each day. Of course, we also compiled a security guide with more details on cryptography and security concepts.
Read the security guide now.

Disclosing vulnerabilities

If you think you found a security vulnerability, please refrain from posting it publicly on the forums, the chat, or GitHub
and send us an email to instead.


Our continuous integration runs a collection of benchmarks against ORY Hydra. You can find the results in ./


Our services collect summarized, anonymized data which can optionally be turned off. Click
here to learn more.



The Guide is available here.

HTTP API documentation

The HTTP API is documented here.

Upgrading and Changelog

New releases might introduce breaking changes. To help you identify and incorporate those changes, we document these
changes in and

Command line documentation

Run hydra -h or hydra help.


Developing with ORY Hydra is as easy as:

go get -d -u
cd $GOPATH/src/
dep ensure
go test ./...

Then run it with in-memory database:

DATABASE_URL=memory go run main.go host


  • We changed organization name from ory-am to ory. In order to keep backwards compatibility, we did not rename Go packages.
  • You can ignore warnings similar to package case-insensitive import collision: "" and "".

Libraries and third-party projects



Blog posts & articles


This project exists thanks to all the people who contribute. [Contribute].
<a href="graphs/contributors"><img src="" /></a>


Thank you to all our backers! 🙏 [Become a backer]

<a href="" target="_blank"><img src=""></a>

We would also like to thank (past & current) supporters (in alphabetical order) on Patreon: Alexander Alimovs, Chancy Kennedy, Drozzy, Oz Haven, TheCrealm


Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>
<a href="" target="_blank"><img src=""></a>

A special thanks goes out to Wayne Robinson for supporting this ecosystem with $200 every month since Oktober 2016 on Patreon.

Docker Pull Command
Source Repository