Product map

Three flagships. One Control Plane.

Radio, Deck and Harbor divide the software lifecycle into clear responsibilities. Shared platform capabilities carry identity, policy, context, compute and billing underneath.

User-facing products

Choose the surface for the work at hand.

Every flagship works with the same Account, Workspaces and Projects, while remaining deliberately focused.

Conversations and collaboration

Radio

Plan, research and coordinate work with agents across Account, Workspace and Project context.

  • Durable agent conversations
  • Model, mode and context controls
  • Memory and agent configuration
  • Human approval for consequential actions

Browser development

Deck

Work with projects, source code, Git and durable Agent Consoles inside a focused browser workspace.

  • Source Explorer and editor
  • Git status, history and review
  • Agent Chats, Consoles and Boards
  • Memory and Server sidebars

Infrastructure and operations

Harbor

Manage Servers, workloads, placement, services, domains and deployments from one operational surface.

  • Workspace and environment placement
  • Cloud and self-hosted Servers
  • Capacity and workload visibility
  • Services, domains and deployment lifecycle

Shared platform

Capabilities behind every surface.

These are platform services and execution components—not extra dashboards users must learn before they can begin.

Kami and the Agent Platform

Persistent agent identity, versioned configuration, context, memory, governed tools, approvals and durable runs.

Implemented

Kodemare Atlas

Stable platform model identities, provider routing, plan access, token limits, pricing and Auto Router policies.

Implemented

Kodemare Node

Connects eligible hosts to the Execution Plane and supervises isolated filesystem, Git, runtime and service work.

In progress

Kodemare Cloud

Managed capacity for included Workspace Servers and additional credit-paid Servers, scheduled behind user-facing abstractions.

In progress

Kodemare Pass

Free, Pro and Max plan entitlements, included Workspace Server capacity and recurring credits. Paid checkout is not connected yet.

Catalogue implemented

Kodemare Credits

One usage balance for metered AI and Cloud Server time. Ledger and charging are live; customer top-up settlement is not.

In progress

How it stays coherent

Specialised products. Shared guarantees.

Shared identity and desired state

The Control Plane owns Accounts, Workspaces, Projects, permissions, billing and scheduling for every product.

Execution stays isolated

Source operations and workloads run through governed Execution Plane components, not inside public product frontends.

Agents move with context

Agents can work across surfaces without receiving broader permissions or crossing Workspace and Project boundaries.