Reconciliation Infrastructure You Can Actually Inspect
Settler publishes MIT-licensed SDK, protocol, CLI, and React packages plus Apache-2.0 Rust crates. The hosted web console, control-plane API, adapters, and data schema remain proprietary platform code.
What's public
Package-level licensing and repository classification define the public boundary.
Rust Verification Kernel
Apache-2.0 crates for deterministic primitives, hashing, content-addressed artifacts, and proof verification.
CLI
Run reconciliation jobs from the command line or CI. Pack inputs, execute runs, inspect output, verify evidence hashes.
TypeScript SDK
Typed client for creating jobs, polling runs, fetching mismatches, and exporting evidence. Integrates with any Node.js or Deno runtime.
Evidence Model
Public protocol types and verification tools support independent checks of compatible evidence artifacts.
Examples and Local Tooling
Public examples and CLI workflows demonstrate local reconciliation and evidence verification without exposing the hosted control plane.
Verification Tools
WASM and CLI verification surfaces let reviewers inspect artifact integrity outside the hosted application.
Run the local demo
Clone, install, and run the demo path to inspect a local reconciliation and its evidence output. Setup time depends on the local toolchain.
Clone the repo
git clone https://github.com/Hardonian/Settler.git && cd SettlerInstall dependencies
pnpm installRun the demo
pnpm demoInspect evidence output
cat examples/demo-output/evidence.jsonWhy use the public packages?
- Keep local workflows inside your chosen environment when configured that way
- Evaluate public packages without adopting the hosted platform
- Inspect the published package source and license terms
- Customize matching rules and adapters for your specific data model
- Verify compatible evidence artifacts with the public CLI or WASM tooling
Architecture
Public packages expose the verification and client-side portion of the system.
Data In
CSV, JSON, Parquet, webhook events, or any adapter-supported source. Inputs are deterministic and version-pinned.
Engine Core
Rules-based matching with configurable field tolerance, multi-source joins, and exception classification.
Evidence Out
SHA-256 hash chain over the full evidence payload. Mismatch report, variance log, and replay bundle.
Inspect the Source Before You Trust It
Financial infrastructure should be auditable. Read the code, run the tests, verify the evidence model.