Public product roadmap

Governed memory first. Controlled action follows.

Frege is shipping the governed organizational-memory layer first, then adding policy-controlled integrations and execution without weakening provenance or customer choice.

Available
Supported in the current product.
Beta
Usable now; interfaces may change.
Planned
Direction, not a delivery-date commitment.
A stone facade centered on a sundial and arched doorway, rendered with numeric glyphs.
Status over timeNumeric-character study / source 03

Use today

Available now

The governed memory and context foundation available to Frege customers today. Beta capabilities are usable, but their interfaces may still change.

Available

Versioned organizational memory

Store organizational knowledge as governed pages and sources with revision history instead of scattering it across agent-local files.

Available

Scoped, cited context

Build task-specific context from sources the caller is allowed to receive, with citations back to the returned material.

Available

Reviewable memory updates

Let agents propose durable knowledge changes while keeping canonical memory under human review.

Available

Session and event ledger

Keep durable task context, context builds, tool activity, and notes connected to the work that produced them.

Available

MCP and CLI access

Connect Codex, Claude Code, and other MCP clients through the Frege CLI and a scoped API key.

Beta

Model routing

Send governed context to an organization-configured model provider and record invocation telemetry.

Beta

Hosted agent runs

Queue and inspect hosted, single-step agent runs while the policy-controlled multi-step runtime is developed.

Policy first

Building next

The identity, policy, and provenance controls Frege needs before agents can safely receive broader access and take more consequential actions.

Planned

Agent and service principals

Represent humans, agents, and services as explicit identities with scoped, delegable credentials.

Planned

Versioned authorization policies

Evaluate principal, action, and resource together under default-deny policies that can be reviewed and versioned.

Planned

Authorization receipts

Return an attributable record of why access was allowed or denied without revealing restricted source content.

Planned

Governed connector framework

Sync external sources with source identity, revisions, access mapping, deletion handling, and connector health. GitHub and Google Drive are the first planned connectors.

Planned

Unified provenance ledger

Connect reads, denials, context builds, proposals, approvals, and model activity in one attributable event history.

Controlled execution

Later

Broader workflow and runtime capabilities built on the same policy checks, review boundaries, and portable organizational record.

Planned

Durable tasks and workflows

Track assigned principals, steps, inputs, outputs, and idempotent state transitions without overloading agent sessions.

Planned

Approval gates

Pause consequential work, collect an authorized decision, and resume from recorded state.

Planned

First-party Frege Agent

Run bounded, multi-step tool loops under the same capability, approval, step, and spend controls as every other agent.

Planned

Portable organizational record

Export and import organizational knowledge with source, revision, and provenance context so customer memory is not trapped in one runtime.

Planned

Stable control-plane contracts

Add versioned API contracts for principals, policies, receipts, connectors, tasks, and approvals while preserving current v1 clients.