Commercial use and licensing

The RouteRTL shell is MIT licensed. The core is distributed under the PolyForm Shield License 1.0.0, which permits use, modification, and distribution subject to its terms, including its restriction on using the software to provide a competing product. Both licence texts ship in the source tree and in the published package, and those texts control.

A Pro entitlement changes which features are available. It does not alter the rights or restrictions in those licences.

The following are available without a subscription, seat registration, or entitlement expiry, for commercial and non-commercial use permitted by the software licences:

• ·Single-vendor and multi-vendor build orchestration across the supported Xilinx, Intel, Lattice, and Microchip backends
• ·Synthesis, implementation, and bitstream generation
• ·Open-source toolchain support and the virtual board
• ·Simulation with nvc, GHDL, Verilator, and cocotb
• ·All lint profiles
• ·rr program and rr linux
• ·Local telemetry and local rr diagnose
• ·Registry search, package installation, and IP submission

Vendor toolchains are supplied and licensed by their own vendors. RouteRTL orchestrates the toolchains already installed on the machine and does not provide them.

A current Pro entitlement covers the advanced verification layer:

• ·rr verify — verification sessions and evidence records
• ·rr formal — PSL and SVA property checking
• ·Coverage maps against a requirements contract
• ·rr loop — the agentic verification loop

Pro is quoted per seat. Availability, price, term, and support scope are quoted by email and stated in written terms before any purchase.

The capabilities listed above are those included in the free tier today. There is no plan to move them to Pro. Tier definitions may change for future releases, and where a capability is being considered for Pro it is identified as a preview in the release documentation before any change takes effect.

A change to the tiers applies to later releases. It does not alter the licence terms of a release already obtained.

A Pro entitlement is carried in an Ed25519-signed token held on the machine. RouteRTL checks that token locally against a public key built into the release. The check itself contacts no server, so a machine with an issued token can run the licensed features offline, including on an air-gapped network.

Tokens carry an expiry, so renewal involves installing a replacement token. Obtaining or refreshing a token, and commands that use registry, package, or online diagnostic services, do require network access.

Commands guarded by an entitlement refuse with an explicit error naming the entitlement they need. Optional online data sources may instead be unavailable while local work continues.

RouteRTL uses a local signed-token check to control access to the designated features. The core is source-available, so the check can be read and modified. Obligations attached to a Pro subscription are set out in the written terms supplied before purchase, and those terms control where they conflict with this page.