The Router licence in plain words

This page explains the licence in plain words. It grants no right and changes none: the LICENSE of the version you use, and your Order if you have one, govern.

What is free

  • Production use of an installation with up to 500 Endpoints, free of charge and with any number of services, as long as the installation is not used to provide a hosted service for third parties.
  • Your own business includes the applications and services you make available to your customers: their use of those applications is not a hosted service.
  • The Business Source License 1.1 also lets anyone copy, modify and redistribute the code and use it outside production, at any count.

What counts

  • An Endpoint is a distinct combination of a route path template and an HTTP method or method group, configured for the installation's production routing. GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS and TRACE each count once per template; all other methods on a template, such as PATCH, count once together as one method group; routes that accept any method count once together.
  • A template counts once across the installation, however many services, gateways, instances or versions serve it. Parameter names, and the values a parameter takes, do not add Endpoints.
  • The count is the current number, not a running total: an Endpoint stops counting when no part of the installation routes it in production any more. The Router's own health, status and API-description endpoints do not count.
  • An installation is one coordinated routing system: its replicas, workers and failover instances count together. Genuinely separate systems are separate installations, each with its own free allowance.
  • While you rely on the free use, you count the Endpoints yourself, including any the gateway does not discover. You do not report the count to us.

A notice level is not a limit

Above 250 Endpoints the gateway writes an informational notice in its log and its licence status. The notice level is not a limit: crossing it does not mean you need an order, and it creates no fee.

The gateway reads its licence status offline and only reports it: it never refuses or slows a request, never stops and never contacts us. That it keeps running does not show that a use is permitted: the licence and any Order decide.

If you go over by mistake

An accidental excess over 500 Endpoints, or over the capacity your Order authorises, is permitted from its start until 14 days after you first become aware of it. By then, reduce the count or obtain enough capacity. This does not cover deliberate or repeated circumvention, and crossing the notice level does not start the 14 days.

Embedded in a product you deliver

Embedded use

Under the component Additional Use Grants, you can operate the Router or Workflow engine for your own business within the applicable free limits, or under an applicable standard capacity Order. This includes applications and services used by your customers, subject to the embedded-production boundary below.

These grants do not by themselves authorise production operation of the Router gateway or Workflow engine as an embedded part of a third-party commercial software product. That boundary applies to any such commercial software product, including products that do not compete with a gateway or workflow platform.

Such production use requires express permission in an applicable Order unless another independently applicable licence or permission already authorises it, including an effective Change License.

This boundary concerns production operation. It does not restrict independently available copying, redistribution or non-production permissions, and it does not apply to the packages and corresponding source independently licensed under Apache-2.0 in the accompanying release-specific licensing manifest. Permission to distribute your own application code or workflow definitions does not, by itself, grant permission to operate an embedded server or runtime.

An applicable existing Order can contain the necessary express permission. A separate transaction is unnecessary merely because the permission has a separate scope.

That permission costs nothing: an Order gives it with a no-fee embedded line for each end-customer installation (Customer Agreement, Schedule 3, C.4).

Hosted service for third parties

Providing the Router's routing or rate limiting as a hosted or managed service for third parties' own applications or infrastructure, for example operating a gateway for another company's independent services, is outside the free use and outside a standard order. It needs an Order that names that permission, its scope and its price; ask for a quote. A contractor that operates your installation on your behalf does not make it a hosted service.

Apache-2.0 packages and the component licence

The microservice SDK and the client side of the transports are licensed under the Apache License 2.0. The gateway, the server side of the transports and the rate-limiting packages are licensed under the Stella Ops Router licence.

A service that uses only the SDK and a client transport therefore uses Apache-2.0 packages only. The rate-limiting packages for services carry the Router licence.

Each Apache-2.0 package carries this statement in its README:

The packages StellaOps.Canonical.Json, StellaOps.Components.Licensing, StellaOps.Cryptography.Abstractions, StellaOps.Cryptography.DefaultProvider, StellaOps.DependencyInjection, StellaOps.Messaging, StellaOps.Messaging.Transport.InMemory, StellaOps.Messaging.Transport.Postgres, StellaOps.Messaging.Transport.Valkey, StellaOps.Microservice, StellaOps.Microservice.AspNetCore, StellaOps.Microservice.SourceGen, StellaOps.Plugin, StellaOps.Router.Common, StellaOps.Router.Transport.InMemory, StellaOps.Router.Transport.Messaging, StellaOps.Router.Transport.RabbitMq, StellaOps.Router.Transport.Tcp, StellaOps.Router.Transport.Tls and StellaOps.Router.Transport.Udp are licensed under the Apache License, Version 2.0. They comprise the shared foundation packages, the general Messaging packages and the Router client packages (the client SDK, the client contracts and the client transports).

The Stella Ops Router gateway, the server transports and the rate-limiting packages, and the Stella Ops Workflow packages, are separate packages. They are licensed under the Business Source License 1.1 with the Additional Use Grant of the Router or Workflow licence. Those licences govern those separate packages only. They place no condition on the use of the Apache-licensed packages.

"Stella Ops" is a trading name of Е-САЛЮШЪНС ЕООД (e-Solutions EOOD). Use of the Licensor's trade names and marks is governed by section 6 of the Apache License, Version 2.0. That section permits use as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

Change Date: Apache-2.0 after four years

Each version of the Router changes to the Apache License 2.0 on its Change Date: the fourth anniversary of that version's first public distribution. Each version has its own date, written into its LICENSE at release.

The licence file

  • An order comes with a vendor-signed licence file, or the same record as a single text value, for the installation. The gateway reads it offline, for its licence status and notices only.
  • With a file that matches the installation and covers the running version, the gateway's logs and health output show “Licensed to” and the name agreed in the Order.
  • The file records your Order. It grants no right by itself, and a missing file or a notice withdraws no permission. Free use needs no file.

Full licence texts

Each package carries its LICENSE and NOTICE files, with the release fields (version, release tag and commit, Change Date) filled in when the version is released. Until the first release, the licensing guide and Schedule 3 of the Customer Agreement state the terms.