Five packaged products, powered by six domain hubs. A sovereign cloud workspace, governed memory, an operator dashboard, and a voice + chat assistant — designed for environments where every decision needs a name attached.
The platform breakdown — each product ships independently, deploys per-tenant, audits to the same trail.
Builder · Buyer
newCode in your browser. On your infrastructure. Governed by construction.
Builder · Operator
Six domain-isolated engines that ship code, decisions, content.
Builder · Buyer
Governed memory. Append-only audit. Semantic recall over the why.
Operator · Buyer
Operator dashboard for your tenant fleet.
Builder · Operator
Voice + chat assistant for the workspace. Multi-provider. Audited.
Pillar 01
Per-domain engines that ship code, content, and decisions.
A hub is a domain-shaped engine that ships outcomes — code commits, training tracks, decision records, sales artifacts. Each hub speaks the same contract (intent → governed action → memory write → audit event) so cross-hub work composes without rewiring. New hubs ship without touching old hubs because the contract is the integration point.
Pillar 02
Governed memory with append-only audit and semantic recall.
BrainDB is the organizational memory layer. Every write carries rationale, owner, and dependencies — the three governance fields that make memory queryable, attributable, and reviewable. Append-only audit namespaces are immutable by construction. Semantic search via pgvector finds the relevant prior decision, not the most recent one.
Pillar 03
Operator dashboard for the tenant fleet.
Control Tower is where operators provision tenants, watch fleet health, refresh configurations, and respond to drift. Every tenant runs in its own isolated stack — Control Tower is the only place that sees them all. The tenant wizard provisions a complete environment in minutes; the refresh primitive surgically applies changes without operator-edited compose drift.
Pillar 04
Every decision recorded, queryable, and per-tenant isolated.
Audit is not a logging library. It is the contract every hub and every operator action satisfies: actor, action, tenant, timestamp, and a payload shaped to the action. Designed for compliance review — not real-time analytics. The audit trail is queryable by actor, by action, by tenant, by time range. Per-tenant isolation means tenant A cannot see tenant B's audit even with a misconfigured query.
Six capabilities on one governed platform. Each one ships outcomes with an audit trail attached.
Every decision, context thread, and institutional insight is written to BrainDB with rationale and owner. Nothing is lost when people leave.
The Coding Hub ships commits, not suggestions. Code generation is governed by the same audit contract as every other hub action.
Contracts, briefs, and reports generated with full context from BrainDB. Documents inherit the governance layer — no orphaned artefacts.
Every decision has an actor, a rationale, and a timestamp. The audit trail is queryable so you can answer 'who decided this, and why?' in seconds.
LUNA, the voice and chat assistant, is the conversational surface for the platform. Sessions are persisted; context carries forward.
Hubs compose into workflows. Academy trains, Legal reviews, Coding ships. Each step is receipted so the autonomous loop has a verifiable paper trail.
The dimension where we differ
We do not compete with Cursor or Copilot on autocomplete speed. We compete on what they do not ship at all — the governance layer underneath autonomous agents.
Comparison reflects public capabilities as of 2026-06. Each tool ships frequently; verify current state at the vendor's site. We compare on the governance axis only — code-suggestion quality and autocomplete latency are not in scope.
Two paths in. Pick the one that fits.