Mendloop
Request access

Run all of it on your servers.

Private beta Mendloop’s core is Apache-2.0: the same code that runs our cloud. The repository opens to everyone at the public release; beta teams get access now. You’ll need Postgres, Redis and a machine with Docker. Nothing else.

Get notified at launch Self-host guide 
# needs Docker, git and make
$ git clone https://github.com/mendloop/mendloop
$ cd mendloop
$ make setup
  .env written with fresh keys
  Postgres and Redis are up
  migrations applied
$ docker compose up -d
$ npx mendloop init   # in your app’s repo

From a clean machine to a first test error. mendloop serve runs every process in one for small installs.

Core
Apache-2.0
Enterprise
ee/, commercial licence
Forks
None: one codebase

Open core, one codebase

Everything that finds, fixes and remembers is Apache-2.0. A few features that large organizations need live in ee/ under a commercial licence and switch on with a licence key. Cloud and self-hosted run the same code; one setting, MENDLOOP_EDITION, turns on billing and sign-up for our cloud.

What’s in it

Core, Apache-2.0

  • Ingest, issues, dedupeSentry, SDKs
  • Root-cause investigatorsAny model
  • Approvals and remindersChat, phone
  • Fix sandbox and pull requestsDocker or CI
  • Workflows and test modeYAML, versioned
  • The Brainpgvector
  • Privacy layerHash, scrub
  • CLI and MCP serverTyper, MCP

ee/, with a licence key

  • Single sign-onOIDC, SAML
  • SCIM provisioningEnterprise
  • Audit log exportBusiness
  • Advanced approval policiesEnterprise

The ee/ licence key comes with Enterprise. See pricing

Self-host it

The repository opens at launch; these are the steps you’ll run. Postgres 16 with pgvector and Redis 7 are the only services Mendloop needs. Object storage is optional; reports and maps go to local disk by default.

$ git clone https://github.com/mendloop/mendloop && cd mendloop   # beta access; public at release
$ make setup          # .env with fresh keys, Postgres and Redis, migrations
$ docker compose up -d
$ make doctor         # checks configuration and connectivity

Running Kubernetes? A Helm chart scales workers on queue depth with KEDA.

Configuration

Only these settings. Setup writes the required ones.

Environment variables
VariableRequiredPurpose
DATABASE_URLYesPostgres
REDIS_URLYesRedis
MENDLOOP_BASE_URLYesThe public address of your install
MENDLOOP_SECRET_KEYYes, generatedSessions and signing
MENDLOOP_MASTER_KEYYes, generatedWraps each organization’s key; or use a KMS
STORAGE_URLNoDefaults to file:///data
SANDBOX_DRIVERNoci-only by default, or docker, gvisor
MENDLOOP_LICENSE_KEYNoUnlocks ee/
LLM_*_API_KEYNoModel keys for the whole install; organizations can add their own

How big a machine

One team

2 vCPU, 4 GB

  • Up to about 1 million events a month
  • mendloop serve: api, ingest and worker in one process
  • Postgres and Redis on the same host, 40 GB disk
  • Fixes verified by your CI

A department

8 vCPU, 16 GB

  • Up to about 10 million events a month
  • api, ingest and worker as separate containers
  • Managed Postgres and Redis
  • Docker sandbox runner for local verification

A company

Kubernetes

  • Helm chart; workers scale on queue depth with KEDA
  • gVisor sandbox pool
  • Ingest scales with event volume, workers with queue depth
  • Talk to us about an Enterprise licence

Bring your own model

Each step asks for a tier, fast, balanced or strongest, never a model name. You map tiers to the providers you trust, with fallbacks and budgets.

We recommend Claude for the strongest tier. Small local models without tool calling still work: Mendloop asks them which evidence they need, fetches it, and has them answer in JSON.

Model providers in Settings: OpenAI and Anthropic connected, Ollama running locally with three models loaded, and Gemini, an OpenAI-compatible endpoint and cloud providers ready to connect, each with its data policy.

Start in your app

Run npx mendloop init in your app’s repository. It finds your framework, adds the SDK and source-map upload, writes the config and sends a test error. Or keep Sentry and change only the DSN.

Prefer the CLI: npx mendloop init detected Next.js 15, added the SDK and source-map upload, wrote the config and sent test error ML-1.
A Sentry connection: connected with read access, 18,402 events in the last 24 hours from 3 projects, webhook p95 of 1.2 seconds.

Build it with us

Issues, ideas and pull requests are welcome. Integrations are plugins with a template, so a new tool is one package.

GitHubSource, issues and releasesAt public release
DiscussionsQuestions and ideasAt public release
ContributingHow to set up and send a changeAt public release
Plugin templateWrite an integration with its own verify stepAt public release
SecurityReport a vulnerability privately
LicenceApache-2.0, in fullAt public release
A sixteenth-century Korean stoneware tea bowl with combed white rings, its cracks and chipped rim repaired with gold lacquer.

Mends you can see

Kintsugi leaves the repair in plain sight. So does an open codebase.

Read every prompt, every investigator and every rule that decides what Mendloop may write. If you disagree with one, change it and send it back.

Tea bowl, Korea, Joseon dynasty, 16th century, repaired with gold lacquer. Ethnological Museum, Berlin. Photograph by Daderot, CC0.