Bounded launch scope
The current launch scope centers on bounded Linux project/task workflows. Broader operating-system support is not claimed here.
Current limitations ยท 2026-10-05
What StateHinge does not claim yet.
The business and payment path are live. The product scope is intentionally narrower than the website itself: current support claims stay tied to verified evidence.
Named integrations
The product is positioned around existing coding-agent workflows, but named-agent integration claims are withheld until their exact integration evidence is closed.
External-machine onboarding
Clean another-machine installation/onboarding is not claimed as universally verified in this BUSINESS evidence set.
Customer proof
No real customer pilot or paid-customer case study is presented as proof yet. Pricing remains a launch hypothesis until customer evidence accumulates.
Why keep this page public?
Because StateHinge is selling a control boundary. Trust improves when verified capability, current limits and future work are separated instead of blended into one marketing claim.
Use the right first workflow
Start bounded, then expand from evidence.
If your workflow falls outside the current scope, ask before paying.