# Overview

A multi-tenant double-entry ledger engine for building financial applications.

URL: https://docs.shiwake.app/docs



Shiwake is a domain-agnostic, multi-tenant, double-entry ledger engine.
It exposes the primitives every financial application needs (accounts,
journal entries, balances, holds, reversals, and reconciliation) over a
versioned REST API, with an official .NET SDK on top for higher-level
banking operations.

It is designed for engineering teams who need a correct, auditable ledger
*inside* a larger product: neobanks, payment platforms, wallets, loan
servicing, marketplace escrow, parent-portal billing. Shiwake handles
the accounting; you build the product on top.

What it gives you [#what-it-gives-you]

* **Double-entry, always balanced.** Every journal entry must balance
  per-currency before it posts. The engine rejects anything that doesn't.
* **Multi-tenant by default.** Every row is scoped to a tenant, enforced at
  the database layer via global query filters. One API, many isolated books.
* **Holds and captures.** Authorize an amount now, settle later. Partial
  captures release the remainder automatically.
* **Reversals, not deletes.** Journal entries are immutable. Corrections
  post compensating entries with a `reversalOf` pointer. Your audit trail
  is never rewritten.
* **Reconciliation built in.** Trial balance and stored-vs-computed balance
  verification are first-class endpoints.
* **Idempotent mutations.** Every write accepts an `Idempotency-Key` and
  replays the original response on retry.
* **Per-tenant rate limiting.** One noisy tenant can't affect another.

What it does not do [#what-it-does-not-do]

Shiwake is intentionally narrow. It does **not** know about customers,
products, orders, fees, FX rates, payment rails, or KYC. That is your
product's job. Think of Shiwake as the books your product writes to, not the product itself.

How it compares to Apache Fineract [#how-it-compares-to-apache-fineract]

Fineract is a full core banking platform: loans, savings, KYC, reporting,
workflows, the lot. Shiwake is the opposite end of the spectrum: just
the ledger, nothing else. If you need a batteries-included banking stack,
use Fineract. If you need to own the product and use a ledger that gets
out of your way, use Shiwake.

Two layers [#two-layers]

<Cards>
  <Card title="REST API" href="/docs/api">
    The raw engine. Accounts, journal entries, holds, reconciliation.
    Language-agnostic, HTTP + JSON, `X-Api-Key` auth.
  </Card>

  <Card title=".NET SDK" href="/docs/sdk">
    Typed C# client with a higher-level **Banking** layer for common
    operations: deposits, withdrawals, transfers, disbursements.
  </Card>
</Cards>

Next steps [#next-steps]

<Cards>
  <Card title="Core concepts" href="/docs/getting-started/concepts">
    Double-entry, normal balances, tenants, and holds in 5 minutes.
  </Card>

  <Card title="Quickstart" href="/docs/getting-started/quickstart">
    Provision a tenant, post your first entry, read the balance.
  </Card>
</Cards>
