Movements
Every transaction moves a resource from one account to another. Bkper enforces the zero-sum invariant and derives balances from posted records.
Bkper Platform
The programmable ledger behind trustworthy finance workflows.
Bkper provides the hard accounting infrastructure — zero-sum books, reliable balances, events, permissions, app identity, and audit trails — so your apps, reports, and AI agents all work from the same source of truth.
Need help designing the workflow? Access our expertise through Professional Services.
The model
Keep the book as the source of truth.
Bkper is not a database beside your accounting system. It is the bookkeeping core your tools read from and write to.
Context
Groups, properties, and hashtags add reporting meaning without account sprawl or external metadata tables.
Events
Transactions, accounts, files, and comments produce events. Apps react with their own identity in the activity trail.
What teams build
Build workflows directly on the books your team reviews.
Replace spreadsheet glue and side databases with tools that operate directly on the books your team already reviews.
Statement intake
Import files, route exceptions, post movements, and keep review in the book.
Client reporting
Turn balances, groups, properties, and hashtags into recurring reports.
Audit coordination
Track checks, evidence, comments, locks, files, and app actions together.
Book-aware automation
Mirror transactions, consolidate books, and model any countable resource.
Managed platform
What you do not have to rebuild.
Start from Bkper’s ledger, app runtime, and developer tools instead of assembling infrastructure around exported accounting data.
Hosted apps
Deploy to {appId}.bkper.app with routing and SSL handled.
OAuth & permissions
Users sign in with Google; the platform manages tokens and access.
Events & webhooks
Declare handlers and receive book events locally or in production.
Secrets & KV
Store app secrets and key-value state through platform bindings.
Preview & logs
Use preview environments and inspect retained request logs from the CLI.
API, SDK, CLI, MCP
Build from scripts to full apps with Bkper-native interfaces.
Built on Google Cloud — Google’s data centers, encryption, and infrastructure behind every API call. See security
A real operation on Bkper
How Brain turns books into a reporting operation
Brain’s team processes financial data for client funds and family offices, runs custom tools around the books, and delivers reporting back to clients — all on top of Bkper.
- 01 Bank statements arrive
Client data enters the operation through books and connected tools.
- 02 Transactions are processed
Movements land in accounts, preserving balances and traceability.
- 03 Apps and scripts run
Custom automation handles the work their operation actually needs.
- 04 Reports and audits follow
Outputs stay tied to the same source of truth and activity trail.
“The partnership with Bkper has been a cornerstone of Brain’s digital strategy, driving operational efficiency, cost savings, and enhanced service delivery.”
Camilo Preve Partner, Brain
Developer path
Build without rebuilding app plumbing.
Start locally, receive live book events, deploy safely, and inspect logs from the CLI.
bkper app init Create the app structure, config, client, and Worker server.
bkper app dev Run locally with HMR and live webhook delivery to your laptop.
bkper app deploy Preview first, then serve your app on the managed Bkper runtime.
CLI Agent
Use Bkper-native help when you build
Query balances, scaffold handlers, inspect commands, and keep the from-to model explicit while you code.
Explore the CLI Agent
Build on one source of truth.
Use Bkper as the bookkeeping core for custom finance workflows, reporting, and automation.