The resource-transaction database
One place to decide what is available.
Mira is an open-source database project being developed in Zig to decide who can use a resource, how much they can use and for how long.
One stable booking identity.
Capacity, time and authority.
A retry recovers the same outcome.
Planned behavior, shown as a product example. This is not output from a released engine.
When availability is a decision
The last room. The final item in a basket. The remaining GPU capacity. These are decisions that concurrent requests must agree on, even when a server crashes or a successful reply is lost.
Mira's purpose is to make resource rules part of the transaction authority: check the rules, commit the outcome and preserve the identity of that decision across retries.
Several resources. One business outcome.
A proposed booking might require a room, a person and equipment. An atomic bundle must acquire all required resources or leave the prior state intact. Putting requests in the same transport batch does not, by itself, make them one atomic bundle.
- Explicit claims, temporary holds, confirmation, cancellation and expiry.
- Exact quantities and conservation rules for each resource kind.
- Stable request identities and durable retry outcomes.
- Tenant authority, versioned rules and fenced ownership.
A focused part of your application
Your application still owns its content, discovery, recommendations and business experience. Mira is designed to own the authoritative resource decision and publish committed outcomes to other systems.
The project is at the research and formal-specification stage. Adoption of the Zig engine foundation and implementation of the resource model are ahead; a production release has not been qualified.
Help shape what comes next.
Talk to the founder