Offline governed runtime
A local governed operating environment for AI-assisted software work with protected source and explicit authority boundaries.
Commercial model
FoldEngine pricing now follows a proof ladder: begin with one repo or one governed change problem, prove the value, then expand only when the evidence supports a larger deployment.
The commercial entry point is a bounded diagnostic, not a headline enterprise program.
Pricing principle
You are not buying seats. You are not buying API calls. You are not buying a chatbot.
A local governed operating environment for AI-assisted software work with protected source and explicit authority boundaries.
Capacity for governed work across projects, workcells, reviews, and evidence-preserving flows.
Preserved evidence, receipt chains, review surfaces, and continuity across repeated work and repeated decisions.
Guided intake, repository takeover, project workspaces, organization operations, review, and environment readiness surfaces.
Qualified evaluation, deployment support, operator sessions, and buyer-facing evaluation reporting.
Runtime support for governed work without silently widening authority across consequential delivery boundaries.
Proof ladder pricing
Final pricing depends on deployment scope, repository count, governance requirements, support model, implementation services, and organizational rollout. Enterprise programs follow successful proof, not the other way around.
1. Governed Repo Diagnostic
30–45 days
One repo or one bounded change problem with a readiness assessment, construction blueprint, governed trial where admissible, and review handoff.
2. Founding Customer Runtime
One team, one to two repos, guided deployment, customer readiness, organization governance profile, governed engineering workflow, and onboarding support.
3. Team Runtime
Multiple users, bounded repository scope, supported stacks, governed trial execution, governed patch or development candidates, review handoff deliverables, and operational continuity.
4. Regulated Pilot / Multi-Repo Deployment
Multiple repositories or one regulated workstream with multi-repo readiness, governed construction and development deliverables, audit-ready evidence handoff, and custom delivery support.
5. Enterprise / Regulated Program
Services-heavy, custom, multi-repository deployment for buyers who have already completed a successful pilot or scoped enterprise proof.
Governed Repo Diagnostic
The governed repo diagnostic is the primary commercial entry point for serious buyers. It proves repository understanding, construction quality, review handoff quality, and governed trial readiness before broader deployment planning.
Founding customer runtime
For the first controlled customers, FoldEngine may be offered as a guided deployment for one team and one to two repositories after the diagnostic proves fit, stack readiness, and review value.
Licensing options
Team Runtime fits multiple users with bounded repository scope and supported stacks. Enterprise and regulated programs are services-heavy follow-on deployments after a successful pilot or scoped proof.
Buyer promise
Start with one repository or one governed change problem. FoldEngine will produce a construction blueprint, readiness assessment, governed candidate work package where admissible, evidence trail, review handoff, and a clear next-step recommendation.
Compliance framing
FoldEngine helps preserve the evidence needed to answer: what was proposed, what was allowed, what was blocked, who reviewed it, and what changed over time.
It does not guarantee compliance, replace policy, or act as a certification surface.
Comparison to consultants
Consultants can help solve one project.
FoldEngine gives your team a repeatable governed operating environment for future projects, future reviews, future evidence, and future AI-assisted work.
For some teams, the right path is both: use consultants where needed, and use FoldEngine to make the operating model repeatable afterward.
What happens after you request a diagnostic
Buyer self-qualification
Probably not a fit if you only need a chatbot, generic code assistant, or a fully unattended code agent.
Non-claims
Next step
The right commercial entry point is usually a governed repo diagnostic that proves fit, boundaries, evidence value, and operator workflow in your environment before a larger runtime commitment.