Overview of our service model

Overview of our service model#

Here we provide a high-level overview of our Managed JupyterHub Service and the major teams, processes, and expectations for both 2i2c and the partner communities we work with.

Want to partner with us?

If you’re interested in setting up a service for your community, click the button below to send us an email.

Send us an email.

Our shared responsibility model#

Our hub service is a collaboration between 2i2c and one or more communities. We break down the responsibilities that must be carried out in order to successfully run a service. We can then assign or share these responsibilities with partner communities according to their needs and interests.

Your Right to Replicate your infrastructure#

A core principle of 2i2c is to build and manage technology that is controlled by the community that uses it. One way in which we adhere to this principle is by respecting the Community Right to Replicate. This states the following:

The Right to Replicate gives communities the right to replicate their infrastructure in its entirety elsewhere, with or without 2i2c.

Following this principle leads to a more equitable and more productive ecosystem for research and education in the cloud, and helps avoid many of the potential downsides of relying on a cloud vendor for infrastructure. Read the Right to Replicate documentation for more information about what this means.

Transparent infrastructure and operations#

All configuration and deployment code for 2i2c JupyterHubs is publicly available in the 2i2c infrastructure/ repository. This repository contains both deployment scripts and documentation explaining how the infrastructure works.

This transparency serves several purposes:

  • It follows our commitment to Open Practices and Open Technology

  • It supports the Right to Replicate, giving communities full visibility into how their infrastructure is configured

  • It allows communities to understand exactly how their hub is deployed and managed

  • It provides a reference for communities that may wish to manage similar infrastructure themselves

The infrastructure repository is intended for advanced users and is provided for transparency. For day-to-day hub management, use the guides in this documentation rather than modifying infrastructure code directly.

To learn more about how the infrastructure works, see the infrastructure documentation.

Service Level Objectives#

Our Service Level Objectives define our goals in running the service for each partner community. This includes goals like service uptime and support responsiveness.

Contents