Meta didn’t just release a new design system. It open-sourced the one it’s been dogfooding for eight years. Astryx, now available in beta under an MIT license, is the company’s largest and most-used internal UI framework, and it ships with a specific opinion: stop choosing between a system that makes your app look like everyone else’s and a frankenstack of copy-pasted components that you have to babysit.

The package lands with over 160 accessible React components, seven pre-built themes, dark mode, templates, and a CLI. It runs on React 19 and StyleX, but Meta made a point of removing friction. You import pre-built CSS and typed React components. There’s no build plugin to configure and no new styling library to swallow. If you want to override styles, you can do it with Tailwind, CSS modules, or plain old classNames. If you need to truly own a component, the “swizzle” command ejects its full source into your project.

The philosophical split is what makes Astryx interesting. The system owns behavior, accessibility, and quality. Themes own the look, via CSS custom property overrides at the token level — color, type, radius, motion. A designer can retheme the entire system without forking or wrapping source. Meta calls its approach “guidance over enforcement,” which is a polite way of saying they’re not going to force your app to look like Facebook.

But the real wrinkle is the AI-native framing. The team says the API, docs, conventions, and CLI were designed together so that a person and an AI assistant build from the same reference. The CLI can surface machine-readable docs over MCP, scaffold templates, generate themes, and run migration codemods. Meta claims every change that made Astryx easier for AI also made it easier for people. Whether that symmetry holds up when agents start generating production interfaces is the experiment every team adopting this will run.