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
Build reports, automations, and AI-assisted workflows around books that stay balanced and reviewable. Bkper provides the accounting model underneath: zero-sum Books, from-to Transactions, reliable balances, Events, permissions, app identity, and audit trails.
The model
Bkper is not a database beside your accounting system. It is the bookkeeping core your tools, scripts, apps, and AI agents read from and write to.
Every transaction moves a resource from one account to another. Bkper enforces the zero-sum invariant and derives balances from posted records.
Groups, properties, and hashtags add reporting meaning without account sprawl or external metadata tables.
Transactions, accounts, files, and comments produce events. Apps react with their own identity in the activity trail.
What teams build
Replace spreadsheet glue and side databases with tools that operate directly on the same books you or your team already review.
Import files, route exceptions, post movements, and keep review in the book.
Turn balances, groups, properties, and hashtags into recurring reports.
Track checks, evidence, comments, locks, files, and app actions together.
Mirror transactions, consolidate books, and model any countable resource.
Managed platform
Start from Bkper’s model, ledger, app runtime, and developer tools instead of assembling infrastructure around exported accounting data.
Zero-sum Books, from-to Transactions, Accounts, Groups, properties, files, and balances are API-addressable primitives.
Deploy to {appId}.bkper.app with routing and SSL handled.
Users sign in with Google; the platform manages tokens and access.
Declare handlers and receive book events locally or in production.
Store app secrets and key-value state through platform bindings.
Use preview environments and inspect retained request logs from the CLI.
Call curated, multi-provider models through one OpenAI-compatible endpoint with Bkper auth — included allowance, no separate provider keys or bills.
Use the same accounting primitives from scripts, assistants, pipelines, and full apps.
Built on Google Cloud — Google’s data centers, encryption, and infrastructure behind every API call. See security
A real operation on Bkper
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.
Client data enters the operation through books and connected tools.
Movements land in accounts, preserving balances and traceability.
Custom automation handles the work their operation actually needs.
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.”
Developer path
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.
Query balances, scaffold handlers, inspect commands, and keep the from-to model explicit while you code. Included Bkper AI models power it out of the box — no API keys to configure.
Explore Bkper CLI Agent
Use Bkper as the bookkeeping core for custom finance workflows, reporting, and automation.