We read everything that arrives. Early access requests get a reply from a person, not an autoresponder.
Request early access
Tell us what you are trying to build and what makes it hard. The most useful details are:
- The domain. What does the software do, and what is the part with the fiddly rules?
- Your current practice. Do you already write Gherkin, keep an OpenAPI document, or write specs some other way?
- Your constraint. What is actually blocking you today — review load, unclear requirements, slow feedback, or something else entirely?
If the honest answer is that Trigger & Trial is not a fit, we will say so and point you at something more appropriate. We would rather turn down a bad fit early than waste a month of your time.
Report a problem
If you are already using the platform, report problems with as much of the following as you can:
- The build ID and the spec commit SHA
- The exact error output or log excerpt
- What you expected and what happened instead
The build ID matters most. Every build is pinned to an immutable spec snapshot and a recorded model version, which means most reported problems are reproducible rather than a matter of recollection.
Other questions
Pricing, self-hosted deployment, security review documentation, and anything else — same address.
Legal and abuse
- Abuse reports (someone is using a trial environment to run something they should not): please include the environment URL, so we can act on it directly.
- Copyright complaints about material hosted in a trial environment: see our Terms of Service, which set out the procedure and the designated agent.
Privacy
We do not add third-party analytics or tracking scripts to this site, and we do not run third-party advertising pixels. What we do collect is described in the Privacy Policy.