Skip to main content
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 GitHub repository for the tool — public, or private if you supply access (see Private repos below).

​
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:
    • Tool Name — display name (e.g. “My Internal API”).
    • GitHub Repository — owner/repository (e.g. kubernetes/kubernetes).
    • Description (optional).
    • Category — for grouping in your org’s tool list.
    • Tool Visibility — Private (organization only), Internal, or Public (catalogue).
    • Optionally turn on Sync Only (under Release Sync Mode) to track releases and get notifications without running AI feature extraction.
  4. Click Add Tool.
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: supply access

If the tool lives in a private GitHub repo, turn on the Private GitHub Repository? option in the Add Custom Tool form and give Relnx read access in one of two ways:
  • Fine-grained Personal Access Token — paste a token scoped to the repo with read access to its contents. This is the quickest option for a single repo.
  • GitHub App installation — install the Relnx GitHub App for the GitHub organisation or user that owns the repo (Org → Repositories → Add GitHub Org), then the tool can read any repo the App was granted. This avoids long-lived tokens and refreshes automatically.
After access is set up, Relnx fetches the private repo’s releases the same way as a public one.

​
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.