The bricks

Start with statement data, transaction activity, a shadow ledger or workflow orchestration. Use the documented APIs and CLIs to connect the modules your work needs. Prototypes and planned products are listed separately below.

Available modules

Apps with documented APIs and command-line clients.

📄Available

Statements→

Upload supported bank and card statements. Query accounts, transactions and balances, apply classification rules, and inspect checks and reports.

Open app ↗Docs →

💳Available

Transactions→

Extract supported bank notifications from a connected mailbox into accounts and transactions. Read the resulting activity through the UI, API or CLI.

Open app ↗Docs →

⚙️Available

Orchestrator→

Define stations and steps, schedule runs, and inspect work records and supporting documents. Configured workers execute your step code.

Open app ↗Docs →

Built around the API

Programmatic writes, with views and reports for inspection.

📒API & CLI

Ledger→

Mirror upstream records as balanced transactions and entries. Query by account and dimension, and inspect financial reports. Your upstream system remains the book of record.

Open app ↗Docs →

Prototypes

Being explored; not ready for public use.

🗂️Prototype

Master Data→

Exploring schema-defined vendor records, field history and conformance with mock integrations. Public API access and live source-system integrations are not ready.

Planned

The direction we are working toward.

🤖Planned

Assistant→

Architecture work toward an assistant that uses your financial tools together. Federated assistance and external connectors are planned, not available today.