APACHE-2.0 · SELF-HOSTABLE · NO SALES CALL

The open-source
agent foundry.

Agents plan, build, test, and review your code. Each run is a sandbox you can watch, on a platform you can read. Your gates decide what ships.

Start nowRead the code

—

  MOGPLEX SYSTEMS

  INTENT → REVIEWED → RUNNING CODE

  NO SEAT FEES. NO SALES CALL.

Checks passed
3 files changed +142 −18
PLANNER

Analyzed codebase and dependencies

IMPLEMENT

Create rate limiter middleware and tests

Running
REVIEW

Security review

Queued
REVIEW

Code quality review

Queued
DEPLOY

Staging deployment

Queued
3 files changed

middleware/rate_limit.py+78−2

tests/test_rate_limit.py+45−0

app/api/routes.py+19−16

$mogplex run 4821

10:24:31•Planner agent completed in 1.2s

10:24:32•Implement agent started

  OPEN AND INSPECTABLE

Apache-2.0 source
Bring your own keys
Per-run sandboxes
Itemized run costs

  ORCHESTRATOR

Command every project
from one control surface.

The orchestrator is one control surface across all of your projects. Say what you want. It routes the work, spawns the agents, and reports back with PRs.

How the orchestrator works

MULTI-PROJECT

Every repo answers to the same control surface.

Ask for a change that spans three services. The orchestrator routes work to each project, tracks every run, and answers with links to the PRs.

PARALLEL WORKTREES

Agents work side by side, not in line.

Each agent runs in its own worktree. Ten tasks fan out at once and never collide. The work merges behind your gates.

SPEC-BASED BUILDS

Point it at a spec. Set a budget.

Want a full system — an EHR, say? Write the spec, set a $25,000 cap, and let it run. You review the PRs while the cap holds the spend.

01 / SPECWrite what you wantThe orchestrator plans the pipelines
02 / FAN OUTAgents in parallelOne worktree per agent
03 / BUDGETA hard spend capRuns stop at your limit

  BUILD AND MAINTAIN

Shipping is half the job.

Software rots the day it ships. Dependencies age, CI breaks, docs drift, and coverage decays. Mogplex runs pipelines against both halves of the job.

All 8 starter pipelines

BUILD

PRs that ship safely to production, with guardrails you set.

Label an issue. A draft PR comes back with the plan, the diff, and the test run. Ask in Slack, and the PR link lands in the same thread.

MAINTAIN

Wake up to fixes, not a red wall.

A run can test dependency bumps each night, diagnose a failed CI job, or open a docs PR when your API changes. You wire each pipeline once.

  YOUR GATES HOLD

Autonomy is a dial.
You set it per pipeline.

Every run ends at your branch protections, required checks, and required reviews. Mogplex cannot bypass them. The code that enforces your gates is open, so read it before you trust it.

Follow one run
FRESH PER RUN

PER-RUN ISOLATION

Every run gets a fresh microVM.

It holds a clone of your repo. Runs share nothing, and every run starts clean.

01 / BOOTFresh sandboxOne run only
02 / EXECUTIONScoped workspaceRepo clone and tools
03 / STOPSandbox endsOutput through your gates
YOUR CHOICE

BYOK / KEY ROUTING

Use hosted models or your own keys.

Hosted model access uses your Mogplex balance, at published rates. Or route each call through your own Anthropic, OpenAI, OpenRouter, or AI Gateway key. Your vault stores it.

VAULT://PLATFORM/PRODUCTION

AnthropicCONNECTED

OpenAICONNECTED

OpenRouterAVAILABLE

EVERY CALL, EVERY CENT

Trace every decision down to the dollar.

Open any run call-by-call: model calls, tool calls, diffs, approvals, tokens, and cost. Approve the next call, redirect the plan, or stop the run.

LIVE REPLAYCOST ATTRIBUTIONRUN CONTROLS
TRACE / RUN 4821COMPLETE

planner

implement

security

quality

deploy

TOKENS84.2k

COST$2.18

TOOLS37

RUN POLICIES

Your gates hold at every step.

Network, filesystem, secret, and runtime policies apply to each run. Your repository rules still decide what can ship.

Network egressALLOWLIST

FilesystemWORKSPACE ONLY

SecretsSCOPED

Max runtime30 MIN

MCPAPI+

MCP CONNECTIONS

Your tools ride along.

Connect MCP servers and REST APIs to a pipeline: Linear, Notion, Sentry, Supabase, Zapier, Browserbase, and your own.

NO SEAT FEES

ROLES / BILLING

Four roles. One pooled balance.

Owner, admin, developer, viewer. Team usage stays in one prepaid balance, with the cost for each run and member.

OWNERADMINDEVELOPERVIEWER

  HARNESS LAYER

Not locked to our agent.
Not to our models.

Mogplex does not lock you to one agent. Pick the native Mogplex agent, Claude Code, or Codex for each pipeline. Every harness runs in the same sandboxes, behind the same gates, on the same meter.

MOGPLEX.YAMLHARNESS READY
run:
  harness: mogplex
  model: claude-opus-5
  credentials: mogplex-hosted
  sandbox: per-run
  telemetry: full

HARNESS READY

Mogplex Native

The house agent, built into the platform. No CLI to install and no keys to bring — a pipeline runs on hosted models the moment you wire it.

  • Zero setup — no CLI, no keys
  • Hosted models on your balance
  • Tuned for Mogplex pipelines

  READ IT FIRST

Read it before you run it.

Code that authenticates against your repos must be readable before you run it. The platform is Apache-2.0 on GitHub. Read it, file issues, and send patches.

Need the system inside your own network? Self-host it — your air-gapped deployment starts with a git clone, free forever. Want dedicated capacity or custom terms on top? Email enterprise@mogplex.com and talk to the people who build it.

Read the codeSelf-hosting docs

START HERE

NO SALES CALL

Wire your first pipeline tonight.

PRICENo monthly fee on PAYG

METERPublished rates only

PLATFORMgithub.com/mogplex/mogplex

DOCSdocs.mogplex.com/quickstart