Architecture
Monoliths, microservices, single-repo and multi-repo systems create different proof and adoption paths.
Pricing
Pay for governed delivery, shaped to your repo.
AI coding tools generate changes faster. SDF helps your team review and trust the resulting PRs faster, with scope, evidence, verification results, risks, and limits attached.
The commercial path is Free readiness check → Paid assessment → First governed change → Team operating model. Start with a free readiness check. If there is a fit, paid work covers the assessment, one bounded first governed change, and the team operating model needed to make the loop useful for your repo.
There is no fixed SaaS tier. The paid assessment, first governed change, and optional follow-on support are founder-led, operator-assisted, and scope-agreed. SDF works inside your existing repository and delivery process; your team keeps approval, merge, release, and product judgement.
Why no flat tier yet
The price reflects the delivery work.
A Rails monolith, a TypeScript service mesh, a legacy mobile app, and a mixed-stack platform do not need the same first governed change or operating model.
The quote covers the work required to fit governed delivery to your repo: how changes are scoped, checked, evidenced, reviewed, and handed off. It does not buy more generated code.
Stack
Rails, TypeScript, React, mobile, legacy, greenfield, and mixed stacks may need different evidence and verification shapes.
Review workflow
Team standards, CI maturity, release expectations, and reviewer pressure determine what evidence will actually help.
Free readiness check
Check the fit before paying.
The free readiness check looks at your app and repo shape, review pressure, current AI use, quality gates, and whether one governed change would be a useful proof.
You get a practical next-step recommendation: continue to a paid assessment, scope a first governed change, resolve blockers first, or choose another path. It does not require blind repo access.
Assessment output
Practical fit guidance
-
What it looks for
Repo and app context, review pressure, AI-assisted workflow, quality gates, and evidence gaps.
-
What you receive
Fit guidance, visible blockers, and a practical recommendation for the next step.
-
What it avoids
No hosted scan, automatic execution, repo mutation, approval, merge, release, or correctness guarantee.
Early adopter path
For teams feeling the review bottleneck.
SDF is proven daily in its own delivery: the SDF CLI repo, this GTM app, and Explore all run governed changes through the loop. The next step is more real-world proof across different teams, technologies, and review cultures.
Early adopters help shape how the operating model fits their repo and workflow. The value is not cheaper code generation. It is clearer review: evidence-backed changes, verification truth, known limits, and team standards carried into AI-assisted work.
Good fit
Teams already experimenting with AI coding assistants and feeling review, quality, or governance pressure.
Control fit
Technical leaders who want delivery speed without giving up engineering discipline or human review control.
Proof fit
Teams willing to prove the approach on one bounded governed change before turning it into repeatable practice.
What pricing is based on
What shapes the quote.
Once fit is clear, the quote reflects the work needed to give reviewers useful evidence and keep delivery under human control in your environment.
App and repo complexity
How much surface area the first governed change and operating model need to cover.
Tech stack
Rails, TypeScript, React, mobile, legacy, greenfield, and mixed-stack context.
Test and CI maturity
Whether existing checks already give reviewers useful evidence or need clearer results and limits.
Repos and services
Single app, multi-repo, service boundaries, and release coordination.
Governance needs
Review expectations, team standards, risk boundaries, and the evidence reviewers need to decide.
First governed change
Whether the first governed change is tiny, representative, cross-cutting, or blocked.
Engagement shape
Assessment-only, first governed change, team operating model, or ongoing support.
Commercial options
What you can engage us for.
These are scope-agreed engagement shapes, not fixed SaaS tiers.
Start here
Free readiness check
A no-cost fit check that decides whether SDF is worth exploring for your app and team.
- Lightweight context review
- Fit and blocker guidance
- Recommended next step
After paid assessment
First governed change
A bounded proof that takes one useful change through the executable verification loop when the paid assessment supports it.
- Scope and acceptance criteria
- Receiver-owned checks applied
- Evidence and checked reviewer handoff
Adoption
Team operating model
Adapt what proved useful to your repo, stack, review workflow, guidance, verification boundary, and evidence expectations.
- Repo-specific guidance
- Team standards carried forward
- Reviewer workflow and evidence expectations
Optional follow-on
Ongoing governed delivery support
Optional follow-on support keeps the operating model useful as teams, stacks, risks, and AI-assisted workflows change.
- Playbook refresh
- Evidence review
- Governance adaptation
Next step
Find out whether the proof is worth paying for.
Share the app, team, and workflow context that matters. The free readiness check is designed to tell you whether SDF is worth pursuing.
If there is a fit, we will scope the paid assessment, first governed change, or team operating model your repo actually needs. Optional follow-on support remains available when useful.