Learn/Disco Party

The MATA OEM Sidecar — How Hardware Joins The Disco Party

The OEM sidecar is how hardware joins the Disco Party: one binary on the OS you already ship, with mID, an honest catalog, and optional FFAI.

Signed by M·
Chrome motorcycle parked on an open road with a long stretch of asphalt behind it

🪩 The Disco Party is MATA's distributed cloud.

The OEM sidecar is how a hardware maker joins the Disco Party without throwing away the operating system they already ship. mata-oem-sidecar is one binary you drop beside your existing image: mID for identity, an honest catalog of what the machine will provide, and optional FFAI if the SKU has a camera or a mic worth running locally. No forked OS. No "flash this custom distro or you are not invited." The maker keeps the board support they already paid for. The sidecar is the doorway onto the mesh.

That is the only OEM story that ships. Demanding a clean-room OS is how you get a press release and zero factories. The Disco Party needs volume: NAS boxes, mini-PCs, home computers, the quiet machines in a shop. The OEM sidecar is the volume path. What Is A Distributed Cloud is the architecture. This article is the SKU.

Why The OEM Sidecar Is The Honest Disco Party On-Ramp

Makers already have an OS, an updater, a support tree, and a lawyer who likes that tree. A Disco Party that starts with "rewrite your image" starts with no partners. The OEM sidecar respects that constraint. One binary. Declare what you offer — storage, CPU, bandwidth, optional on-device AI. Sign it. Let the mesh verify with mID. Owners adopt the machine with a grant, the same adoption story as a chip, at appliance scale.

Trust is the device identity in the sidecar. Security is the catalog that does not lie about sensors and the encryption on anything those sensors produce. Incentive is the payout the owner can enable so a shop NAS earns while it sits. Those are the only three Digital Freedom primitives. The OEM sidecar maps all three onto a box that still boots the vendor kernel. The NIST Secure Software Development Framework wants a reviewable component you can add without boiling the ocean. A sidecar is that component.

The Electronic Frontier Foundation has the file on appliances that quietly enrolled in a vendor cloud. The OEM sidecar enrolls in a mesh the owner controls. The Disco Party is that mesh.

What The OEM Sidecar Puts On A Disco Party Machine

mata-oem-sidecar is not a second desktop and not a container host you have to staff. It is the disco client for hardware: identity, catalog, optional FFAI. Sign in with Sovereign ID is the same mID verify, now sitting next to a manufacturer's init system.

mID In The OEM Sidecar — No OAuth On A NAS

The sidecar verifies tokens locally. No MAU fee. No client ID the maker has to renew with a broker. A Disco Party node that cannot name itself cannot get paid and cannot be revoked. mID is the name. The NIST Zero Trust Architecture applies to appliances. A default password on the sticker does not.

An Honest Catalog Is The OEM Sidecar's Product Surface

The catalog says what the box will do: how much disk, whether a camera exists, whether FFAI is compiled in. Honest means the owner sees the same list the mesh sees. A Disco Party that advertises a GPU the SKU does not have is a fraud. The Federal Trade Commission already knows how to spell that. The OEM sidecar makes the catalog a signed document, not a marketing PDF.

Optional FFAI — Local AI Without A Vendor Brain

FFAI is the house AI layer: OCR, ASR, detection, on-device. The OEM sidecar can ship it or not. A camera SKU that wants local faces without a cloud API turns it on. A dumb NAS leaves it off. The Disco Party does not require a model to join. It requires a grant. The Importance of Remade With Rust is why FFAI is remade, not a Python wheel taped to a sidecar.

How Hardware Makers Keep Their OS And Still Join The Disco Party

Drop the binary. Start it from the existing service manager. Point owners at the Freedom Guide for the human half. Digital Freedom Era 3 is when shops and homes are the cloud. The OEM sidecar is the factory-shaped path into that era. Remade With Rust is the catalog of primitives the binary links.

The OEM Sidecar Does Not Fork Your Support Tree

You still ship the kernel you know. You still take the warranty call you know. The Disco Party is a process on that image. When something breaks, you still have a tree. That is the whole point. A remade OS is a different product. This is an OEM sidecar.

SpaceDB And Iroh Are The Storage And Transport Behind The Sidecar

SpaceDB is the local-first database. Iroh is the mesh. The OEM sidecar is the deliverable that turns those libraries into a box on a shelf. Deputy keeps the binary's graph remade. The Privacy Rights Clearinghouse is what you avoid by not standing up a maker cloud "to help customers sync."

Remade Primitives, Disco Party, Digital Freedom

mata-oem-sidecar, mID, SpaceDB, and optional FFAI are Remade-With-Rust primitives. They become a Disco Party when hardware makers drop one binary and owners adopt the box. They become Digital Freedom when Trust, Security, and Incentive — identity, encryption, payouts — ship in the carton. Start at the Disco Party and What Is Digital Freedom. Keep your OS. Ship the OEM sidecar.

The bridge that sidecar walks is Janus. Chip-side mesh is esp32 iroh. The identity it drops on the board is mID on the chip. Keys the owner holds, not the factory, are hardware you hold.