Usage Guidelines

This page details some guidelines and policies that we follow at

Temporary Banning

Temporary banning means that will stop building / serving Binder sessions for a given repository. This usually happens because of some undesired behavior with the repository. Some examples of behavior that could result in temporary banning include:

  • A large, unexpected spike in traffic that persists over time.
  • Sessions that routinely use a large amount of CPU.
  • Sessions that attempt to perform a lot of outgoing networking traffic.

The team uses the following workflow in discussing / deciding when to temporarily ban a repository:

  • An issue is created to document why a repo (or group of repos) is being banned
  • A PR that implements the ban is opened
  • A “bans” tag notes any PRs that created a ban
  • The issue stays open until the ban is lifted

If you are temporarily banned, contact us on the Gitter Channel or Open an Issue to discuss how to un-ban the repository.

Maximum Concurrent Users for a Repository

We don’t want a single repository to dominate all of the traffic to Binder, so we’ve set a maximum limit of concurrent user sessions that point to the same Binder link. The maximum number of simultaneous users for a given repo is 100. If you think you have a really good reason for why this number should be higher, please Open an Issue to discuss with the community!

Reporting Abuse

If you’d like to report any abuse of the service, please click here to send an abuse report.