Architecture
Monoliths, microservices, single-repo and multi-repo systems create different proof and adoption paths.
Pricing
Pricing starts with your app.
SDF pricing depends on the repo shape, stack, team standards, governance needs, and review workflow it has to fit.
The current entry point is a free readiness check. It helps decide whether SDF is a fit, what proof would be useful, and whether a paid assessment or governed PR proof is worth discussing.
No fixed SaaS tier is implied here. Assessment, proof, and support are assisted, scope-agreed, and bounded by human-controlled review.
Why no flat tier yet
Every delivery environment is different.
A Rails monolith, a TypeScript service mesh, a legacy mobile app, a greenfield React product, and a mixed-stack platform do not need the same setup or proof shape.
SDF has to fit the team’s existing delivery workflow: how work is scoped, tested, reviewed, evidenced, approved, and handed off. A generic pricing box would hide the work that determines whether governed AI-assisted delivery will actually help.
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 burden change the work SDF has to support.
Free assessment
Start with a no-cost fit check.
The free assessment is a low-risk first step. It looks at app and repo shape, review pain, current AI usage, quality gates, and whether SDF can produce a useful first governed PR.
The output should be a practical recommendation: continue to a paid assessment, shape a proof sprint, wait until blockers are clearer, or choose another path. It is not a sales trap and 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 it produces
Fit guidance and a practical next-step recommendation, not a generic subscription pitch.
-
What it avoids
No hosted scan, automatic execution, repo mutation, approval, merge, deploy, or correctness guarantee.
Early adopter path
Early teams help shape the operating model.
SDF has been proven internally and across selected app and stack contexts, but it is intentionally looking for more real-world proof across different teams, technologies, and review cultures.
Early adopters get practical influence over how SDF develops for their stack, repo shape, team workflow, and governance needs. The value is not cheap AI coding. It is governed delivery, reviewer confidence, evidence-backed PRs, and team standards carried into AI-assisted work.
Good fit
Teams already experimenting with AI coding assistants and feeling review, quality, or governance pressure.
Founder fit
Technical founders who want speed without losing engineering discipline or human review control.
Proof fit
Teams willing to prove the approach on one bounded governed PR before turning it into repeatable practice.
What pricing is based on
The quote follows the proof shape.
Once fit is clear, commercial scope is based on the work needed to make governed delivery useful in your actual environment.
App and repo complexity
How much surface area the first proof and operating model need to cover.
Tech stack
Rails, TypeScript, React, mobile, legacy, greenfield, and mixed-stack context.
Test and CI maturity
Whether verification evidence is already useful or has to be made reviewable first.
Repos and services
Single app, multi-repo, service boundaries, and release coordination.
Governance needs
Review expectations, team standards, risk boundaries, and evidence depth.
First proof scope
Whether the first governed PR is tiny, representative, cross-cutting, or blocked.
Engagement shape
Assessment-only, paid proof sprint, team/front-door setup, or ongoing support.
Commercial options
Lightweight options, not fixed tiers.
These labels describe possible engagement shapes. They are not fixed SaaS packages or discount mechanics.
Start here
Free assessment
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
Scoped proof
Paid proof sprint
A bounded proof designed around one useful governed PR where the assessment supports it.
- Scope-agreed work item
- Evidence-backed PR surface
- Human-controlled review
Adoption
Team/front-door setup
Adapt the governed PR spine to your repo, stack, review workflow, playbooks, and quality gates.
- Repo-specific operating model
- Team standards carried forward
- Reviewer-facing evidence path
Support
Ongoing governed delivery support
Keep the operating model useful as teams, stacks, risks, and AI-assisted workflows change.
- Playbook refresh
- Evidence review
- Governance adaptation
Next step
Start with a free assessment.
Share the app, team, and workflow context that matters. The first step is low-commitment and designed to tell you whether SDF is worth pursuing.
If there is a fit, the next conversation can scope the right assessment, proof sprint, or front-door setup for your repo.