Built for teams that ship continuously

Public Beta • Free until March 31, 2026

Run delivery from one source of truth, not scattered tools.

ConstructOS connects project intent, specifications, tasks, notes, rules, and AI execution in a single operating layer. Your team keeps context with vector plus graph retrieval, moves faster, and keeps an audit trail. Deployment model is self-hosted only through Docker Compose.

  • CQRS + Event Sourcing Core
  • Vector + Graph Retrieval
  • Jira + GitHub MCP Integrations
  • Codex Required
  • Self-Hosted Only
  • Public Beta: Free Until March 31, 2026

Self-hosted guide

Coming soon

The full Docker Compose installation and operations guide is being finalized. Join the waitlist for the release notice, or request early access and we will share rollout steps directly.

Core capabilities

Everything needed to execute with context

Specification-driven execution

Link every task and note to the specification and keep scope traceable from intent to done.

Operational memory

Keep project rules, notes, references, and decisions attached to the work where teams need them.

AI with guardrails

Use MCP tools and automation workflows with first-class Jira MCP and GitHub MCP integrations, plus support for additional MCP connectors.

Hybrid retrieval (vector + graph)

Use semantic vector search plus graph traversal to surface dependency-aware context with precision.

Live workspace visibility

See changes as they happen with real-time notifications and activity updates.

Enterprise-ready foundation

Built-in licensing controls, structured APIs, and event-level auditability for governance.

System shape

Architecture that engineers can reason about

Deterministic write path

Commands append events, projections update read models, and retrieval combines vectors plus graph context so every state transition stays traceable.

UI --REST/SSE--> API
API --append--> Event Store
Projections --> SQL + Graph
Context API --> Vector Index + Graph

AI execution with guardrails

MCP tools and automation runners operate through explicit command boundaries and policy checks.

Agent --> MCP Tools
MCP --> Domain Commands
Command IDs --> Idempotent Mutations

How it works

From planning to execution in three steps

01

Define intent

Create projects, specifications, and rules that become the source of execution context.

02

Execute with context

Drive tasks and notes from specifications while retrieving context through vector and graph search.

03

Automate safely

Run agent workflows through MCP with traceable outcomes, retries, and controls.

Pricing

Simple pricing for self-hosted delivery teams

Public beta is free until March 31, 2026. No automatic charges during beta.

Public Beta

Beta Access

$0 until March 31, 2026

  • Self-hosted deployment and onboarding support
  • Core product features enabled for evaluation
  • No automatic billing during the beta window
Join Beta Deployment

Starter

$9 / user / month

  • Project and task management
  • Specifications, notes, and rules
  • Basic automation access
Request Starter Plan

Enterprise

Custom annual contracts

  • Advanced security and compliance support
  • Private network architecture review
  • Custom onboarding and team enablement
  • Priority support and success channel
  • Procurement and contract support
Talk to Sales

Next steps

Choose what you want to do next

Join waitlist

Get notified when the self-hosted guide and onboarding assets are published.

We only send updates about the self-hosted guide and release milestones.

Book demo

Review architecture, deployment model, and team workflow with a guided walkthrough.

Request plan

Ask for Starter, Team, or Enterprise self-hosted plan details and procurement info.

Deployment onboarding

Get the Docker Compose rollout path and environment setup checklist.

FAQ

Common questions

Is ConstructOS only for software teams?

No. Any delivery team with structured work, dependencies, and knowledge-heavy workflows can use it.

Can we self-host?

Yes. Enterprise plans support private deployment and operational control requirements.

Do you support AI operations safely?

Yes. Automation flows use controlled command execution, idempotency patterns, and audit trails.

Do you support vector search?

Yes. ConstructOS supports semantic vector search combined with graph context traversal.

Which MCP integrations are highlighted?

Jira MCP and GitHub MCP are highlighted integrations, and ConstructOS also supports additional MCP integrations for broader workflows.

Is Codex optional?

No. Codex is a required runtime dependency for core automation workflows.

Is there a hosted cloud app?

No. ConstructOS is self-hosted only and deployed through Docker Compose in your own environment.

Is there a free beta period?

Yes. Public beta is free for all teams until March 31, 2026, with no automatic charges.

What happens after beta ends?

After March 31, 2026, you can select a paid self-hosted plan to keep production usage active.

How quickly can a team onboard?

Most teams can set up their first production workflow in under one day with starter templates.

Scale delivery without losing context.

Use ConstructOS as your execution layer for reliable output, clearer ownership, and safer automation.