FAQ
Direct answers before you try it.
What StateHinge is, what it costs, what the current scope is, and what we intentionally do not claim.
What is StateHinge?
A control layer around an existing AI coding-agent workflow. It keeps candidate work separate from accepted project state, runs declared checks, asks a human to approve the exact candidate, and records promotion/recovery evidence.
Is this another coding agent?
No. StateHinge is designed to sit around the agent/workflow you already use rather than replace it.
What problem is it trying to solve?
The gap between “the agent changed files” and “our team accepts this exact change as trusted project state,” plus the review/recovery work when runs fail, drift or are interrupted.
Do I need a credit card for the trial?
No. The 14-day trial is cardless and does not automatically convert into a paid plan.
What does it cost?
Launch pricing is Solo $29/month, Team $149/month and Agency $349/month. See the Pricing page for current scope and U.S. business self-service eligibility.
Does it support every coding agent and operating system?
No such broad claim is made. The current launch scope is bounded and Linux-centered; named-agent integrations and broader environments are only claimed when the relevant evidence is closed.
What happens when validation fails?
In the verified core, failed deterministic validation blocks the candidate from being promoted into accepted project state.
Can it roll back?
The verified core includes rollback restoration and evidence that checks the restored baseline. A status saying “rollback complete” is not treated as proof by itself.
Can I use it on production client repositories immediately?
The first workflow should stay inside the current bounded scope. If your use case requires broader production access or an unverified environment, ask before paying.
Where can I ask a question?
Email [email protected] or use the Contact page. Do not send secrets or production credentials by email.
Still deciding?