EuroMakers
  • Software
  • Launches
  • Journal
  • Advertise
Submit
  • Software
  • Launches
  • Journal
  • Advertise
Monday digestAbout
Submit your product
Back to the Journal

Editorial

Orion Belt went AGPL. The SDK you can install didn’t

The UK access gateway dropped the Commons Clause on 18 November. Its new SDKs still install as version 1.0.0 with the old licence file inside, and the repo’s 1.0.0 now says AGPL.

IV

Inês Valente · 21 November 2026 · 3 min read

Editorial cover for Orion Belt went AGPL. The SDK you can install didn’t

This morning I downloaded `@orion-belt/sdk` from npm, unpacked it and opened `LICENSE`. The first line reads ‘Commons Clause License Condition v1.0’. Three days after Orion Belt announced it is open source under the AGPL, that is the licence on the SDK you actually get.

Orion Belt is a self-hosted gateway for SSH and RDP access: agents on your machines dial out to it through reverse tunnels, so nothing needs an open inbound port, and it records sessions and handles just-in-time approvals on top. It is a small UK project, on GitHub since 1 January 2026, with 48 stars when I looked. It is not in our directory.

The move in the other direction

Version 1.5.0 was tagged on 15 November. On 18 November the maintainers explained the licence change: from 1.5.0 the gateway is `AGPL-3.0-only`, replacing Apache 2.0 with the Commons Clause, which it had used since the first release. Their reasoning is plain. The clause banned selling the software, it is not an OSI licence, and teams with an ‘OSI-approved only’ policy could not adopt the gateway at all. The AGPL keeps the code auditable and self-hosting free, and anyone who runs a modified hosted copy has to publish their changes.

Screenshot of the Orion Belt blog post announcing that Orion Belt is now open source under the AGPL v3.0
The 18 November post. Releases up to 1.4.x keep the licence they shipped with; 1.5.0 is the first under the AGPL.

This is the rarer direction. Most licence news I have written about this autumn went the other way, with repositories archived, closed or moved behind a login. A security tool that becomes easier for a cautious team to approve is good news, and the same release fixes four issues from an external audit in early November and adds SLSA provenance so you can check a binary came from the tagged build.

Two licences, one version number

The 1.5.0 release also introduced Python and TypeScript SDKs for the whole `/api/v1` surface. The post says they are AGPL too, and adds that the packages on PyPI and npm ‘still carry the old license metadata from their 1.0.0 release. Their next release picks up the AGPL.’

It is more than metadata. The npm tarball for 1.0.0 ships the Commons Clause text with Apache 2.0 underneath, naming Mohamed Zrouga as licensor, and its `package.json` points to that file. PyPI lists `orion-belt-sdk` 1.0.0 with the licence expression `LicenseRef-Apache-2.0-with-Commons-Clause`. Meanwhile, in the repository, `sdk/js/package.json` and `sdk/python/pyproject.toml` say version 1.0.0 and `AGPL-3.0-only`. When I checked today, no newer package existed on either registry.

By the project’s own rule, a licence does not change retroactively, so the copy you installed is under the licence in the file you received. For most people that is fine, perhaps even easier: the Commons Clause only bars selling a product whose value comes substantially from the software, while the AGPL would ask you to publish the source of an application that bundles the SDK and is distributed or served to others. But a lockfile that says `1.0.0` no longer tells you which of the two you have. A licence scanner reading the registry will report the old one. Someone vendoring the SDK from the repository will get the new one under the same number.

The maintainers already offer the clean way out: calling the REST API with any HTTP client does not bring the AGPL into your code. If you build something you ship on top of Orion Belt, do that, and keep the SDK for internal scripts. And the fix on their side is one publish away. Bump the SDKs to a version that has never existed under the Commons Clause, so the number tells you the licence.

#Open source#Licensing#Access management

Monday digest

Europe’s best new software, every Monday.

Top launches, new listings and stories from the Journal. One email, skipped on quiet weeks.

Every product in the directory is checked before it goes live and shows where it’s made. Explore the directory

Keep reading

Editorial cover for The Jira checklist that arrives without an owner

The Jira checklist that arrives without an owner

HeroCoders’ migration guide spells out what a ticket count won’t tell you: the checklist can make it to Jira Cloud without the people and deadlines that made it work.

20 November 2026 · 1 min read

Editorial cover for Nextcloud’s release notes list a cloud its app leaves out

Nextcloud’s release notes list a cloud its app leaves out

Nextcloud Office Desktop 9.3.8 lists an OpenCloud connector. I checked both Debian downloads and found only Nextcloud.

19 November 2026 · 1 min read

EuroMakers

The home of European software.

Discover

  • All software
  • By tool
  • Launches
  • Map

Community

  • Journal
  • Monday digest
  • Your feed

For makers

  • Submit your product
  • Claim your listing
  • Advertise
  • Listing criteria

EuroMakers

  • About
  • Contact
  • API
  • Privacy
  • Terms
Explore the map →

© 2026 EuroMakers. Made with conviction in Europe. Product logos belong to their makers.

Language: English
  • English
  • Български
  • Čeština
  • Dansk
  • Deutsch
  • Ελληνικά
  • Español
  • Eesti
  • Suomi
  • Français
  • Gaeilge
  • Hrvatski
  • Magyar
  • Italiano
  • Lietuvių
  • Latviešu
  • Malti
  • Nederlands
  • Polski
  • Português
  • Română
  • Slovenčina
  • Slovenščina
  • Svenska