For research services that need to stay online, not just jobs that need to run

Scientific Application Hosting

Host scientific applications, databases, APIs and research platforms inside UPF infrastructure.

This service provides virtualized infrastructure for research groups that need to run persistent scientific services that do not fit the HPC batch model. It is designed for applications that need to stay online, such as research web portals, project databases, APIs, dashboards, containerized services and dedicated research environments.

Bring the scientific application; SCC provides the institutional infrastructure to host it.

Use this service when you need to:

Host a scientific web application.
Run a project database.
Deploy an API or backend service.
Publish a dashboard or data portal.
Run a containerized scientific service.
Maintain a project platform that must stay online.
Use a dedicated research environment with managed infrastructure.
Keep the service hosted inside UPF institutional infrastructure.

What can be hosted

Scientific web applications

Web applications developed by research groups, such as portals, analysis interfaces, internal tools or user-facing scientific services.

Project databases

Databases that support a research project, application or platform. Examples may include PostgreSQL, MySQL / MariaDB or MongoDB, subject to review.

APIs and backend services

APIs, backend services and integrations that support research workflows, data access or scientific applications.

Dashboards and data portals

Dashboards, reporting tools and data portals for visualizing results, project data or research outputs.

Containerized research services

Scientific applications packaged as containers that need to run in a stable institutional environment.

Dedicated research environments

Virtualized environments for projects that require more control than standard HPC or interactive sessions can provide.

Deployment models

The service is based on a system virtualization and can support different deployment models depending on the project requirements.

Virtual machines

Dedicated virtual servers for persistent services, web applications, databases and project environments.

Use when: The project needs a stable operating system environment, service persistence or managed virtual infrastructure.

Containers

Containerized services for portable and reproducible application deployments.

Use when: The application can be packaged as a container and benefits from a lightweight deployment model.

Docker, Apptainer or compatible container workflows may be considered depending on the project.

Kubernetes

Kubernetes-based deployments for more complex services, composed applications or platforms that need orchestration.

Use when: The project requires multiple services, scalability, service composition or container orchestration.

Kubernetes deployments require prior assessment and are not automatically the default option for every project.

HPC or Virtualization?

HPC and virtualization solve different problems. HPC is for workloads that are submitted, executed and completed. Virtualization is for services that need to remain available.

Need Recommended service
Run jobs that start, compute and finish HPC
Train models or run GPU workloads GPU Computing
Work interactively with notebooks, IDEs or graphical apps Visualization & Interactive Apps
Host a service that must stay online Virtualization & Scientific Application Hosting
Deploy a database, API or web application Virtualization & Scientific Application Hosting
Build a dashboard or data portal for users Virtualization & Scientific Application Hosting

Architecture overview

Research group Scientific application / database / API / dashboard
SCC virtualization platform · VMs · Containers · Kubernetes
UPF on-premise infrastructure Network · storage · backup · monitoring
Users access the service Web portal · API · internal tool

Shared responsibility

Scientific application hosting is a shared responsibility between SCC and the research group. SCC provides the infrastructure and technical guidance; the research group remains responsible for the scientific application and its functional requirements.

SCC can provide

  • Virtual infrastructure.
  • VM provisioning.
  • Network integration.
  • Base system support.
  • Storage integration when needed.
  • Backup options depending on the service.
  • Monitoring and availability guidance.
  • Advice on containers or Kubernetes deployment.
  • Security.

Research group is responsible for

  • Application code.
  • Scientific software logic.
  • Application-level configuration.
  • Data ownership.
  • User-facing content.
  • Application-specific updates.
  • Defining functional requirements.
  • Identifying scientific users and access needs.
  • Security.

Before requesting a hosted service

  • Define what the application does and who will use it.
  • Clarify whether the service must be internal, external or restricted to specific users.
  • Identify data storage and backup needs.
  • Identify security, privacy or sensitive data requirements.
  • Decide whether the workload is a persistent service or a batch computation.
  • Prepare information about software dependencies and expected resource needs.
  • Contact SCC before choosing between VM, container or Kubernetes deployment.

Need to host a scientific service?

Tell us what you want to deploy, who will use it, what data it needs and whether it must be available as a web service, database, API, dashboard or internal research platform. The SCC team can help identify the right deployment model.