Architecture

Architecture Overview

System layers, data flow, execution guarantees, and tech stack.

ArchitectureOverview
Last updated March 17, 2026

System Layers

Solvren is composed of the following layers:

  1. Integrations — Connect billing, CRM, pricing, and other revenue systems
  2. Identity Graph — Entity resolution across systems for correlated signals and issues
  3. Signals — Ingested, normalized data streams
  4. Detectors — Logic that creates issues from signals (detector packs)
  5. Issues — Detected revenue-impacting problems
  6. Impact Engine — Quantifies revenue at risk and feeds prioritization
  7. Playbooks — Defined workflows and actions for resolution
  8. Execution Engine — Orchestrates actions, write-back, retries, and state
  9. Verification — Confirms outcomes against external systems
  10. ROI Tracking — Recovered revenue, avoided loss, dashboards
  11. Safe Automation — Policies, approvals, safe mode, confidence thresholds

Data Flow

Signals → Detectors → Issues → Impact → Actions → Verification → ROI


Key Principles

Explainability

Every issue is traceable to signals and evidence.

Reliability

All actions are idempotent and retry-safe.

Observability

All operations are logged and auditable.

Safety

Policies control execution and automation.


Execution Guarantees

  • No duplicate actions (idempotent design)
  • Safe retries
  • Full audit trail
  • External state verification

Outcome

A deterministic, explainable, and reliable system for revenue protection.


Tech stack

  • Frontend: Next.js 16, React 19
  • Backend: Next.js API routes, Supabase
  • Auth: Supabase Auth
  • Database: Supabase (PostgreSQL)

✏️ Edit this page on GitHub
Was this page helpful?
Send feedback