Platform Licensing
Licensing is designed for enterprises adopting ProDevFactory internally: governed execution, controlled environments, and audit-ready delivery — without surrendering human authority.
Platform license tiers
No startup-style pricing tables. Tiers define capacity and governance boundaries; commercial numbers are finalized through enterprise agreements.
Starter
Entry adoption
For controlled pilots and early internal adoption where governance foundations must be established first.
- Intended audience: single program / early platform team
- System capacity: limited number of governed systems
- Environment allowance: Sandbox + Staging foundations
- AI autonomy tier: Advisor / Assisted focus
- Governance scope: baseline approvals and traceability
- Support level: onboarding guidance and standard support
Growth
Multi-team
For expanding adoption across multiple teams with stronger controls and repeatable delivery patterns.
- Intended audience: multiple teams / shared platform capability
- System capacity: multiple governed systems
- Environment allowance: Sandbox + Staging with controlled promotion patterns
- AI autonomy tier: Assisted with governed automation boundaries
- Governance scope: stronger policy enforcement and evidence readiness
- Support level: enhanced support and enablement
Scale
Enterprise-wide
For program-grade adoption where governance maturity, environments, and operational visibility are non-negotiable.
- Intended audience: enterprise programs and long-lived platforms
- System capacity: higher scale across systems and teams
- Environment allowance: Sandbox + Staging + Production governance model
- AI autonomy tier: Autonomous (governed) available where approved
- Governance scope: advanced controls, audit evidence patterns, policy alignment
- Support level: enterprise support and operational enablement
OEM
Partner-ready
OEM is a separate commercial track for partners delivering under their own brand. See OEM page for structure.
- White-label commercial model
- Partner delivery templates and operating model
- Multi-client governance and segmentation
- Strategic partnership structures
AI agent capacity and autonomy tiers
Autonomy is not “more AI”. It defines what agents are allowed to do without a human decision — and how governance can override behavior.
Advisor Mode
Agents provide analysis, options, and recommendations. Humans approve and execute decisions. Suitable for early adoption and high-control environments.
Assisted Mode
Agents draft plans, generate implementation artifacts, and prepare changes for approval. Humans remain required at governance gates and promotions.
Autonomous Mode
Agents can execute within approved boundaries (policy + scope + environment), but cannot bypass governance. Humans retain override and approval on critical gates.
Human-in-the-loop boundaries
- Humans remain the deciders for scope, policy, and production promotion.
- Autonomous execution is constrained by approved policy and environment boundaries.
- Every critical action must remain traceable and auditable.
- Governance override can pause, block, or require approval at any time.
Environment and system licensing logic
Enterprise cost and governance risk change materially by environment. Licensing separates environments to keep commercial scope and operational controls explicit.
Sandbox
Where systems are designed and built safely. Ideal for experimentation under policy without production exposure.
Staging
Where validation, evidence, and approval gates operate before any production promotion.
Production
Where strict controls, audit evidence, operational readiness, and risk policies are enforced.
Multi-system concept
Organizations often govern multiple systems (ERP, portals, vertical apps). Licensing scales by number of systems and the environments you operate for each.
Commercial positioning
- Enterprise contracts: annual agreements with defined scope and governance commitments.
- Custom quotes: shaped by systems, environments, autonomy tier, and support level.
- Regional readiness: localization and compliance language support procurement requirements.
- Compliance considerations: auditability, approvals, segregation of duties, and data ownership expectations.
Request a licensing recommendation
Share your governance constraints (approvals, audits, security posture) and how many systems/environments you plan to operate.