diff --git a/_posts/2026-04-15-rubygems-org-has-a-public-roadmap.md b/_posts/2026-04-15-rubygems-org-has-a-public-roadmap.md
new file mode 100644
index 0000000..084cb8a
--- /dev/null
+++ b/_posts/2026-04-15-rubygems-org-has-a-public-roadmap.md
@@ -0,0 +1,16 @@
+---
+title: "rubygems.org has a public roadmap"
+layout: post
+author: Colby Swandale
+author_email: colby@rubygems.org
+---
+
+[rubygems.org](https://rubygems.org) has been a busy project. This past year we shipped formal policies for the first time in the registry's history, launched the Organizations private beta, and made some meaningful security improvements to how gems get validated and how compromised passwords get caught. A lot of that work happened quietly. If you wanted to know where things were headed, you had to catch the right conference talk or subscribe to the right newsletter, and even then you'd only get pieces. The roadmap puts it in one place.
+
+The roadmap covers work at different stages, from Organizations moving toward general availability to longer-horizon work on security tooling, gem archival, and acceptable use policies. The full list is on [the board](https://github.com/orgs/rubygems/projects/21).
+
+As the registry has grown, the stakes of each change have grown with it. Those changes ripple out to gem authors, client maintainers, and anyone who depends on the ecosystem being stable. Getting that right requires input from people outside the core team. Contributors from both the RubyGems client team and Shopify are already working with us on making native gems a better experience for the Ruby community. A public roadmap makes more of that possible.
+
+If you see something on the [roadmap](https://github.com/orgs/rubygems/projects/21) that affects your work, leave a comment on the issue. If something's missing that you think should be there, [open an issue](https://github.com/rubygems/roadmap/issues/new).
+
+The roadmap is public now. We're curious what the community does with it.