About
This blog is run by the team behind EntryTarget — dedicated double-entry ledger infrastructure that deploys inside the customer’s own AWS account.
What we write about
- Engineering notes. How the Rust runtime handles batching, crash recovery, and back-pressure. Why we chose the boring primitives we chose.
- Security posture. Integrity model, key rotation, license signing, where data physically lives, and what we can (and cannot) see from our side of the line.
- Operations. The AWS CDK stack we deploy, the IAM template customers review, the heartbeat and license flow that keeps the runtime honest.
- Accounting primitives. Why double-entry still wins in 2026, reconciliation patterns, and the operational consequences of asking “where did this number come from?”
We don’t publish on a schedule. Posts go out when there’s something worth writing down.
Get in touch
- Waitlist / sales: contact@entrytarget.com
- Security reports: security@entrytarget.com (policy)
- Source & changelog: github.com/entrytarget