Need help with biscuit?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

167 Stars 10 Forks Apache License 2.0 112 Commits 28 Opened issues


delegated, decentralized, capabilities based authorization token

Services available


Need anything else?

Contributors list

Biscuit authentication/authorization token

Join the chat at


Biscuit is an authentication and authorization token for microservices architectures with the following properties:

  • distributed authentication: any node could validate the token only with public information;
  • offline delegation: a new, valid token can be created from another one by attenuating its rights, by its holder, without communicating with anyone;
  • capabilities based: authorization in microservices should be tied to rights related to the request, instead of relying to an identity that might not make sense to the verifier;
  • flexible rights managements: the token uses a logic language to specify attenuation and add bounds on ambient data;
  • small enough to fit anywhere (cookies, etc).

Non goals

  • This is not a new authentication protocol. Biscuit tokens can be used as opaque tokens delivered by other systems such as OAuth.
  • Revocation: while tokens come with expiration dates and revocation ids, revocation still requires external state management that we will not specify.


You can follow the next steps on the roadmap.

Current status: - the credential language, cryptographic primitives and serialization format are done - we have implementations in Rust, Java, Go and Web Assembly (based on the Rust version) - Currently deploying to real world use cases such as Apache Pulsar - looking for an audit of the token's design, cryptographic primitives and implementations

How to help us?

  • provide use cases that we can test the token on (some specific kind of caveats, auth delegation, etc)
  • cryptographic design audit: we need to decide on a cryptographic scheme that will be strong enough

Project organisation

    : introduction to Biscuit from a user's perspective
    holds the current ideas about what Biscuit should be
    is the description of Biscuit, its format and behaviour
  • experimentations/
    holds code examples for the crypographic schemes and caveat language.
    contains an experimental version of Biscuit, built to explore API issues


Licensed under Apache License, Version 2.0, (LICENSE-APACHE or

logo by Mathias Adam


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed as above, without any additional terms or conditions.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.