From public proof to a controlled engagement.
Launch is the qualification and access surface for Dominion OS™, the Fractal5 SaaS Suite, governed builds, pilots, private deployments, and enterprise work.
Understand the system on `/dominion-os`, inspect public proof on `/demo-1`, explore the catalogue on `/store-preview`, then use this page to choose the right governed access path.
Choose the smallest path that can prove value.
Different buyers need different levels of access, evidence, procurement, security, and implementation support.
Demo bridge
A sandboxed route for sample data, guided scenarios, public-safe runtime evidence, manifests, and proof surfaces.
Governed build
A scoped engagement for a website, dashboard, workflow, portal, intelligence system, data surface, AI-native build, or custom module.
Pilot capsule
A bounded institutional pilot with success criteria, roles, source classes, security boundary, implementation plan, and expansion decision.
Controlled deployment
A provider-specific, client-owned, private-cloud, or sovereign deployment path where runtime, identity, security, data, observability, support, and release evidence are confirmed.
License / extend
Licensing, module extension, integrations, APIs, or custom deployment arrangements only under confirmed legal, technical, commercial, and support terms.
Exploration & R&D
Research, prototypes, frontier systems, and experimental pathways can begin as bounded work without representing them as generally available products.
Fit → discovery → pilot → evidence → deployment.
The launch path keeps commercial ambition high while making each stronger commitment depend on current evidence.
Executive fit
Identify the mission, buyer, users, operating problem, and likely Fractal5 capability.
Discovery
Map stakeholders, systems, risks, data, security, support, procurement, and success criteria.
Pilot
Create a bounded proof or implementation capsule with explicit acceptance criteria.
Evidence
Review the result, controls, receipts, claims, limitations, technical state, and handoff.
Deployment
Expand only when the buyer, evidence, commercial terms, and operating boundary support it.
Simple public tiers. Scoped enterprise work.
Public pricing communicates the hosted tier structure. It does not replace discovery for private, regulated, institutional, licensed, marketplace, API, or custom deployments.
Starter
$49 / month1 seat · personal users, creators, individual command workflows.
Standard
$149 / month3 seats · small teams, pilots, early dashboards, and professional workflows.
Pro
$399 / month10 seats · Connect-module posture, delivery teams, and repeatable operations.
Enterprise / Gov
CustomRole separation, private or client-owned deployment, compliance review, onboarding, support, procurement, and scale.
Commercial boundary: production, private-cloud, government, regulated, licensed, API, marketplace, and enterprise deployments require scoped review. Marketplace packaging remains a controlled future path unless a current listing and its commercial/support terms are independently confirmed. Hyperscaler paths may include Google Cloud, Microsoft Azure, AWS, Oracle Cloud Infrastructure, or private environments depending on the engagement; provider mention does not establish universal deployment readiness.
Launch converts interest. It does not manufacture certainty.
The strongest Fractal5 sales path is one where the public story, proof surface, commercial catalogue, engagement scope, and implementation evidence all agree.
Private by default
Customer data, credentials, source code, internal services, production workflows, signing material, and restricted systems remain outside the public launch surface.
Claims fail closed
Availability, runtime, compliance, certification, API, marketplace, deployment, and regulated-use language stays bounded until the required evidence is current.
Expansion by proof
A governed build can become a larger Fractal5 operating layer only after the initial work demonstrates value, controls, and an acceptable deployment boundary.
Bring the serious problem. Start with the right-sized proof.
Fractal5 can frame the smallest credible engagement that clarifies the system, proves value, protects the boundary, and creates a disciplined path toward deployment.