A portable, encrypted, offline-first data platform built on a
self-contained file format: .fieldbook
— a ZIP archive containing an AES-encrypted SQLite database,
schema, hash-chained operation log, hash-chained audit trail,
and embedded documents.
A .fieldbook file is the unit of work, the unit of transfer, and the unit of audit. Open it in the desktop app, mail it to a colleague, archive it for seven years — it remains a single verifiable object.
Fieldbook ships with a complete KYC / CDD framework: cryptographic attestation of documents, a nine-state lifecycle from collection through certification, and Chinese Wall information barriers for multi-firm engagements.
Passport created, no documents collected yet.
One or more mandatory documents uploaded; collection in progress.
All mandatory documents collected; verification not yet performed.
Documents under review by a verifier; cryptographic attestations being collected.
All mandatory documents verified; passport may now be certified.
Certification issued. Passport is operational and may be exposed to authorised counterparties.
A document has expired; replacement must be supplied within configured grace window.
Grace window elapsed without replacement. Passport temporarily unusable until refreshed.
Passport frozen for investigation or litigation; no modifications permitted until released.
SHA-256 document fingerprints + signed attestation statements (HMAC) bound to verifier identity, document, time, and method.
HMAC for internal signing, PKCS7 for external, QES (Qualified Electronic Signature) framework for regulated jurisdictions.
Information barriers across firms inside the same file. Cross-wall access requires explicit authoriser approval, logged to audit.
Right-to-erasure, data subject requests, cross-border transfer logging — implemented at the format level, not bolted on.
Policy-driven row filtering. The same file shown to different users yields different rows — enforced by the engine, not by the UI.
Obligations extracted by Redline Ledger flow into Fieldbook for evidence collection and auto-satisfaction tracking.
Tauri 2 + React 18 + TypeScript. Primary cross-platform client. 84 UI components, 80+ core modules, 43 test files.
Native SwiftUI app with modular store pattern. Direct FFI to fieldbook-core; full feature parity with desktop.
SwiftUI + UniFFI bindings to the Rust core. Same .fieldbook files open identically across all clients.
27 subcommands. Open, inspect, query, export, validate, encrypt, sync. Pipe-friendly. CI/CD ready.
Axum HTTP API with PostgreSQL backend for centrally-hosted deployments. Drop-in replacement for local file mode.
Chrome and Safari. Captures structured evidence directly from the web into the active .fieldbook.