TigerBeetle famously uses static allocation. Infamously, the use of the term is idiosyncratic: what is meant is not static arrays, as found in embedded development, but rather a weaker no allocation after startup form. The amount of memory TigerBeetle process uses is not hard-coded into the Elf binary. It depends on the runtime command line arguments. However, all allocation happens at startup, and there's no deallocation. The long-lived event loop goes round and round happily without alloc.