Capability can be dual-use. Authority must be explicit.
Licensing connects the actual customer, mission, authorized users, product scope, jurisdictions, deployment environment and controls before stronger rights are granted.
Mission × End User × Jurisdiction × Controls × Written Authority
Mission first. Written scope. Reassess when facts change.
Licensing proceeds from the actual use case, not from a generic product label.
Mission
Define intended use, operators, end users, accountable authority and supported decisions.
Jurisdiction
Identify countries, access locations, hosting, administrators, remote paths and cross-border movement.
Classify
Review software, cryptography, technical data, integrations, third-party rights and regulatory exposure.
Control
Bound identity, privilege, logging, keys, human authority, residency, rollback and incidents.
Authorize
Signed terms establish the permitted customer, users, modules, use, environment and term.
Reassess
Material changes to mission, end user, jurisdiction, hosting, integration or access can trigger re-review.
Rights follow the approved deployment.
Engagement models are considered individually. Availability depends on current product state, mission, end users, jurisdictions, deployment boundary, security review, support and governing documents.
Use approved capabilities as a service.
Operated for a defined organization, team, program or mission under an approved boundary.
Deploy into an approved environment.
Self-hosted, on-premises, private-cloud, sovereign or client-controlled deployment where the release and controls support it.
Extend approved interfaces.
Scoped API or SDK rights for defined integrations, modules and environments.
Prove the mission before expansion.
Time-limited evaluation with agreed users, data handling, boundaries and success criteria.
Discuss defined embedded rights.
Product-specific OEM, embedded or white-label rights require explicit written scope.
Structure the engagement around the mission.
Commercial, public-sector, security, defence, nonprofit, research and strategic-partner requests are assessed individually.
License what is actually available.
Public availability statements describe current access posture only. They do not themselves grant entitlement, deployment, export or regulated-use rights.
| Product / Surface | Public Posture | What That Means |
|---|---|---|
| Dominion OS™ 1.0 | Inquiry & governed access | Customer-specific scope, use, deployment, security, support, fees, limits and written terms are required before entitlement. |
| Windows Business | Evidence-gated release track | Provider and distribution claims remain tied to verified release evidence. Catalogue presence does not create a public binary. |
| Dominion for Politics | Controlled engagement | Real controlled campaign deployment history is distinct from the synthetic public demo. No public downloadable Politics binary is represented. |
| Fractal5 SaaS Suite | Configure & qualify | Modules can be scoped within approved Dominion OS or account-specific engagements according to current availability and evidence. |
| Public Demonstrations | Illustrative access only | Demonstrations show operating concepts. They do not grant production, redistribution, commercialization, deployment or regulated-use rights. |
This public licensing page intentionally describes current product and access posture. Internal previews, future major versions, research roadmaps and unreleased release plans are not public licensing offers unless Fractal5 deliberately publishes them through a separate, approved, versioned surface.
Authorization follows the mission.
The written record should connect the customer, end use, end users, exact product scope, jurisdictions, deployment controls, commercial terms and approved access.
Missing, inconsistent or materially changed information can stop activation, expansion, transfer or continued deployment.
Capability does not outrun authorization.
Product access, technical capability and legal authority are separate questions.
This page does not classify the product.
Actual requirements depend on the specific software, technology, technical data, cryptography, integrations, end use, end users, destinations, access paths, jurisdiction and facts.
Nothing on this page is a formal export classification, permit, exemption, certification, legal opinion or government authorization. Where a transaction requires specialist legal, regulatory, security or classification review, that review remains separate from this public page.
Controlled deployment is not a public binary.
Dominion for Politics can be delivered through controlled engagement where appropriate. Public deployment records remain separate from private campaign operations, private campaign data, credentials, protected correspondence and internal security details.
A deployment record does not itself imply electoral success, voter influence, endorsement, electoral-authority approval or certification.