Final beta / evaluation
The final beta starts with a workflow you already know.
We are accepting applications before production release. Each evaluation is scoped around a real workflow, explicit data boundaries and evidence the operator can judge.
Applications reviewed by JTF · no guaranteed acceptance · no release date invented
What it costs
Beta participation is free.
Nothing to apply, nothing to evaluate
There is no application fee, no evaluation fee, and no card on file. If the evaluation is a fit we scope it, run it, and you tell us where it broke.
Every published system has a free tier
Each system in the register has a free version, and it stays free. It is deliberately limited — every product page states where that system actually is rather than implying more.
Outside-vendor work is opt-in
A few capabilities are bought from a third party — a commercial measurement report is the usual one. Those are requested per job, quoted before they run, and nothing is charged unless you ask for one.
Production pricing is published before release. Beta operators see it first.
Step 01
Inventory the current stack.
Your baseline
Count what the current stack costs before anyone promises savings.
Local calculation only. These figures are not transmitted or stored.
Step 02
Scope the beta evaluation.
Choose the workflow
Bring work your team already understands and can evaluate from experience.
Name the evidence
Agree on what success, failure and an exception look like before the run.
Set the boundary
Define the data allowed into the test and the person responsible for reviewing its output.
Step 03
Run the workflow and report what happened.
The final beta exists to find release defects. Feedback should identify where the system helped, failed, or needs a clearer human decision gate.
Final beta · applications open
Bring the invoices and one workflow.
We are accepting roofing operators who will test one real workflow, tell us where it breaks, and help shape the production release.