Runtime License
For standard governed runtime use in a customer environment with agreed project, workcell, and support scope.
Commercial packaging
Commercial packaging and licensing
FoldEngine is licensed as an offline governed runtime. It is not sold as seats, API credits, or a hosted SaaS subscription.
This page explains how proof-ladder pricing, diagnostic licensing, runtime activation, expiry, renewals, support, ownership, privacy, and offboarding work before formal procurement begins.
Licensing
Runtime licenses match deployment posture
FoldEngine customers license a governed runtime deployment and the support surrounding it. A deployment typically means one managed runtime environment, its agreed evidence boundary, and the project or workcell capacity associated with that environment.
Diagnostic License
For the bounded 30 to 45 day governed repo diagnostic used to confirm fit, operating posture, and buyer confidence before broader runtime licensing.
Enterprise License
For broader team, project, review-queue, and organizational operations use after a successful pilot or scoped proof with expanded onboarding and support commitments.
Regulated Deployment License
For sensitive, regulated, audit-heavy, or tightly bounded offline environments requiring deeper deployment controls.
Diagnostic terms
The governed repo diagnostic is a bounded commercial engagement
Diagnostic Runtime is not broad Production Runtime. The diagnostic exists to prove fit, validate operating boundaries, and establish whether FoldEngine should expand into a licensed governed runtime in the customer environment.
- Typical duration: 30 to 45 days.
- Deliverables: repo readiness assessment, construction blueprint, evidence pack, review handoff, and a go / no-go expansion recommendation.
- Evaluation objectives and success criteria are defined at the beginning of the engagement.
- Extensions may be offered by mutual agreement when the customer needs more time to complete a bounded evaluation objective.
- If the evaluation is not converted, the runtime is removed or deactivated according to the agreement and customer environment plan.
- An optional Founding Customer program may be offered when fit, timing, and capacity align.
Runtime expiry
What happens when a license term ends
Evaluation concludes at the agreed term unless converted or extended. Generated documentation, evidence, receipts, and customer repositories remain customer-owned. Runtime execution may become unavailable after expiry depending on the license and agreement.
Renewals
Renew by agreement, not by hidden automation
Renewals are handled as a commercial review covering deployment scope, support level, version path, and customer priorities. FoldEngine does not present automatic renewals as the default model.
Updates
Major, minor, security, and documentation updates
Commercial agreements define access to major releases, minor releases, security updates, documentation updates, and compatibility guidance. Update delivery remains controlled and environment-aware.
Support tiers
Support follows deployment seriousness
Evaluation
Deployment help, buyer/operator check-ins, and response targets appropriate for the 45-day validation window.
Business
Standard runtime support for one team or one primary deployment with planned update coordination.
Enterprise
Broader review, organizational coordination, and stronger response expectations for larger governed operations.
Strategic
High-touch deployment planning, operational review, and executive coordination for sensitive or strategic environments.
Responsibilities
Shared operating responsibilities stay explicit
Customer responsibilities
- Prepare the environment and maintain local infrastructure.
- Protect credentials, backups, and operating access.
- Review outputs and approve delivery-boundary decisions.
- Maintain internal policy and decision ownership.
FoldEngine responsibilities
- Deliver the licensed runtime and supporting materials.
- Provide installation and onboarding guidance.
- Support updates according to the agreement.
- Preserve the supported authority boundaries of the runtime.
Ownership
Customers own their repositories, source, generated work, evidence, and receipts. FoldEngine retains ownership of the FoldEngine software, trademarks, and documentation unless a written agreement says otherwise.
Acceptable use
FoldEngine is not licensed for illegal activity, malware development, unauthorized intrusion, rights violations, or unsafe use of material the customer lacks permission to handle.
Warranty / disclaimer
FoldEngine assists governance and evidence-backed review. Human review remains required. It does not guarantee every defect is detected, create automatic compliance certification, or hold autonomous delivery authority.
Privacy
FoldEngine Runtime is offline and customer-environment oriented. Customers control their data and environments. Continuous cloud connectivity is not required for the commercial model described here.
Export and offboarding
Customers keep their evidence and can remove the runtime
At the end of an engagement or license term, customers retain their evidence, generated documentation, and receipts. Runtime software can be removed from the environment according to the agreed offboarding plan, and support concludes according to the commercial agreement.
Not formal contract terms
Enterprise-readable operating model before legal paper
This page helps procurement, IT, and legal readers understand the commercial posture before formal agreements are drafted. It does not replace negotiated order forms, statements of work, or signed legal terms.
FAQ
Commercial questions buyers usually ask first
Can I evaluate before buying?
Yes. The standard path is a 45-day Evaluation Runtime engagement that proves fit, boundaries, and operating value before a production license is discussed.
Do I need Internet access?
Not for the core offline commercial model. FoldEngine is positioned as a local-first governed runtime rather than a cloud-only subscription service.
Can I renew?
Yes. Renewals are handled through commercial review of scope, deployment posture, support level, and update path.
How are updates delivered?
Updates are delivered as controlled runtime and documentation releases according to the active agreement and supported environment plan.
What happens when my evaluation expires?
The evaluation concludes, converts, or is extended by agreement. Customer-owned evidence and documentation remain available even if runtime execution access ends.
Can I move the runtime?
Potentially, but it should be treated as a deployment and support question rather than assumed by default. The environment boundary matters.
Who owns generated outputs?
Customers own their generated work, evidence, and receipts. FoldEngine retains ownership of the FoldEngine product and its related materials.