Monster Orange Get started

Den · How it fits

How Den and Den Hub fit together

Den runs your stack on a machine you choose.

Den Hub is where your team and its agents share the work. It runs on the web, managed by Monster Orange.

Den works alone. Hub adds the team.

  • Den, available now
  • Den Hub (Teams: closed beta. Enterprise: coming)

01One Den

One Den

Your repos, your tests and your agents, in one place.

api npm run dev · :3000? web EADDRINUSE :3000 db did anyone start it? tests tab 4, from memory agent can't see what runs api npm run dev · :3000? web EADDRINUSE :3000 db did anyone start it? tests tab 4, from memory agent can't see what runs
[ fig. 00 — without den ] Without Den, the stack is a handful of terminals and whatever you remember.
Den, on your machine Agentsany vendor, any persona P Planner D Developer R Reviewer MCP Den Local HTTPS edge, real hostnames https://app.example.dev Your repos, started in order 1 · apiup 2 · webup 3 · docsup Tests in the loop Smoke Browser API Journeys Security Performance Den, on your machine Agentsany vendor, any persona P Planner D Developer R Reviewer MCP Den Local HTTPS edge, real hostnames https://app.example.dev Your repos, started in order 1 · apiup 2 · webup 3 · docsup Tests in the loop Smoke Browser API Journeys Security Performance
[ fig. 01 — one den ] One Den holds the repos, the tests and the agents.
  • Repos start in dependency order, behind a local HTTPS edge with real hostnames.
  • Tests run in a loop: smoke, browser, API, journeys, security, performance.
  • Agents work over MCP under Den's guards, on one audit trail.

02With Hub Coming

Den with Den Hub

Each teammate keeps their own Den. Hub sits in the middle and keeps everyone, and every agent, on the same plan.

  • Den, available now
  • Den Hub (Teams: closed beta. Enterprise: coming)
Feedback flowsback into Hub Den Hub coordinates every memberand their agents A AnaDesignerDen B BenDeveloperDen M MiaPlannerDen Ideas Rough notes Designs and docsPRDs, ADRs, HLD/LLD, UX mocks Approvedready to build GitHub issues Built in Denby people and agents Shippedread from code and releases Feedback flows back into Hub Den Hub coordinates every memberand their agents A AnaDesignerDen B BenDeveloperDen M MiaPlannerDen Ideas Rough notes Designs and docsPRDs, ADRs, HLD/LLD, UX mocks Approvedready to build GitHub issues Built in Denby people and agents Shippedread from code and releases
[ fig. 02 — den with hub ] The loop: ideas to shipped work, with feedback back in Hub.
  • Shared memory links docs, mocks, decisions and comments into one model. Search reads inside it.
  • Design home: your design system and tokens, imported from your repo.
  • Mocks carry versions and pinned comments. A comment reaches the agent that made the artifact. It revises, then replies.
  • Approved designs become GitHub issues. Dens build them. Shipped is read from your code and releases, and feedback returns to Hub.
  • Hub never becomes your issue tracker. Agents work in Hub over MCP. Planned: Slack, Linear and Figma.

03Built in Den

Built inside itself, today

Agents working inside Den and Den Hub build both.

Den, on your machine Managed by Monster Orange Den Projects Den repoproject Den Hub repoproject P PlannerAgent D DesignerAgent R ReviewerAgent D DeveloperAgent work in Den Hubthe team home Den Hub for TeamsClosed beta, by invite Den Hub for EnterpriseComing versions comments Den, on your machine Managed by Monster Orange Den Projects Den repoproject Den Hub repoproject work in P PlannerAgent D DesignerAgent R ReviewerAgent D DeveloperAgent Den Hubthe team home Den Hub for TeamsClosed beta, by invite Den Hub for EnterpriseComing versions comments
[ fig. 03 — built inside den ] Role-holding agents work on both repos inside one Den.
  • Den's repo and Den Hub's repo are projects in a Den.
  • Agents hold roles: planner, developer, designer, reviewer.
  • People work with them through Den and Hub.

Many agents, one Den

Each project in a Den has its own agents, from whichever vendor suits the job. They all work in the same running stack. Den's Agents page lists every agent with its state and project.

  • queued
  • working
  • done
  • message between agents (coming to Den)
  • Claude Code
  • Codex
  • Gemini CLI
  • Grok Build
[ fig. 03b — agents in one den ] An illustration: each square is one agent, grouped by project. The letters are its runtime, the word its role, the colour its state. A line is a message from one working agent to another, coming to Den.

92

Den builds Den. Agents working inside Den and Den Hub build both. So far that's92 Den releases on npm, 0.1.0 to 0.4.81.

04Runs anywhere Today

Runs anywhere

Den runs on any machine you choose: macOS, or Linux on a machine or VM, on your desk or in any cloud. Open it in the browser on a laptop, iPad, iPhone or Windows PC.

One machine, your choice Only a browser needed Denbuilds, tests, ships Build Test Ship Private network Laptopin a browser iPadin a browser iPhonein a browser Windows PCin a browser One machine, your choice Only a browser needed Denbuilds, tests, ships Build Test Ship Private network Laptopin a browser iPadin a browser iPhonein a browser Windows PCin a browser

Runs on

  • macOS
  • Linux

Or in any cloud, for example

  • AWS
  • Azure
  • Google Cloud
  • and more

Needs Node 22.13+ and git. Docker or a compatible engine runs your project's services.

[ fig. 04 — runs anywhere ] Every device is a browser. The work stays on the machine running Den.
  • Anywhere your private network reaches, signed in, never with a password.
  • On a plane, your laptop's Den keeps running offline. Your agents still need their own service.

05Many Dens

Many Dens, one Hub

Monster Orange has its own Den. Each client has theirs. Den Hub is where they meet, with each company kept separate.

Dens: each one isolated Managed by Monster Orange Monster Orange's own Denits own isolated DenA client's Denits own isolated DenA client's Denits own isolated Den Each Den connectsto its own companyin Den Hub Den Hub Companies, each kept separate Monster Orange A client A client Dens: each one isolated Managed by Monster Orange Monster Orange's own Denits own isolated DenA client's Denits own isolated DenA client's Denits own isolated Den Each Den connectsto its own companyin Den Hub Den Hub Companies, each kept separate Monster Orange A client A client
[ fig. 05 — many dens, one hub ] Dens do the work. Hub is where companies meet.
  • Teams: one Hub shared by several companies, each kept separate.
  • Enterprise: a Hub for one company alone.

06Teams

Den Hub for Teams and Enterprise

Den Hub runs on the web, managed by Monster Orange. Your team keeps its own Dens, and they connect to your Hub.

Monster Orange runs it, and keeps it current Yours: each person's Den runs on their own machine ↑ docs, designs ↓ decisions, issues single sign-on connected by you Your Den Hub the team home hub.monsterorange.com Checkout PRD v3 · 2 pins Login design v2 Approve Issue #214 GitHub One-page checkout decision A Den AnaDesigner B Den BenDeveloper M Den MiaPlanner + Enterprise Your identityprovider SAML Your repos documents andsource code Monster Orange runs it,and keeps it current Yours: each person's Denruns on their own machine ↑ docs, designs ↓ decisions, issues Your Den Hub the team home hub.monsterorange.com Checkout PRD v3 · 2 pins Login design v2 Approve Issue #214 GitHub One-page checkout decision A AnaDesigner Den B BenDeveloper Den M MiaPlanner Den + Enterprise Your identity providerSAML · single sign-on Your reposdocuments and source code
[ fig. 06 — teams and enterprise ] Your team keeps its Dens. They connect to your Hub.
Teams and Enterprise, side by side
Den Hub for TeamsDen Hub for Enterprise
RuntimeShared, each company kept separateIsolated, only your company in it
Sign-inGitHub sign-inSAML single sign-on, through your identity provider
Addresshub.monsterorange.comYour own domain, or a subdomain on monsterorange.com
StatusClosed beta, by inviteComing
  • Monster Orange runs it and keeps it current.
  • Your team keeps its own Dens, connected to your Hub.

Want this? Join the waitlist and tell us.

07Your data

Your docs and code stay yours

Your documents and source code stay in your own repos and systems. You connect them to Den Hub.

Yours Managed by Monster Orange Your data sourcesdocuments, source code docs/checkout-prd.md src/checkout.ts Your integrationsyou provide them connectsto Hub Den Hub Checkout PRDv3 · 2 pins Login designv2 Yours Managed by Monster Orange Your data sourcesdocuments, source code docs/checkout-prd.md src/checkout.ts Your integrationsyou provide them connectsto Hub Den Hub Checkout PRDv3 · 2 pins Login designv2

Today

  • GitHub
  • Git

Coming: your own S3-compatible bucket

  • Amazon S3
  • Cloudflare R2
  • Google Cloud Storage
  • MinIO
  • Backblaze B2
  • Wasabi

Coming: export everything in open formats

  • Markdown
  • HTML
  • JSON
  • CSV
  • DTCG tokens
[ fig. 07 — your data ] Your docs and code stay put. Hub connects to them.

You run

  • Den, on macOS or Linux, at your desk or in a cloud
  • Your repos, docs and code
  • Your agents and their vendor accounts
  • Your services and data

Monster Orange runs

  • Den Hub for Teams and Enterprise, on the web
  • Sign-in: GitHub for Teams, SAML single sign-on for Enterprise
  • Hub updates
[ fig. 07b — who runs what ] Den runs where you put it. Den Hub runs on the web, and we run it.
  • You choose what Hub connects to, and you bring the integrations.

Start your Den in five minutes.

Hand this to your agent

Set up Den for me by following https://monsterorange.com/den/agent.md
  1. Your coding agent installs Den and starts it.
  2. It hands you a one-time link. Open it in your browser.
  3. Den's own agent walks you through bringing in your repos. About five minutes in all.

Prefer the terminal?

npx @monster-orange/den@latest create <name>