Where OneSciencePlace fits
OneSciencePlace (OSP) supports a wide range of scientific, educational, and data-sharing scenarios — from institutional HPC portals and multi-institution science gateways to lab and instructional environments. Each deployment context below describes who it is for, what problem it solves, and how OSP addresses it.
HPC portal
- Deliver the full power of HPC clusters through an intuitive browser interface — no command line required
- Connect multiple compute systems through a single interface: local clusters, national HPC, cloud instances, and standalone servers — all accessible from one login without switching platforms
- Stream high-performance GUI tools (MATLAB, ANSYS, RStudio) directly to the browser via secure reverse-proxying
- Build custom launch interfaces for complex batch jobs using the no-code form builder — no custom development needed
- Configure the portal in user space — no root privileges required on the connected systems
- Manage interactive and batch job submission across one or more integrated clusters and clouds
- Maintain persistent research environments where data, software versions, and job configurations are ready to resume
For a comparison with Open OnDemand and other HPC portal platforms, see the Compare matrix.
Science gateway
- Provide centralized access to domain-relevant applications, data, and reproducible workflows
- Connect domain researchers to multiple national HPC resources through a single interface — no separate accounts or logins per system
- Enable community members to contribute and share domain-specific applications directly through the gateway
- Federate user access across institutions without requiring a shared identity provider
- Build unified, simplified interfaces for researchers using the no-code form builder
- Support cross-institutional collaboration with built-in provenance tracking for reproducible research
- Publish and cite community tools and datasets with FAIR-compliant publishing and persistent identifiers
Quakeworx is OneSciencePlace's flagship science gateway deployment. Read the case study →
Campus or research center portal
- Provide a unified institutional portal with institutional branding and federated authentication
- Deliver a centralized App Catalog of validated computational tools
- Connect multiple institutional compute resources — local clusters, cloud, and national systems — through a single managed interface
- Manage access controls across compute and storage resources from one interface
- Enable cross-lab and cross-college resource sharing without rebuilding infrastructure for each group
- Give individual departments private, branded workspaces while sharing underlying HPC clusters
Repository and publishing platform
- Publish datasets, articles, software, notebooks, and workflows in a customizable FAIR-compliant repository — for a single project or an entire institution
- Assign DOIs, Handles, or ARKs for permanent citation and reliable referencing
- Automate metadata capture — every time an app runs via OSP, job parameters, software versions, and input files are logged automatically
- Support flexible metadata schemas and configurable curation workflows
- Create verifiable, audit-ready records of the entire research lifecycle, from computation to publication
- Configure embargo periods and access restrictions to align with funding policies
Education and training portal
- Deliver curriculum-integrated applications (Jupyter, RStudio, Linux Desktop, and others) with persistent workspaces
- Simplify student onboarding through federated identity — students sign in with institutional credentials
- Support virtually any browser-deliverable Linux application, not just notebooks
- Integrate campus HPC and cloud resources under a single class allocation
- Scale seamlessly from a small workshop to a large course without additional configuration
Lab and project portal
- Host lab members, applications, publications, and private datasets in a single branded environment
- Publish research outputs, protocols, and applications as shareable, citable objects with DOIs
- Manage the lab environment through a streamlined interface — no dedicated IT support required
- Start small and expand as the lab grows: add users, applications, and storage over time
Moving beyond your current gateway, portal, or Jupyter setup
OneSciencePlace gives research communities a modern platform to grow beyond their current environment — whether migrating from a legacy gateway or expanding from a Jupyter-based setup, offering a sustainable, managed foundation without rebuilding infrastructure from scratch.
Many OneSciencePlace deployments start as consolidations or extensions of tools teams are already running. Each of these tools works well within its scope — research workflows simply tend to expand beyond what any single tool was built for. OneSciencePlace is composable, so most deployments adopt only the capabilities they need today and grow from there. You don't need to use every OSP capability, and you don't need to replace your existing tooling all at once.
- One platform serves multiple groups — no separate JupyterHub instances per lab or community to set up and maintain.
- Application types beyond notebooks: batch executables, VNC graphical apps, scripts.
- A no-code form builder for app UIs.
- App curation, job tracking, and FAIR publishing built in.
- A full Drupal CMS for documentation, news, and community pages — no separate site needed.
- Works entirely in user space — no root access or per-cluster installation required on the connected systems.
- Multi-system federation — span local clusters, national HPC, cloud, and standalone servers from one tenant.
- Granular per-tenant access controls across users, groups, and apps.
- Users can contribute their own apps where institutional policy allows — no waiting on systems staff for every new tool.
- A no-code form builder for batch app UIs.
- Integrated FAIR publishing and a full Drupal CMS — your portal is also your community website, no separate site needed.
- A configurable foundation with app curation, job tracking, sharing, and publishing already built in.
- Replace bespoke per-app code with reusable configuration — keep what's working, retire the maintenance burden.
- A web interface, per-user workspaces, job tracking, and access control — without requiring command-line access to the underlying systems.
For a complete platform comparison across these and others, see the Compare matrix.
Find the fit for your project
Talk with us about your scenario, or try the platform yourself in the pilot environment.