OpenLoam A Rails foundation for AI-built business apps

Multi-tenancy, roles and permissions, audit trails, and an event bus — already built in, so you skip months of plumbing and build the actual business. AI agents can extend it safely too — every write they propose waits for human approval before it takes effect.

Get started

How OpenLoam works

View on GitHub

🏢

Multi-tenancy, structurally

Tenant isolation baked into every query, job, and event via OpenLoam::TenantRecord. A missing tenant context raises — it never silently widens a query.

🔐

Authorization, not just permissions

Roles, policies, and field-level write access declared once. Plus wildcard feature-string permissions (equipment.*), deny-by-default.

📡

A real event backbone

Ephemeral and durable subscribers on one domain event bus — at-least-once delivery, dead-letter, redelivery sweep for the durable tier.

🚧

Guardrails, not guidelines

Structural tests fail the build on a missing tenant scope, a stray .unscoped, or an oversized AGENTS.md — before a human has to catch it in review.

🤖

Built for coding agents

AGENTS.md is the contract; open_loam:entity is the interface; an MCP server exposes tenant-scoped, policy-aware reads and human-approved writes.

📊

Benchmarked, caveats published

In one internal run of the golden-tasks benchmark, tenant isolation held 10/10 on OpenLoam apps versus 1/10 on vanilla Rails — same prompts, same model, protocol pre-registered. A single run, not yet repeated or independently reproduced, and the page says so.