Skip to main content
Horizons is designed as a reusable platform layer: storage, events, agent execution, approvals, and sandbox runtime. Application teams then build product logic on top of those primitives.

​
OpenRevenue (public)

OpenRevenue is a revenue operations app built on Horizons. What it demonstrates:
  • Context refresh connectors feeding durable business context
  • Agent sessions with streaming progress updates
  • Action proposal and approval workflows
  • Audit-friendly, event-driven orchestration
Repository: Run locally (recommended dev path): 
cd OpenRevenue
./run.sh
Then open:
  • http://localhost:5173
Notable routes/workflows to explore:
  • Growth metrics and sync actions
  • Agent sessions (/agents)
  • Approval workflows and audit behavior

​
Dhakka (private/internal)

Dhakka is a Horizons application for personal operations and communication workflows. What it demonstrates:
  • Gmail/Calendar/iMessage connector integration
  • Permissioned actions (approve before execution)
  • Outbox + event-driven execution model
  • Separate app workspace depending on Horizons crates
Run locally (internal repo): 
cd Dhakka
./run.sh --port 8010 --data-dir .dhakka_dev
Then open:
  • http://localhost:8010/dhakka
Optional connector toggles (examples): 
export DHAKKA_IMESSAGE_SYNC=1
export DHAKKA_GMAIL_SYNC=1
export DHAKKA_GCAL_SYNC=1

​
Why this matters

These two apps show the intended architecture pattern:
  • Horizons handles platform concerns
  • App repos own domain models and product UX
  • Teams ship quickly without rebuilding agent infrastructure per app