January 2026 update: Leaning more into open collaboration
We've got a new e-mail look! We're experimenting with the Buttondown newsletter service because it feels more reader- and author-friendly than Mailchimp. Please give us feedback if you like it (or don't)!
The last two months have been busy for 2i2c - we tend to "zoom out" at the end of each year, re-assess where we are financially and strategically, and decide on any major adjustments to make for the next year. We wrapped up the year focusing on infrastructure reliability and transparency, and we're hopeful that this gives us extra capacity to focus on the more "human" parts of our member service (more on that below). 2026 is going to be a pivotal year in learning whether our membership model is fundamentally sustainable, so we are learning and improving as fast as we can! We're excited to learn more into co-creation and collaboration with our member communities, but I'll let you read more about that below...
Our 2026 strategy update
In January we published our 2026 strategy update: we’re leaning harder into collaboration and shared development with member communities, and treating managed infrastructure as "necessary, but not sufficient". (as a teaser - we've recently made our roadmap public)
This strategy is informed by deeper partnerships we’ve built with communities like NASA VEDA and Development Seed, where co-creating new capabilities alongside managed infrastructure has made a real difference.
Highlights from our blog
Service enhancements: We improved community hub reliability in Q4 2025, including better incident response and a new status page (status.2i2c.org) so communities can see real-time hub status. Blog post
Service enhancements: We shipped near-instant home directory usage + quota limit metrics, making storage monitoring more responsive for hub admins and easier to use in upstream JupyterHub dashboards. Blog post
Service enhancements: We enabled CloudBank to safely manage their own cluster infrastructure by isolating Terraform state, unlocking more self-service without risking other communities. Blog post
Upstream impact: We helped ship new MyST/Jupyter Book releases, focusing on bugfixes, stability, and UX polish across mystmd, myst-theme, and Jupyter Book. Blog post
Highlights from communities
Collaborator: We wrote up a recap of a workshop hosted by STRUDEL - 2i2c hosted a hub and did some environment development work to give their users access to design infrastructure and resources for the workshop. Blog post
Open source: Jupyter Book released 2.1.0 and 2.1.1. Release notes
Open source:The MyST Document Engine (mystmd) released 1.6.7, 1.7.1, and 1.8.0. Release notes
Open source: The MyST Theme released 1.0.1, 1.1.0, and 1.1.1. Release notes
Open source: The Zero to JupyterHub Helm chart released version 4.3.2. Release notes
Shout-outs
- Thanks to CloudBank and the BIDS team (UC Berkeley) for collaborating on safer self-service operations.
- Thanks to NASA VEDA for supporting monitoring and alerting improvements for hub administrators.
- Thanks to Project Pythia for supporting additional foundational work in the Jupyter Book / MyST ecosystem that led to the nice jupyter book releases page we linked to above.
THANKS FOR READING ❤️
-- Chris and the 2i2c Team
