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 you can focus on discovery, and we contribute to the open source tools that make it possible.

How our model 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
>2000
  • Nasa logo
  • Smithsonian logo
  • Howard Hughes Medical Institute logo
  • NCAS logo
  • Pangeo logo
  • University of toronto logo
  • Columbia University logo

What is a community hub?

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

Powered by and .
Custom environments
Choose from community-maintained stacks or bring your own.
Managed access
Community leaders control who can use the hub.
Scalable compute
From laptops to GPUs, sized for your workflows.

What makes us different

Non-profit, no vendor lock-in

We exist to serve research and education communities, not shareholders. 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 everyone — 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.

Announcing our public roadmap for open development

Announcing our public roadmap for open development

At the core of 2i2c’s service is a commitment to doing our work in a way that follows open principles and practices. We commit to doing all of our work in the open and only managing and developing open infrastructure.

Introducing Jupyter Book 2 at FOSDEM 2026

Introducing Jupyter Book 2 at FOSDEM 2026

Our teammate Angus Hollands gave a talk at FOSDEM 2026: Introducing Jupyter Book 2. The talk shares why the Jupyter Book 2 and MyST stack was rebuilt, and how it supports open, reusable computational publishing workflows.

Better sharing UX with nbgitpuller and contextual error handling

Better sharing UX with nbgitpuller and contextual error handling

TL;DR # nbgitpuller now has improved UX context-aware error handling. Try out the pre-release version 1.3.0b1 and let us know what you think by opening an issue or via the feedback form below 🚀

Learn more or get started