About the JupyterHub Service¶
The Managed JupyterHubs Service is an open, scalable, sustainable cloud service for interactive computing environments in research and education. It follows a “DevOps as a Service” model where communities in research and education can pay for managed cloud infrastructure that runs on an entirely open source stack, and give you the right to replicate your infrastructure.
It is run by 2i2c, a non-profit organization that develops and operates interactive computing infrastructure for research and education. 2i2c values transparency and community driven infrastructure. The sections below describe the Managed JupyterHub Service, its strategy and goals, as well as information about its major features and pricing.
Get a hub for your community
If you’re interested in working with 2i2c to get a hub for your own community, please send us an email and we’d be happy to discuss options with you.
The service is currently in an alpha phase, and may evolve as we learn more about how to best serve our target communities.
Who is a 2i2c JupyterHub for?¶
2i2c JupyterHubs are designed for communities in research and education who want the following things:
Access to the latest technology in Jupyter and interactive computing for collaborative and scalable data science running in the cloud.
To utilize open source, community-driven tools and standards.
To use infrastructure that they could take control of themselves, and that gives the user the Right to Replicate.
To use infrastructure that is designed by and for individuals in research and education.
To support infrastructure from a non-profit organization that is committed to communities in research, education, and open source.
What will 2i2c provide?¶
2i2c will operate and manage a 2i2c JupyterHub deployment for use by you and your community, accessible via a web URL. 2i2c will handle the design, configuration, development, and ongoing operation of the hub infrastructure.
The following sections describe several common activities that the 2i2c team will perform as a part of your managed JupyterHub.
Requirement definitions and technical scoping
Initial deployment on cloud infrastructure
Ongoing development of hub infrastructure¶
Develop customizations needed for the hub deployment
Updates to the hub software environment
Upgrades and optimizations to 2i2c Hub infrastructure
Ongoing operation of hub infrastructure¶
Debug infrastructure issues, with expedited turnaround time for responses
Providing “escalation support” before / during / after the outages and downtime
Provide support to hub admins to facilitate their use of the infrastructure
Development of open source software that underlie the 2i2c Hubs¶
Improvements to the Jupyter ecosystem of tools and standards for interactive computing.
New features and bug fixes for the tools that are used in a 2i2c Hub
Your Right to replicate¶
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 Customer Right to Replicate. This states the following:
The Right to Replicate gives customers the right to replicate their infrastructure in its entirety elsewhere, with or without 2i2c.
We believe that following this principle will lead to a more equitable and more productive ecosystem for research and education in the cloud. It also 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.
What 2i2c provides¶
Each Hub is a collaboration between 2i2c team members, and representatives from the community that uses the hub. They require a variety of expertise to design, deploy, maintain, and use.
Generally speaking, 2i2c provides development and operation of a 2i2c JupyterHub, as well as support for questions and issues that arise with the hub infrastructure. It does this in collaboration with leaders from the community for a particular hub (usually, these leaders have “administrative” rights on a hub with more priveleges for user control etc).
Support options: see Get support.
Will 2i2c keep information about a hub’s users?¶
2i2c will not collect user data for any purpose. 2i2c will have access to all of the information that is inside a hub (which it requires in order to debug problems and and assist with upgrades), however we will not retain any of this data or move it outside of the hub, and will not retain it once the hub is shut down (except in order to transfer data to you at your request).
Funding open source¶
Everything that 2i2c deploys is open source and community-driven projects. We prioritize using multi-stakeholder projects that are well-supported by a diverse community of contributors. The resources that we receive to run 2i2c JupyterHubs thus also go towards making open-source improvements in these communities so that others may benefit from them. We see this as an opportunity to solve two problems with one stream of funding: support research and education, and support open source communities in the Jupyter ecosystem and beyond.
Replicate a 2i2c Hub¶
2i2c JupyterHubs are designed to use entirely open-source tools that work in other contexts. We are a non-profit organization that believes that using tools that are interoperable, open-source, and owned by the community will empower research and education and make it more equitable and inclusive. For this reason we are committed to deploying open source infrastructure that you can take elsewhere and deploy on your own.
Check out Migrate off of a JupyterHub for information about replicating a 2i2c JupyterHub.