OneSciencePlace is available today as a fully managed service. An open-source distribution for institutional self-hosting is planned.

Managed Deployment

In a managed deployment, the OSP team works with your project or institution to configure, deploy, and operate the platform on your behalf. You retain full control over your infrastructure, applications, content, and users. OSP operates in userspace. The OSP team handles the platform layer.

Who this fits

  • Campus computing groups requiring an HPC portal
  • Researchers aspiring to build science gateways for their community
  • Multi-institutional projects or centers with compute, data, and dissemination needs
  • Education and training initiatives requiring prebuilt application environments
  • Faculty labs or centers needing a portal without dedicated engineering staff

What a deployment can include

  • Application onboarding and configuration
  • Compute and storage integration
  • Identity and access setup, including federated authentication
  • Data sharing and publishing workflows
  • Site structure, branding, and content setup
  • Ongoing platform support and updates

What We Each Bring

Each deployment is a collaboration between the OSP team and your project or institution.

OSP team provides:

  • The OSP software stack, hosted and operated by the OSP team
  • Platform deployment, updates, and security patching
  • System integration and core configuration
  • Identity and access setup
  • Technical guidance on application onboarding
  • Issue resolution for the platform layer

Your project or institution provides:

  • Research use cases and priorities
  • Application-specific requirements
  • Local policy and compliance decisions
  • Project content and user community management

Compute and storage

Compute and storage resources can be provided by your institution or requested from the OSP team. Resources may be on-premises, cloud-based, or a combination of both.

Supported compute environments include Slurm-based HPC clusters and standalone Linux hosts.  OSP can integrate your existing HPC clusters, cloud instances, or ACCESS/NAIRR allocations. If you need compute or storage provisioned as part of your deployment, we can discuss options.

Storage can be POSIX file systems or S3-compatible object storage, on-premises or in the cloud.

Roles across other areas can also be adjusted based on your team's capacity and preferences. Some projects prefer more local control; others prefer a more fully supported model.

How Engagement Starts

Engagement typically begins with a discussion of your use case, followed by a scoped deployment plan based on your project goals, systems, and support needs. There is no fixed starting configuration; deployments are scoped to fit.

Contact the OSP team to discuss your use case → osp@oarc.ucla.edu

Pricing

Pricing is scoped by project. A small lab portal and a national science gateway have very different requirements. Cost depends on deployment scope, systems integration, and the level of ongoing support required. Contact us to discuss your use case and pricing.

Get in touch to discuss scope and pricing

Open-Source Distribution

An open-source distribution for institutional self-hosting is planned. When available, it will enable institutions to deploy and operate OSP on their own infrastructure. Managed deployment is the current production model.

Learn more about the open-source plan 

Frequently Asked Questions

Is OSP available now? Yes. OSP is available today as a fully managed service. Contact us to start a conversation about your use case.

Is OSP open source? OSP is built on open-source software and open standards. A unified open-source distribution for self-hosting is planned. Core components are already available in public repositories.

Can I self-host OSP? Not yet. Self-hosting will be enabled by the planned open-source distribution. Managed deployment is the current production model.

Who is OSP for? OSP is designed for HPC portals, science gateways, education instruction, faculty labs, and projects, i.e., from a single PI lab to national-scale systems and communities.

What compute systems does OSP integrate with? OSP integrates with Slurm-based HPC clusters and standalone Linux hosts, on-premises or in the cloud. National resources, including ACCESS and NAIRR allocations, can also be integrated. Multiple systems per deployment are supported.

Can I bring my own compute and storage? Yes. If you have existing HPC clusters, cloud instances, storage systems, or national resource allocations, OSP can integrate with them directly. Compute and storage can also be requested from the OSP team if needed.

How does engagement start? With a conversation. Contact the OSP team to discuss your use case, and we will work with you to scope a deployment plan. Contact the OSP team

Let's explore how OSP fits your use case. Schedule a demo