Ranse

The Cloudflare-native shared inbox for support teams.

Ranse turns support email into a real-time, multi-agent support workspace built on Cloudflare Workers, Durable Objects, Email Service, R2, D1, Queues, and AI Gateway.

---

Why Ranse

• Email-native shared inbox with ticketing, assignment, and internal notes.
• Multi-agent assist — triage, summarization, knowledge retrieval, reply drafting, escalation, SLA.
• Human approval gates for every outbound reply, with edit-before-send.
• Multi-provider LLM — Workers AI out of the box; drop-in Anthropic, OpenAI, Google, Grok, OpenRouter, Cerebras via AI Gateway.
• Historical evals — resolved conversations become anonymized replay cases; ranse eval catches prompt/procedure regressions before they ship.
• Forkable procedure library — install vetted support workflows with evals, provenance checksums, and MCP reference contracts, then customize them in your repo.
• Insights loop — score conversations, surface evidence-backed unresolved intents, draft reviewable KB suggestions with lineage, and detect source-specific drift from successful replies.
• Public web channels — embed chat widgets or hosted support forms that create normal tickets in the same inbox.
• One-click deploy to your own Cloudflare account — customer-owned from day one.
• Open source (Apache-2.0).

Quick start

1. Click Deploy to Cloudflare above. Cloudflare forks the repo into your GitHub, provisions a Worker + D1 + R2 + KV + Queues + Durable Objects, and kicks off a build.
2. During the deploy-button flow, fill in the prompted variables:
   • APP_URL — your Worker URL (fill in after first deploy if unknown)
   • ADMIN_EMAIL — your admin account email
   • SUPPORT_DOMAIN — the domain you'll use for support email (e.g. support.acme.com)
3. Open your Worker URL — Ranse redirects you to /setup.
4. Enter the generated ADMIN_SETUP_TOKEN (see your Worker's secrets) to create the first admin + workspace.
5. Add your support mailbox in step 2 of the wizard.
6. In the Cloudflare dashboard → Email → Email Routing, route support@yourdomain.com to the Ranse Worker.
7. Send a test email — it lands in your inbox as a ticket with a triage summary and a suggested reply waiting for approval.

Architecture, in one picture

Inbound email
   │
   ▼
 Worker  email()                ┌──────────────────────────────────────────┐
   │  parseInbound (postal-mime)│ WorkspaceSupervisorAgent (Durable Object)│
   │  resolveMailbox (D1)       │  ├─ ingestEmail()                        │
   │  putRaw → R2               │  │  └─ schedule(triageAndDraft)          │
   └──▶ Supervisor.ingestEmail──┤  ├─ triage → specialists/triage          │
                                │  ├─ search → specialists/knowledge       │
                                │  ├─ draft → specialists/draft            │
                                │  └─ createApproval → D1                  │
                                └──────────────────────────────────────────┘
                                              │
                                              ▼
                                  Operator console (React)
                                  Approve → Supervisor.approveAndSend
                                                 │
                                                 ▼
                                             env.EMAIL.send

All LLM calls go through a single dispatcher (src/lib/llm/) that uses the OpenAI SDK and the Cloudflare AI Gateway /compat endpoint, so switching providers is a one-line config change per agent action.

Docs

• Installation — detailed setup, troubleshooting, DNS.
• Architecture — agents, storage model, event flow.
• Operations — ticket lifecycle, approvals, escalations.
• Security — auth, roles, reply signing, auto-reply handling.
• Roadmap — the planned path from copilot to autonomous agent.
• FAQ

Local development

bun install
bun run setup                 # writes .dev.vars with generated secrets
bun run db:migrate:local
bun run dev

Then open http://localhost:5173 (or http://localhost:8787 for the Worker directly).

Note: Local email testing requires a Cloudflare Email Routing setup on a real domain. For local work you can POST /setup/bootstrap + seed test data manually, or write integration tests that call Supervisor.ingestEmail with a mock payload.

Roadmap

Ranse is heading from "AI-assisted shared inbox" to a full autonomous customer-service agent — but not as an OSS clone of Fin or Decagon. The goal is the agent those products structurally cannot become: sovereign by construction, per-step model choice, procedures-as-code, MCP-native actions, eval-first against your own ticket history, and a forkable procedure library.

The shape, in short: retrieval → workspace management → agentic retrieval → autonomous resolution → procedures → MCP actions → evals → procedure library → insights → multi-channel. Phase 0 (bootstrap, inbound email, supervisor DO, draft + approval), Phase 1 (retrieval foundations), Phase 1.5 (workspace management & tenant isolation), Phase 2 (agentic multi-hop retrieval), Phase 3 (autonomous resolution), Phase 4 (procedures as code), Phase 5 (MCP-native actions), Phase 6 (historical evals), Phase 7 (procedure library), Phase 8 (insights & auto-improving KB), and Phase 9 web channels are shipped.

Full pipeline, principles, and how to contribute to a phase: docs/08-roadmap.md. It's directional, not committed — if you want to work on something further down the list, open a discussion and we'll happily reorder.

License

Apache-2.0 — see LICENSE.

---

Built on Cloudflare Workers + Agents SDK + Hono + React 19. Inspired by vibesdk's deploy pattern.