As a non-profit, we run shared, open infrastructure for research and education communities. Each member community gets a hub: a flexible cloud workspace with its own software, data, and compute. Membership pools resources so that one team can operate every hub and improve the open source tools you depend on.

That work spans four areas (informally called “DOCS”): Developing software your community needs, Operating infrastructure, Connecting & advising communities with information and resources, and Stewarding upstream open source projects. These fuel the cycle you see below:

Membership also connects you with a network of member communities that support one another: a problem solved for one becomes an improvement shared by all. Members co-fund and steer our open roadmap. Learn more about our mission or explore the platform.

Your Right to Replicate keeps your configuration transparent and portable, so you’re never locked in. All our engineering work is open source with licensing that protects communities, and we contribute upstream to the projects we depend on. Our hubs are secure by default, with isolated user environments and continuous monitoring.

See our public roadmap for current priorities, or read more about our open practices.

Membership is a fixed annual amount that supports our mission and key member services. Where we run infrastructure for members, we add bounded usage costs to cover the extra time and cloud fees.

Base membership. A fixed annual fee at one of two tiers. Both give you the benefits of all four areas of our work. They differ in how much time and strategic attention you get.

• General: For communities that want to benefit from our core shared platform and team. We’ll operate your hub, support your community, and steward open source projects on your behalf. General membership doesn’t cover the cost of new development, but you’ll still benefit from the work that Premier members and directed engagements fund.
• Premier: For communities that want to support open source and our mission, and want deeper engagement with our team and member network. Includes more service hours across all four areas and a deeper strategic relationship: optional monthly strategy sessions, quarterly roadmap reviews, and collaborative work time with our team.

You don’t need a hub to be a member: members without infrastructure pay only the annual fee, and some direct their support toward the open source projects their communities depend on. Others join an existing community’s hub and share its operating costs instead of running their own.

See the service description for the services included with each tier.

Directed engagements. Fund extra dedicated work in any of the four areas described above. For example, you can support development from our roadmap, more complex infrastructure operations, or dedicated upstream stewardship time. Some organizations also fund larger project collaborations alongside membership. We’ll scope the work together and come up with a plan for invoicing and cost recovery.

Usage. A per-user fee that changes monthly based on who has used your hub. The rate levels off as your monthly users grow, and stops entirely above a certain size, so there’s a maximum monthly fee no matter how large your community gets.

Cloud. Bring your own cloud account and manage spending yourself (we’ll just need access to the infrastructure), or have us manage it and pass through your cloud costs with no usage-based markup. Either way, you can track cloud spend in dashboards, get alerts before it runs over, and read how cloud costs work and how to control them.

Getting started. The timeline is usually influenced by how quickly your community settles on what it needs. Most hubs are set up in a few days, once these decisions are made. Figuring out the needs is not trivial and might take a few weeks on its own, but we’ll guide you through the process.

• Get started