Settler is reconciliation intelligence plus an audit-grade operating system: deterministic runs, hash-linked proofpacks, explicit degraded states, and tenant-scoped operator truth (not UI-invented summaries).
Settler matches financial transactions across data sources (e.g., Stripe payments vs. bank deposits) with replayable outcomes, adjudication-backed institutional memory, and evidence exports operators and auditors can verify.
- Finance operations teams who need automated, audit-ready reconciliation
- Engineering teams building financial products that require transaction matching
- Compliance teams needing deterministic evidence for every reconciliation decision
- Stripe ↔ Bank transaction matching with configurable tolerances
- Manual review queue with audit trails
- Deterministic evidence generation for every decision
- CSV/API ingestion pipelines
- Multi-workspace tenant isolation
See What Works Today for full details.
Settler's architecture is composed of five primary layers, ensuring a separation of concerns between deterministic computation, policy enforcement, and operator interfaces.
- Rust Kernel: Provides deterministic primitives for computation, hashing, and proofs.
- TypeScript Control Plane: The
packages/apiservice, which handles orchestration, tenancy, API routes, and persistence policies. - CLI Surface:
packages/cliprovides the primary interface for operators, automation, and local development verification (e.g.,foundry). - Console Surface: The
packages/webNext.js application, which serves as the visualization and control surface for operators. - Enterprise Integration Layer: Connectors and policies for managed environments.
For persistence, the platform uses a hybrid model:
- TigerBeetle: Acts as the immutable, high-performance ledger core for all financial-grade transactions.
- PostgreSQL (Supabase): Stores projections, operational metadata, audit logs, and tenant configurations.
packages/api— Node.js Control Plane (Express, TypeScript).packages/web— Next.js Operator Console.packages/cli— Engineering and Foundry tooling.crates— Rust Kernel and related utilities.docs— Canonical documentation.scripts— Verification, repo hygiene, and automation.
For the complete local setup guide, see Canonical Local Setup.
After install, run a deterministic onboarding checklist (no network, no secrets):
pnpm exec tsx packages/cli/src/index.ts first-runThe canonical verification command to ensure your environment is correctly configured and the codebase is healthy is:
# Run the full linting, typechecking, and testing suite
pnpm verifyFor canonical run surface + proofpack + tenant posture checks without the full verify wall clock:
pnpm run verify:moat-readinessGlobal helper scripts are available for managing the local TigerBeetle container:
pnpm tb:start— Start the TigerBeetle container.pnpm tb:status— Check the ledger's health.pnpm tb:logs— Follow ledger logs.pnpm tb:reset— Wipe and reformat the ledger (for development use only).
Getting started:
- Quickstart — Fastest path to running locally
- Canonical Local Setup — Full local development setup
- Demo Walkthrough — Step-by-step demo guide
- Starter Kits — Runnable example projects
- What Works Today — Core functional workflows
- Intentional Boundaries — What's not production-ready
- Common Setup Traps — Avoid setup issues
Evaluation and pilot:
- Pilot Runbook — Run a pilot with go/no-go scorecard
- Trust Packet — Security, privacy, and procurement info
- Teardown Guide — Clean removal and offboarding
Reference:
- Architecture (Canonical)
- API Reference
- Verification Commands — All verification commands
- Security Policy
See CONTRIBUTING.md for the contribution workflow and quality gates. All pull requests must pass the pnpm verify suite.
Settler is licensed under the terms found in LICENSE.
- Squash-only merges
- Auto-delete merged branches
- Weekly dependency update windows
- Security scanning in CI