Mira

In development. Built in Zig.

A database forresource transactions.

Mira is being built to manage reservations, inventory, capacity and budgets through durable transactions with explicit rules.

Explore MiraSee what is ready
Designed for
  • Reservations
  • Capacity
  • Inventory
  • Intervals
  • Concurrency
  • Budgets

Six resource types. Explicit rules.

One identity, one owner

The same seat cannot be sold twice.

A particular room, seat or device has its own identity. Mira's design admits a claim only when that identity is available under its rules.

Explore exclusive

The last unit. The right decision.

Workloads we are designing for, from a single reservation to a bundle of resources that must succeed together.

Seats and rooms

Coordinate temporary holds, confirmed reservations and cancellations without selling the same availability twice.

Explore use case

Inventory and orders

Reserve a basket together, consume stock once and make returns and corrections explicit.

Explore use case

Compute capacity

Admit work against shared GPU, memory and worker capacity in one resource decision.

Explore use case

Appointments

Reserve a person, a room and equipment over the same time window.

Explore use case

Concurrent work

Keep active jobs within tenant limits and distinguish current owners from expired workers.

Explore use case

API and spending limits

Share an allowance across callers with accountable debits, retries and replenishment.

Explore use case

Verification

Correctness you can inspect.

TLA+ models cover the foundation and resource design. Verification is in progress; engine conformance remains ahead.Explore verification
01

Specify

The required behavior is defined before implementation.

02

Check the design

TLC explores bounded states, including modeled failures.

03

Check execution

Observed implementation transitions must conform to the contract.

04

Retain evidence

Keep exact inputs, verdicts and the limits of each check.

Planned client ecosystem

A Zig core. Your language next.

The client plan builds on a shared C ABI and seven language bindings, with JavaScript and TypeScript served through Node.js.Inspect the development plan
Rust
TypeScript
JavaScript
Python
Go
Java
.NET
C
Ruby

Core

A planned Zig foundation with deterministic execution.

Protocol

Planned shared retry, cancellation and result semantics.

Clients

Language SDKs follow the stable public protocol.

What is your
scarce resource?

Bring a real workload. Help shape the cases Mira has to get right.

Talk to the founder