黒字Kuroji
Sign inGet started

How It Works · Sign Up To First Number In 10 Minutes

From Sign Up To Your First Runway Number, In Under Ten Minutes.

Most finance tools require you to maintain a hiring plan, a vendor list, scenario assumptions, and three other spreadsheets. Kuroji requires that you connect a bank. The system does the rest, and shows you everything it did.

  1. 01

    Step 01

    Connect A Bank In Under Ninety Seconds.

    Plaid handles the OAuth handshake on Kuroji's behalf. Your bank credentials never touch our servers; Plaid issues us a short-lived item token that can be revoked from your bank's dashboard at any time. Kuroji supports every institution Plaid does — RBFCU, Mercury, Brex, Chase, SVB, Ramp, and roughly twelve thousand others.

    PSD2 / FDX Compliant · Read-Only Access · Item Revocable

  2. 02

    Step 02

    Connect Your Stripe Accounts.

    One read-only restricted key per Stripe account, scoped to balance transactions and charges. Multi-account if you run a portfolio of products on separate Stripe accounts (you do — half our beta cohort runs four or more). Kuroji never has permission to issue charges, refunds, or transfers.

    Restricted Key · balance.transactions + charges Scopes Only

  3. 03

    Step 03

    Kuroji Ingests Every Transaction As An Immutable Event.

    Every bank line, Stripe charge, and payroll run becomes one row in an event-sourced ledger. Each row is linked to the row before it by SHA-256 hash. This is the canonical layer — the source of truth from which everything else descends. The books, the dashboards, the answers Kuroji gives you: all are derivations of this layer.

    Hash-Chained · Content-Addressable · Re-Derivable

  4. 04

    Step 04

    Journal Entries Project From A Deterministic Rule Engine.

    Categorization runs on a rule engine, not a black-box model. The same charge always produces the same journal entry. When you correct a categorization, that correction becomes a permanent rule that applies retroactively and forward. No silent overwrites; every edit lands in the audit log.

    Same Input → Same Entry · Learns From Your Corrections

  5. 05

    Step 05

    Ask Kuroji Anything.

    'What's our runway?' returns a number with a citation chain back to the events that produced it. 'Anything weird this week?' returns ranked anomalies. 'Draft the May investor update' returns a draft with the underlying numbers linked inline. Kuroji never computes money in its head — every numeric answer is a deterministic projection of canonical events.

    Cited Answers · Grounded In Events · No Extrapolation

  6. 06

    Step 06

    Optionally, Let Kuroji Act.

    After you've watched Ring I for a while and trust what it sees, you can opt into Ring II (writes to your books) and Ring III (acts externally). Each ring has its own consent flow, its own scopes, and its own hard limits — written into the auth chain, not into a config file someone could change quietly.

    Three Rings · Earned Outward · Revocable At Any Moment

The Shape Of The Data

One Long Chain.

Every event links to the one before it by SHA-256 hash. Every journal entry links to the events that produced it. The books are a deterministic view of the chain, not an independent source of truth.

event { id: e_0001, prev: GENESIS,    payload: plaid.transaction.added }
event { id: e_0002, prev: hash(e_0001), payload: plaid.transaction.added }
event { id: e_0003, prev: hash(e_0002), payload: stripe.charge.succeeded }
event { id: e_0004, prev: hash(e_0003), payload: gusto.payroll.run        }
            ⋮
journal_entry { from: e_0001, debit: Software, credit: BankA }
journal_entry { from: e_0002, debit: Hosting,  credit: BankA }
        ⋮ chain continues
        ⋮ derivable from any event
        ⋮ verifiable in isolation

Connect Your First Bank

Ninety Seconds From Now, Kuroji Is Reading Your Bank.

Start Watching →