Skip to content

The development platform for human-agent teams,

from a team of one to a whole company

People and agents share one workspace: the same Spaces, the same Context, and Miriarch, the agent that works across all of it.

Set up a workspace for my teamDownload
01Workspace & Spaces

A workspace, and the Spaces inside it

Workspace
Your team's home in Miriarch. It holds the people, the agents, the shared Context and every Space. A workspace can be just you or, once team workspaces arrive, your whole company.
Spaces
Apps inside the workspace, each built for one kind of work: product, production, a lab for coding agents, and conversation with team workspaces. Each one has its own views and workflows, and they all read from the same Context.
Workspaceoverland
Team
+6MiriarchMiriarch and the coding agents Claude Code, Codex, Cursor
Spaces
CitadelGuardianHive
Context
Shared by everyone and every SpaceOVL-412 · INC-37 · #eta-engine · Kessler Freight
Miriarch on the desktopOverland, a sample workspace
Miriarch on the desktop: Citadel's issues in the sample workspace Overland, some assigned to people and some to Claude Code and Codex.
02Context

One Context across the whole platform. A question asked in one Space is answered with what every Space knows.

Issues, specs, incidents, conversations and decisions all land in the same shared Context. People and agents read from it.

  • Reference any object, in any Space, from anywhere
  • Bring in people and agents with the same history in hand
Context · 3 SpacesOVL-412CitadelINC-37Guardian#eta-engineHub
MO asks: What's holding up the Kessler Freight rollout?
Miriarch answers:
  • node_getKessler Freight rollout · project
  • node_getINC-37 · resolved
  • node_find#eta-engine · 1 decision
  • node_getOVL-412 · needs approval

One open fix. OVL-412 drops stops when carrier pings arrive out of order, which caused last week's INC-37. The team agreed in #eta-engine to hold the rollout until it ships. Claude Code has a fix with tests passing; it's waiting on your approval to open the PR.

03The Miriarch agent

Miriarch works across every Space

Ask, draft, or run an action from anywhere. Miriarch reads the shared Context, directs coding agents like Claude Code, Codex and Cursor, and comes back to you before anything leaves the building.

  • IdleWatching, ready when you are
  • ThinkingReading the Context
  • WorkingRunning a task or an agent
  • Needs youAn approval is waiting
  • DoneFinished, with a summary
  • BlockedStopped and told you why

You set what needs a human

Every action carries a risk class.

Read
Search issues, read logs
Runs automatically
Write
Comment, update an issue
Runs automatically
External
Open a PR, send an email
Asks first
Destructive
Delete, roll back production
Always asks

Asks before it acts

Approve, edit or deny without leaving what you're doing.

ExternalOpen pull requeston overland/platform
Branch
cc/ovl-412-out-of-order-pings
Changes
3 files +48 −12
ApproveEdit firstDeny
04Agents & integrations

Your agents, your tools, one workspace

Connect the coding agents your team already pays for, on their own subscriptions. Integrations bring your other services into the platform, so every Space and Miriarch can work with them.

External agents

Each agent runs on its own account and plan. Miriarch assigns them work and reviews what comes back.

  • Claude CodeYour subscription
  • CodexYour subscription
  • CursorYour subscription
  • OpenCodeYour subscription
  • PiYour subscription
  • Gemini CLIYour subscription
  • Copilot CLIYour subscription
  • Qwen CodeYour subscription

Integrations

Connected services feed the shared Context and give Miriarch new actions, each with its own risk class.

  • Linear
  • Notion
  • Sentry
  • GitHub
  • Atlassian
  • Vercel
  • Datadog
  • Grafana Cloud
  • Prometheus
  • Loki

Miriarch read 3 Sentry errors and opened a Linear issue in Citadel

05Spaces

As many Spaces as your work needs

Each Space is shaped to one kind of work, with its own views, workflow and fields, and every one reads the same Context. Arrange them on the rail and hide the ones you don't use.

  • 01

    Citadel

    Product

    Issues, specs and pull requests, with coding agents assigned alongside people.

    • Issues
    • Planner
    • Docs
  • 02

    Guardian

    Production

    Vitals, deploys and incidents for every service you run.

    • Vitals
    • Deploys
    • Incidents
  • 03

    Hive

    Agent lab

    Run one prompt through several coding agents side by side and keep the best, or build hands-on with agents and terminals. On the desktop.

    • Lab
    • Vibe
    • Codebase
  • 04

    Hub

    Conversation

    Channels and threads where people and agents talk, and decisions are kept.Coming with team workspaces

    • Channels
    • Threads
    • Decisions
Build your own · the space builder is comingWe need a space for the carrier partnerships team. Onboarding new carriers, tracking their API integration, and SLAs once they're live.
Miriarch Drafted Carrier Deskfor review
  • Pipeline
  • Integrations
  • SLAs
  • 1 workflow
06Local & cloud

Run it where your team works

The same platform runs on your own machine or in the cloud. Spaces, Context and Miriarch work the same way in both.

Where it runs

On your machine

Runs next to your code and your terminal. Your workspace and agent sessions stay on your hardware.

Overland · running on this computer
Free, as many local workspaces as you like

The same in both

  • Spaces
  • Context
  • Miriarch

From a team of one to a whole company

DownloadSee pricing