Back to Monster Orange

Open source · MIT

Den

Your whole stack, and every agent working on it, in one local place.

Get started

npx @monster-orange/den create <name>
Den's Graph page: a workspace's services grouped by application, all healthy, with the status chip and the left rail.

Most days start with getting things running.

  1. Many repos, each with its own way to start, and the steps live in someone's head.
  2. No single place to see what's up, what's down, and why.
  3. Agents that act outside the rules people follow: other credentials, no audit trail, no boundary.

What Den does

Everything up, in order.

Each repo gets a manifest. Den starts them in dependency order, puts them behind one local HTTPS edge, and draws the whole thing as a graph.

The Graph page with demo-web selected: its details panel shows its health, its URL on the edge and that it depends on demo-api.

One place to see it.

Health, logs, runs and routes in one web shell and one CLI. When something is down, Den says why and offers the fix.

The status drawer: nothing needs attention, and every service in the workspace, by application, with its latency.

Switch workspaces without losing your place.

Focus on one workspace, check the status of the rest, and switch between them. Switching never stops what you're using.

The Workspaces page: a workspace's repos with their health, mode and Start, Stop, Restart and Logs actions.

Agents in Den, from any vendor.

Start and resume agent sessions in the browser or the terminal, with personas and roles. Claude, Codex, Gemini and more run through one runtime registry, under the same guards, audit trail and workspace boundary as a person.

The Agents tab: a workspace's sessions on the left, and one open in a terminal pane on the right, running a service's tests and then the service.

Built and used daily at Monster Orange.

Den runs Monster Orange's own products every day, through Monster Orange's own distribution of it.

  • Narai
  • Wayfinder
  • Arbor

Why Den?

More than 50 years of building software, distilled into one way of working with agents.

Ward Vuillemot wrote his first programs as a kid, in assembly language. Since then he's been the CTO who designed how whole engineering teams build, test and ship, and, in the last few years, a founding engineer and CTO at companies built around AI agents.

Den is what he learned, made usable. It's how Monster Orange runs every day: our own products (Narai, Wayfinder and Arbor), our client work and Den itself are all built inside it. Our own copy has a name: Lair.

We're sharing it because the best work now happens side by side: seasoned engineers next to people who've never opened a terminal, each with agents that play by the same rules they do. Den is where that happens.

How it works

The engine comes from npm.
One package, @monster-orange/den, versioned and MIT-licensed.
Your distribution sits in your repo.
A small repo of your own holds your product name, repos, hosts, secrets and theme. Den itself knows nothing about your organisation.
Local first.
No account, no telemetry. Nothing phones home.
Your repos stay untouched.
Manifests can live in your distribution instead of the target repo, so Den can manage a repo without changing anything in it.

Den Hub · premium, for teams Coming soon

Den Hub

One place where your team's specs, designs, decisions and agents meet, wherever the work actually lives.

Concept preview of Den Hub's Graph: a PRD section at the centre, linked to the issues, pull requests, decisions and designs that implement or mention it.
Concept preview

A map of your work, not another tracker.

Hub links your issues, PRDs, ADRs, HLDs, LLDs and designs where they already live (GitHub, Linear, your repos, your buckets), and you can ask questions across all of it.

Concept preview of a Den Hub artifact: a screen design with a comment pin, its versions, and a thread an agent answered with a new version.
Concept preview

Artifacts any agent can make and anyone can review.

Like AI artifacts, but not tied to one vendor or one account. Publish from Claude, Codex or Gemini, then comment, compare versions, and send a thread back to an agent.

Concept preview of Den Hub's Design system page: token layers, each brand's overrides, and parity rules checked per brand.
Concept preview

Your design system, kept honest.

Every brand on one core, parity checks on each release, and drift shown per project.

Concept preview of Den Hub inside a member's Den: shared personas in the agent picker, and a thread from Hub waiting for an agent.
Concept preview

Shared agents.

The team's personas, roles and permission intent, on every member's Den.

Join the Den Hub waitlist

We'll send a link to confirm your address. Once you confirm, we'll write once more, when Hub is ready for teams to try.

Den and Den Hub

DenDen Hub
PriceFree, MITPremium, for teams
RunsOn your machineHosted by Monster Orange
AccountNoneGitHub sign-in
ContentsWorkspaces, services, agents, MCPShared map, artifacts, design system, personas, team threads

Hub is optional. Den never needs it.

Questions

Is Den really free?

Yes. Den is MIT-licensed and on npm. There's no paid tier of Den itself; Den Hub is a separate product for teams.

Does Den need Hub, or an account?

No. Den runs entirely on your machine with no account. Hub is optional and adds team features on top.

Which agents work with it?

Claude, Codex, Gemini and more, through one runtime registry. Each runs under the same guards, audit trail and workspace boundary as a person.

Is my data sent anywhere?

Not by Den. It has no telemetry and nothing phones home. Your agents talk to their own vendors, as they would without Den.

Can I run Hub myself?

Not yet. Tell us if you need it.

Start your Den.

npx @monster-orange/den create <name>