Cloud self-service is the default product path. Create an account, confirm email and provision a workspace without installing a Token Observe server. Connecting billing does not recover historical conversations; activity and inline governance require routed supported clients. The optional customer-hosted package and its source are private and remain subject to the source-available licence. This website does not grant shared-cloud penetration-testing rights or invent cloud commercial terms.
The licence permits use, modification and self-hosting under licence; reading the entire governance domain before buying, which is possible because the core package is pure functions with zero runtime dependencies; and security research. It forbids redistribution, and it forbids offering Token Observe as a competing hosted service.
The publication right that follows the security research is narrower than the right to do the research, and the difference is worth reading rather than summarising. Section 9.1 lets the Licensee, and any person operating an evaluation, inspect, test, fuzz, penetration-test and reverse-engineer the software as deployed on infrastructure they control, and commission a third party to do it for them. Sections 9.2 and 9.3 are drafted as the Licensee’s: benchmark results may be published with no pre-approval, provided the publication names the version tested and the configuration used, and security assessment findings may be published, naming the software, after coordinated disclosure. So an evaluator who intends to publish before an Order Form exists holds the right to attack the software but, on the drafting, should get the right to publish agreed in writing rather than read it across. The licence records that the maintainers already publish their own outstanding defects and says section 9 is meant to be consistent with that practice rather than to suppress yours. One caveat travels with every clause quoted in this one: the published licence is a template pending review by counsel rather than legal advice, and the final terms are the ones in your signed agreement.
The commercial shape around it is published in the same register: what a subscription counts and what it never counts, what the thirty-day evaluation grants and what it excludes, the support severities and response targets, and the three published reasons there is no availability service level. Prices are not published, and the reason is stated on the page rather than held back for a conversation.