Community plan
The feature limits
Section 1.14 of the Rigless License defines the Community plan's feature limits by pointing here. A change to this page only applies to versions of the software released after the change, so a build you already have keeps the limits it shipped with.
Version 1.2, effective 3 October 2026.
| Capability | Community plan |
|---|---|
| Plants per session | One |
| Flight recorder: replay, diff, coverage, time travel | Not included |
| Campaigns over seeds and schedules | Not included |
| The Rigless server: hosted or self-hosted runners, SSO, audit log | Not included |
| Running rigless-hil unattended in your own CI | Permitted, within the limits above |
| Support | None. Issues on the public repositories are welcome |
| Everything else the open runtime and the engine do | Included, and production use is permitted |
The license decides who can hold the Community plan. In short, that's individuals on personal projects, accredited educational institutions teaching or publishing, projects with no revenue or funding, non-profits under ten people, and organizations under ten people with less than one million US dollars in both annual revenue and lifetime funding, counting affiliates. Governments can't hold it. You declare eligibility by using it, and the license's own rules are stricter than this summary.
None of this applies to the open runtime, which is MIT or Apache-2.0. These limits are about the engine.
History
| Version | Effective | Change |
|---|---|---|
| 1.0 | 9 September 2026 | First publication. |
| 1.1 | 1 October 2026 | No limit changed. It brought the line on the open runtime's license up to date. |
| 1.2 | 3 October 2026 | No limit changed. The open runtime's license reads MIT or Apache-2.0, as the crate says from 0.1.0, which runs on a core of its own. |
Questions to hello@riglesslabs.com.