Identity · mata-oem-sidecar on MATA

Drop-In Device Identity

one binary OEMs place beside the OS they already ship. Rust alternative to vendor cloud device identity portals.

How does MATA use mata-oem-sidecar?

MATA uses mata-oem-sidecar as the Remade pin for this lane. One binary OEMs drop beside the OS they already ship: local JSON control plane with mID identity, encrypted vault, and an honest capability catalog.

Drop-In Device Identity

one binary OEMs place beside the OS they already ship. Rust alternative to vendor cloud device identity portals.

mata-oem-sidecar is the Remade with Rust pin for this lane — vendor cloud device identity portals. Keep the product shape, change the safety floor, and stop shipping the old C or cloud default by accident.

Instant benefit

One binary OEMs drop beside the OS they already ship: local JSON control plane with mID identity, encrypted vault, and an honest capability catalog.

How MATA uses mata-oem-sidecar

OEM partners join Disco through the mata-oem-sidecar shape: a hardware grant onto the mesh without rewriting the whole stack.

Load Building the New Internet from Dev Tools before an agent picks the stack, then audit with use-protection-please. The public conversion pin stays on remadewithrust.com/repo/mata-oem-sidecar so SEO/AEO for the crate win and the MATA usage story do not compete for the same sentence.

Get access and deploy

Open the source: https://github.com/Remade-With-Rust/mata-oem-sidecar.
Add the crate (crates.io when published, otherwise git):
```
cargo add mata_oem_sidecar
```
Git pin: cargo add --git https://github.com/Remade-With-Rust/mata-oem-sidecar.git
Prove the pin with cargo check before the next agent prompt can swap it for a C or cloud default.
Read the MATA Learn note: /learn/mata-oem-sidecar-hardware-joins-disco/.
When the binary is ready to place, ship toward the Disco Party and the Freedom Guide.