[rosetremiere]

The faq helped, thanks! So, an example of typical use would be, say, as the internal ledger for a company like (transfer)wise, with lots of money moving around between accounts? But I understand it's meant to be used internally to an entity, with all nodes in your system trusted, and not as a mean to deal with transactions from one party to another, right?

[eatonphil]

Yes that's a good example!

And you can model external accounts that have their own confirmation process using our two-phase transfer support.

https://docs.tigerbeetle.com/FAQ#what-is-two-phase-commit

[jorangreef]

Great to hear! Joran from TigerBeetle here.

Yes, exactly. You can think of TigerBeetle as your internal ledger database, where perhaps in the past you might have had to DIY your own ledger with 10 KLOC around SQL.

And to add to what Phil said, you can also use TigerBeetle to track transactions with other parties, since we validate all user data in the transaction—there are only a handful of fields when it comes to double-entry and two-phase transfers between entities running different tech stacks.

The TigerBeetle account/transfer format is meant to be simple to parse, and if you can find user data that would break our state machine, then it's a bug.

Happy to answer more questions!