Skip to main content

Introduction

Relaygate is a debrid gateway for the Stremio addon ecosystem. This page orients you before you dive into the rest of the documentation.

For precise definitions of terms used across these docs, see the Glossary.

Problem​

Stremio addons and related tools integrate with several debrid providers (Real-Debrid, AllDebrid, TorBox, Premiumize, …). Each provider exposes a different REST API, auth scheme, and rate limits. Addon authors repeat the same work; end users juggle many API keys across addons. When those keys are entered into third-party addons, users typically get no clear insight into who is using their keys or which integrations generated a given request.

What Relaygate does​

We operate a gateway: addon backends send JSON control-plane requests to us; we authenticate the caller, map the request to the correct upstream debrid API using the end user’s stored credentials, and return JSON. We do not proxy media file bytes—streaming stays on CDN URLs returned by providers.

From an addon developer’s perspective, Relaygate exposes a canonical standardized API so your backend code does not need to learn each provider’s unique endpoint paths and quirks.

Relaygate's intent is not to serve as a service for subverting the acceptable use terms or restrictions of any debrid provider

Who this is for​

  • End users / Debrid Subscribers — people using debrid services can create a vault, generate a proxy API key, and use supported addons.
  • Addon developers — authors who register, get verified, and call the API from the addon server with developer credentials plus the user’s proxy key.

Actors​

Relaygate operators​

We run infrastructure, review developer applications (ownership verification, not KYC), monitor abuse, and publish a public status page. Developer accounts are free; approval is about trust, not payment.

Addon developers​

We require an account, submitted evidence of addon ownership, and manual approval before credentials activate. Every proxied request must present addon identifier + developer API secret (server-side) so we can attribute traffic and let users moderate who can use their API keys. Approvals should take no more than 24 to 48 hours on busy days.

End users​

They register on the web app, add upstream debrid keys to the vault, generate a proxy API key, and paste it into supporting addons configurations. They see audit history and can allow or deny traffic by IP and by addon identifier.

v1 upstream providers​

AllDebrid, Real-Debrid, Premiumize, TorBox. Additional providers are backlog items documented in our progress notes.

Information about internationalisation support​

This docs site does not support any other languages yet even though i18n is configured. I am an English speaker, so I can't personally translate this site into other popular languages (I wish I could). I will avoid using AI for translations I don't understand since this is a Technical documentation site. Sincere apologies to non-English speakers (assuming they can read this).

Long live online freedom, privacy and security, and the people who fight for it.

Recommended read: Free as in Freedom.