Our collaborative service model

Our collaborative 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.

Shared responsibility model

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.

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.

Service Level Objectives

Cost model#

There are two types of costs associated with our service. We treat each of these separately in order to be transparent about where community costs are coming from. They will be covered as either two separate invoices, or two different line items on the same invoice.

Staff costs cover all of the human time that goes into managing, supporting, developing, and improving our hub service. See Usecases and prices for details, and the Cost Model section in our Team Compass for our staffing cost model.

Cloud costs cover the cost we pay a cloud provider for the infrastructure that powers your service. This is either on a dedicated cloud cluster, or on cluster that you share with other communities. See Estimate cloud costs for a guide on how to estimate your community’s cloud costs.

Comparison to similar services#

A comparison with similar kinds of services, to help you understand your options and the considerations you may want to take.

Comparison to similar services