Request information

For operators, mission teams and engineers who want to know whether Mru fits their system. Tell us what you run. We will answer plainly.

→ Request information

Tell us what you run.

A few lines are enough: the hardware, where it is, and how long it must run without a visit. We will tell you plainly whether Mru fits, including when it does not.

  • Requests go to the founder, not a sales team.
  • We reply by email. If a call helps, we suggest one.
  • Technical questions are welcome. The docs and code are public.

Or write to contact@mru.space

Interested in

We use these details only to reply. No mailing list.

Checking fit

Mru fits when three things are true

The equipment has two or more processors. It must run unattended for months or longer. A repair visit is slow, costly or impossible.

Use cases

Engineers

Read the code before you write

The decision core, its proofs and the simulator are open source. The docs start with the shrinking quorum.

Docs

Research and partners

Cite it, test it, challenge it

The whitepaper and every result are published with their limits. We welcome independent checks.

Research

Email contact@mru.space · Code github.com/mruspace · Whitepaper doi:10.5281/zenodo.20579438