Bitcoin accounting infrastructure

Bitcoin's
Accounting Layer

Audit-ready Bitcoin books on infrastructure you control.

Install the CLI
View script
$ curl -fsSL https://clams.tech/install.sh | sh > powershell -c "irm https://clams.tech/install.ps1 | iex"
Finder File Edit View Go Window Help
9:41 AM

Works with Claude, Codex, Opencode and more

3,000+ Desktop downloads shaped the product
Double-entry Books that tie out, not a balance tracker
CLI + Server API One binary, self-hosted
Never metered Not by wallet, transaction, or report

One ledger for Bitcoin, Lightning, and Liquid

Native node connections, xpub and descriptor scans, and CSV imports

Three problems you know too well

  1. You're paying tax on a sale you never made.

    A move between your own wallets gets booked as a sale. You're taxed on a gain you never made.

  2. Your entire financial history sits on someone else's server.

    Your addresses, xpubs, and every transaction live on someone else's server. All it takes is one data breach.

  3. Your books don't balance. You can't prove they do.

    A matching wallet total is not a ledger. Without double-entry, there is nothing to audit.

Clams was built for exactly this.

  • Data stays on your machine by default.
  • Recognizes transfers from real sales.
  • Balances derived from real double-entry accounting.

From wallet to report

01

Connect

Link your wallets. Transactions flow in automatically.

02

Transform

Raw transactions become structured journal entries

03

Analyze

Surface insights across all your wallets

04

Report

Export audit-ready reports for compliance and planning

Built for millions of transactions.

Minutes
Full history import
Unmetered
Wallets and transactions
Incremental
Syncs pick up where they left off

Audit-ready books

Double-entry accounting. Automated reconciliation. Balance tracking across all wallets, current to your last sync.

  • Smart transfer matching between your wallets
  • Auto-categorization with manual override
  • Cost basis tracking and capital gains calculations
  • Catch errors before your auditor does
Explore enterprise →
Clams keeps accounting records on infrastructure you control The CLI and Server REST API use the same Clams engine. Accounting records are stored either on your machine or on your self-hosted server. Hosted Google, Apple, or email magic-link authentication, licensing, billing, and rates services exchange limited operational information separately and do not receive accounting records. Configured wallet, node, and chain-source endpoints may also be remote. Workspaces, role-based access, member invites, and audit-ready exports are available with the deployment. CLI SERVER API SERVER HOSTED SERVICES HOSTED AUTH · BILLING · RATES AUTH · RATES Clams ACCOUNTING ENGINE SYNC → DOUBLE-ENTRY JOURNALS → COST BASIS & REPORTS SYNC → JOURNAL → REPORT WORKSPACES ROLE-BASED ACCESS RBAC AUDIT-READY EXPORTS EXPORTS CHOOSE WHERE CLAMS RUNS Your machine Local database Your server Self-hosted ACCOUNTING RECORDS STAY HERE On infrastructure you control

Flexible by design

Choose how you work. Start simple, scale as you grow.

  • One binary, two interfaces: CLI and Server REST API
  • Store accounting records on your machine or your own server
  • Workspaces and profiles isolate clients, entities, or teams
  • Role-based access with Google, Apple, or email magic-link sign-in
Compare deployment options →

Bitcoin-native

Built for multisig and the complex transactions legacy tools choke on.

  • Reconcile multisig wallets automatically. No manual matching.
  • Account for channel opens, closes, and force-closes, not just payments.
  • Handle on-chain fees and change outputs without inflating gains.
  • Account for L-BTC and Liquid assets like USDt alongside your BTC

The accounting infrastructure Bitcoin was missing

Let's talk about what Clams can do for your organization.