Early teams can move fast with coding agents but lose track of intent, risk, and current state. FactionOS frames the wedge as local mission control with explicit optional surfaces and no inflated metric promises.
Founders
Run multiple agents without losing the shape of the work.
Show the product wedge clearly: local mission control for agent work, a guided demo for exploration, and docs for setup context.
Founders need to understand whether FactionOS makes agent work more controllable without leaning on unverifiable traction, ROI, or productivity numbers.
- Focuswedge
The problem
Where the work loses its shape.
Before and after
What changes with an operating picture.
Multiple agents
Before
Parallel agents create progress without a single operating picture.
With FactionOS
A mission view can keep lanes, lineage, status, and checkpoints visible.
Remote execution and hosted validation are separate product concerns.
Product wedge
Before
Agent tooling reads as another terminal helper or generic dashboard.
With FactionOS
FactionOS is positioned as local mission control for agent coding work.
Copy stays concrete and avoids ROI, speed, or traction metrics.
Zero-install preview
Before
Readers need a way to inspect the product feel before setup.
With FactionOS
The external demo shows a guided product-like preview.
The zero-install demo is a guided preview and stays separate from local sessions.
Risk clarity
Before
Agent autonomy can look impressive while review risk remains vague.
With FactionOS
Approval, replay, and diagnostic language keeps control points visible.
The website cannot grant approvals, run tools, or validate production hosts.
Surface mapping
Which surface does the job.
Availability and guardrail columns keep local, optional, and outbound clearly separated.
| Capability | Surface | Availability | Guardrail |
|---|---|---|---|
| Cockpit | apps/web cockpitThe primary product surface for seeing missions, lanes, and review state. | local | Cockpit behavior belongs to the local product runtime. |
| Demo | demo.faction-os.comA separate guided preview for inspecting product feel without setup. | preview | The zero-install demo is a guided preview and stays separate from local sessions. |
| Docs | public GitBookPublic docs own setup context, runtime details, and validation guidance. | docs | Docs are separate from the website and do not create hosted accounts. |
Operator proof
How this path shows up in the cockpit.
Wedge
Mission control language
The product story stays centered on local visibility, review, and coordination.
Evidence Useful when explaining why FactionOS is not a generic analytics dashboard.
Productivity percentages, ROI, and traction metrics belong in direct evidence.
Preview
Guided demo handoff
Readers can open the demo to inspect a product-like surface without setup.
Evidence Useful when a founder wants product feel before reading installation docs.
The demo does not connect to local state or hosted customer data.
Boundaries
What stays true for this role.
- noneMetrics
Founder copy avoids ROI, revenue, adoption, speed, and productivity metrics.
- previewDemo
The external demo is a guided preview separate from local sessions.
Founder path
Open the demo, then compare the product map.
Zero-install product preview hosted separately from this website. Use the product page for surface boundaries, and the docs when you want setup detail.
This path is for exploration. Hosted accounts, analytics dashboards, customer workspaces, and quantified outcomes are separate conversations.