Open infrastructure for research and education

We’re a non-profit that believes communities shouldn’t choose between managing their own servers and vendor lock-in. We operate shared cloud infrastructure so your community can focus on its work, not its servers, and we invest back into the open source tools that make it possible.

See how it works Join our network

Each community gets a hub with the tools, data, and resources for their workflows

Environment selector interface — Resource and user management

JupyterLab interface. — Interactive interfaces

MyST Markdown interface. — Computational knowledge bases

Membership in our network provides access to our hub platform so your community can create and share knowledge with open infrastructure.

Communities

>90

Active users

>6500

Countries

>15

Upstream PRs contributed

>2000

Learn how membership works

What is a community hub?

A hub is a cloud environment where your community can access shared tools, data, and computational resources.

See how communities use their hubs

How we are different

Non-profit, no vendor lock-in

As a non-profit, our only obligation is to the research and education communities we serve. Your Right to Replicate means you can take your infrastructure anywhere, with or without us.

Open source collaboration

We listen to researchers and educators, then work with upstream open source projects on solutions that benefit the whole ecosystem, not just our members.

Cross-community learning

Our network connects communities across disciplines. When geoscientists and biologists face similar challenges, we bridge the gap through shared tools and practices.

Recent work

We share our progress and impact on our blog.

Better resource management with compute quotas and usage dashboards

Compute quotas and usage dashboards are now available on 2i2c hubs 🚀 This allows hub admins to cap the amount of compute resource a user can access over a given time period, as well as providing end-users with updates on their current usage.

Migrating from one ingress controller to another

What we learned # Migrating from one ingress controller to another is not a trivial task! Context # The news that the best-effort maintenance of the Ingress NGINX Controller would end in the first quarter of 2026 sparked a considerable amount of discussion among the community about what the best replacement for this controller is.

Rebuilding Project Pythia’s gallery on reusable MyST tooling

At the 2026 Pythia Cookoff at NCAR, we spent some hackathon time rebuilding the Project Pythia Cookbook Gallery and blog on shared MyST Engine tooling, replacing the one-off custom scripts Pythia had been using before.

View all blog posts

Learn more or get started

See membership options

Subscribe to our newsletter for monthly updates on open infrastructure.