Pricing
Simple pricing: adopt the toolkit first, then decide whether you need extra help.
SimplicityTools is open source, so the default answer is still easy: install it, run it, and see whether the output changes team behavior. If you need rollout help, start in the open and escalate only when the work truly needs a different support channel.
- The CLI, analyzers, filters, TCA libraries, and sample solutions.
- The docs, integration guides, and reference pages in this site.
- The normal open-source support path through issues and repository discussion.
What you get without paying
The open-source path is the primary product path, not a teaser for a hidden tier.
CLI + report
Analyze a solution, generate a report, and protect a baseline in CI with no feature gating.
Analyzer package
Install the Roslyn package and get SF0001-SF0007 feedback in the IDE and normal builds.
Reference docs
Use command pages, filter docs, configuration guidance, and library usage examples directly from the site.
Samples
Use the checked-in sample solutions to teach healthy shape versus accidental complexity.
If your team needs rollout help
There is no separate productized pricing table in the repo today. The honest next step is still to start in the open unless the work clearly needs a private conversation.
Open an issue
Best for bugs, missing docs, and product feedback that should help every team after yours.
Direct contactStart with the maintainer
Best for training, adoption coaching, or conversations that need project-specific context.
Self-serviceUse the docs first
Best when your real blocker is not support, but the need for a clearer command, analyzer, or configuration reference.