Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.relnx.io/llms.txt

Use this file to discover all available pages before exploring further.

Bring your own tool (custom tools) is an Enterprise feature. Add your own open-source projects or internal/private tools and Relnx will track their releases just like the 100+ tools in the public catalogue — with AI summaries, breaking-change call-outs, email/Slack notifications, and acknowledgments.

​
When to use it

  • An internal tool your team owns that isn’t (and shouldn’t be) on the public catalogue.
  • An open-source project Relnx doesn’t track yet and you don’t want to wait for it to be added.
  • A fork of a public tool — track the fork’s releases, not the upstream’s.
If the tool is already in the public catalogue, just follow it normally — see Follow tools. Custom tools are for things the public catalogue doesn’t have.

​
Prerequisites

  • An Enterprise subscription.
  • An organisation created from your account (Enterprise allows 1 org per account — see Manage an organisation).
  • A release source for the tool — one of:
    • A public GitHub repo (e.g. myorg/myproject).
    • A private GitHub repo — requires your org’s GitHub App installation (set up under Org → Repositories).
    • A Helm chart repository (URL + chart name).

​
Add a custom tool

  1. Open your organisation → Custom Tools (URL: www.relnx.io/organizations/<slug>/custom-tools).
  2. Click Add custom tool.
  3. Fill in:
    • Name — display name (e.g. “Internal Auth Service”).
    • Slug — URL identifier (auto-generated, editable). Lowercase + hyphens.
    • Source — GitHub repo (owner/repo) or Helm chart (repo URL + chart name).
    • Logo URL (optional).
    • Category (optional) — for grouping in your org’s tool list.
  4. Save.
Relnx syncs the tool’s releases on the next scheduled sync (within ~12h) and re-syncs twice daily after that, same as built-in tools. AI summaries, acknowledgments, and notification routing all work identically.

​
Private repos: one-time setup

If the tool lives in a private GitHub repo, your organisation needs to install the Relnx GitHub App so Relnx can fetch releases without a personal token.
  1. Org → Repositories → Connect GitHub.
  2. Pick the GitHub organisation or user that owns the private repo.
  3. Authorise the Relnx GitHub App; pick which repos it can read.
After that, your custom tool can reference any repo the GitHub App was granted access to.

​
Limits

  • Per organisation: unlimited custom tools on Enterprise.
  • Visibility: custom tools are private to your organisation — they never appear in the public catalogue, Slack slash-command listings, or search outside the org.
  • Followers: members of your org can follow the custom tool the same way they follow built-in tools.

​
Removing a custom tool

Org → Custom Tools → ⋯ → Delete. This removes the tool definition; historical features and notifications already sent are preserved for the audit log.