kestrel

Security at Kestrel

Last updated October 10, 2026

Security at Kestrel

This page describes the controls Kestrel has in place today. It makes no claim to any certification.

Your books can't be quietly rewritten

  • Posted journal entries are immutable. Corrections are new reversing entries, never edits or deletions.
  • Every posted entry gets a sequential number and a cryptographic seal (SHA-256) chained to the entry before it. Kestrel checks the chain daily, along with control accounts (receivables, payables, inventory) against their detail records, and records the result.
  • Closing a month stores its balances. A month closed for good can only be reopened by an administrator.
  • Every action in your books is written to an append-only audit log that shows who did what, and when.

Each company's data is separated in the database

Kestrel's database enforces access per company on every query (row-level security). The application connects with a role that cannot change the schema or bypass those rules, and each request is tied to a verified membership before any company data is read.

Encryption

  • In transit: HTTPS with TLS 1.2 or later for the app and website; encrypted, certificate-verified connections between our servers, database and background-job service.
  • At rest: our database provider encrypts stored data. Bank connection credentials are additionally encrypted by Kestrel with AES-256-GCM using keys we hold separately from the database.

Bank connections

Banks connect through Plaid. Kestrel never sees your bank username or password and has read-only access: it cannot move money. You can disconnect a bank at any time, which also removes the connection at Plaid.

Accounts and access

  • Sign-in is handled by WorkOS. Two-step verification (a code from an authenticator app) is required before connecting a bank or a Stripe account.
  • People join a company only by invitation, with a role (owner, admin, accountant, member, viewer). Viewers can read and export but not change the books.
  • Access to Kestrel's production systems is limited to a small number of named people, using individual accounts with two-step verification.

Engineering practices

  • Every change runs automated checks before it ships, including the full database rule test suite, a dependency vulnerability audit, and a scan for accidentally committed secrets.
  • Dependencies are monitored for known vulnerabilities, with automatic security updates.
  • Secrets live in our hosting provider's secret store, never in code.

Reporting a vulnerability

Email security@kestrelerp.com. We'll acknowledge reports within 2 business days.