Public site
Routes under src/app for product, architecture, docs, roadmap.
Product
Architecture and capability proof
A visual view of what is currently shipped: module boundaries, capability clusters, integration points, and packaging boundaries.
Product pillars
How the console and docs are organized: reconciliation core, exception operations, evidence and audit, and the control plane (API, webhooks, billing, settings).
Reconciliation core
Runs, policies, schedules, and replay surfaces for deterministic execution truth.
Exception ops
Queues, severity, analytics, and bounded AI insights with explicit degraded states.
Evidence + audit
Proof explorer, audits, and audit trail for replayable, exportable artifacts.
Control plane
API keys, webhooks, workflows, billing, diagnostics, and tenant settings.
The Settlement Pipeline
Deterministic matching with bit-perfect reproducibility and audit-grade evidence.
Ingest
Multi-source raw data
Normalize
Canonical transformation
Reconcile
Deterministic matching
Evidence
Hash-linked manifests
Adapter & Ingestion Layer
Standardized connectors for existing financial infrastructure and data sources.
Stripe
Salesforce
Custom ERP
Legacy DB
API Hub
Global Control Plane
Platform-wide orchestration and regional synchronization boundaries.
System map
Platform overview: surfaces, control plane, and runtime boundary
Product surfaces
Operator console
Authenticated routes under src/app/app for runs, policies, proofs, and audit.
APIs + docs
Route handlers under src/app/api and OpenAPI surface.
Control plane + deterministic engine
Reconciliation + proof services
Domain + lib modules for run execution, evidence, replay, and validation.
Policy + governance
Policies, rule evaluation, approvals, and entitlement boundaries.
Observability + diagnostics
Tenant-safeAudit logs, trust graph checks, and system health surfaces.
Execution + data boundary
Workers + adapters
packages/adapters, jobforge adapter packages, and CLI-triggered jobs.
Storage + cache
Database access, Redis/cache modules, and immutable evidence artifacts.
External systems
Stripe/ERP/bank sources through adapter interfaces and signed ingestion endpoints.
Capability Clusters
Functional boundaries and interface definitions.
Capability map grounded in shipped surfaces
Deterministic reconciliation
- Rule-based matching with explicit tolerances
- Replayable run semantics
- Mismatch classification and explainability
Evidence + auditability
- Proof explorer and evidence routes
- Hash-linked output artifacts
- Traceability across run lifecycle
Tenant safety + governance
- Shared tenant middleware + context boundaries
- Policy enforcement surfaces
- Role-aware operator workflows
Developer ergonomics
- CLI + SDK onboarding
- Docs, cookbook, and quickstart routes
- Adapter extension model
Integration surface map
CLI
packages/cli for local runs, automation, and CI orchestration.
SDKs
packages/sdk, sdk-java, sdk-csharp, and react-settler integration points.
API
REST/route handlers in src/app/api with OpenAPI schema route support.
Events + hooks
Webhook and async flow support through queue/worker modules and replay traces.
Packaging boundary map
Boundaries are based on repository packages and current public route structure.
Open source core
Core engine, CLI, and SDK packages available in this repository.
/open-source · /oss · packages/*
Cloud / managed workflows
Hosted control-plane and dashboard experiences surfaced through web routes.
/dashboard · /app/* · /status
Enterprise controls
Policy, audit, and trust-oriented features highlighted in enterprise and trust pages.
/enterprise · /trust · /security-and-audit
Engineered for high-integrity financial operations where every byte counts.
Want deeper implementation proof? See architecture, workflow lanes, and changelog with shipped versus directional separation.
Product proof references
Settler is built on verifiable truth. This registry connects marketing claims to concrete implementation modules, ensuring every capability is auditable.
Control-plane and reconciliation surfaces
Public and authenticated route layers expose deterministic run, policy, and evidence paths.
Execution runtime modules
Adapter, SDK, and protocol packages back deterministic execution and integration boundaries.