Two Weeks of Astryx: Thank You
A thank-you note after Astryx's first two weeks in the open.Two weeks ago, we did something that had been years in the making but still felt like stepping off a ledge. We took the design system we had quietly refined inside Meta for the better part of a decade, and we gave it to the world as Astryx: free, open, and ready for anyone to build with.
When you spend that long living inside a piece of software, you lose the ability to see it clearly. You know every rough edge and every compromise, and it becomes very hard to imagine that strangers on the other side of the world might look at it and feel the same excitement you felt on your best days building it. So in the quiet before launch, the honest question in the back of our minds was not "how big will this be." It was simply, "will anyone care?"
They did. And the way they showed up is the reason we're writing this. Not to talk about ourselves, but to say thank you.
What the response actually felt like
We could fill this post with charts, and there are a few numbers we're genuinely proud of. In its first two weeks, Astryx crossed 7,000 GitHub stars, and for a moment we did not see coming, it sat at #2 on GitHub's trending list across every repository on the platform. Close to 200,000 installs a week now flow through its packages, and more than 100,000 developers visit the docs each week to see what it can do. Those signals matter to us, especially this early, because they tell us the work is reaching real people.
But the numbers were never the part that moved us. What moved us was the shape of the response. It was a developer who rebuilt his company's entire website on Astryx within days of launch and then came back to dig into the internals with us, just because he wanted to understand how it worked. It was the engineers in Japan, Korea, and China who, within days and entirely on their own initiative, wrote careful, source-level breakdowns of how our components and tooling fit together, reading our code more closely than we sometimes read it ourselves. It was the person who was so genuinely delighted on day one that we ended up shipping him a little 3D-printed Astryx logo, because that kind of enthusiasm deserves something you can hold.
And it was one early adopter who tried building with Astryx alongside an AI coding agent and told us, almost in passing, that it worked with "literally no issues at all." That single sentence meant more to us than any metric, because it was exactly the thing we had bet the whole project on and were most afraid we hadn't gotten right.
Why we built it this way
We open sourced Astryx on a conviction: that the way people build software is changing, and that the interfaces generated in this new era of AI-assisted "vibe coding" too often look generic and untrustworthy. Not because the tools are bad, but because the AI has no cohesive, production-grade design system to reach for. We wanted to hand both developers and their agents something better, a complete, accessible, deeply customizable component library, built on StyleX and designed from the ground up so that an agent can read it, understand it, and compose with it reliably.
That was the bet, and honestly we won't know for a long time whether it fully pays off. But the early conversation gave us reason to hope. Across every corner of the community, the discussion kept returning to the same things we had cared most about: the tooling, the agent-first architecture, the idea that a design system could be a first-class citizen in how AI writes code. People who have thought deeply about this space engaged seriously and generously, and a few of them, Dominic Nguyen, who co-founded Storybook, along with Sebastien Lorber and Yangshun Tay, took real time to examine what we'd made and share it with their own audiences. When people you respect look closely at your work and decide it's worth their reputation to amplify, it lands differently than any dashboard ever could.
Thank you
None of this happened by accident, and none of it happened alone. Long before the world saw Astryx, it took an enormous amount of unglamorous work from people across Meta: colleagues who fixed the last hundred bugs, who argued with us about defaults, who cleaned up the code so it would be something we'd be proud to put our name on, and who believed in the idea when it was still just an idea. To every one of them, thank you. This was yours before it was anyone else's.
And to the community that welcomed Astryx into the open, the developers who filed issues and opened pull requests, who asked hard questions in Discord, who wrote about it, argued about it, and started bending it to their own brands and needs: thank you for taking a chance on something new. Open source only works because people decide to care, and you decided to care. We don't take that lightly.
We are, genuinely, at the very beginning. There is a long road ahead, with more components to harden, a theme ecosystem we want to grow together, and deeper, more reliable integration with the AI tools developers are already living in. We'd love for you to walk that road with us, to try Astryx, tell us where it breaks, and help shape what it becomes.
Come build with us and follow the journey on Instagram · Threads · Facebook · X – all @astryxdesign
Appendix
- X – launch tweet – @Astryxdesign: 1,058 likes/reactions · 17 comments · 120 (+1,683 bookmarks) shares/reposts · 301.6K views
- Facebook – Meta Open Source – Meta Open Source: 206 likes/reactions · 40 comments · 30 shares/reposts
- Facebook – Meta for Developers – Meta for Developers: 101 likes/reactions · 30 comments · 10 shares/reposts
- Facebook – Life at Meta – Life at Meta: ~319 likes/reactions · 82 comments · 22 shares/reposts
- Facebook – Astryx – Astryx from Meta: 16 likes/reactions · 1 comments · 21 shares/reposts
- LinkedIn – Meta – Meta (official): 259 likes/reactions · 54 comments
CommunityAIOpen sourceDesign systems
