For organizations
Create one governed application service for laboratories, engineering groups, and teaching environments on infrastructure your organization controls.
Provide research and engineering teams with approved applications and reproducible execution without asking them or your infrastructure team to maintain every software stack.
Create one governed application service for laboratories, engineering groups, and teaching environments on infrastructure your organization controls.
Choose an available application, configure a simulation, submit and track the run, review logs and status, and retrieve the recorded results.
Control approved applications and versions, licensing integration, access, resource quotas, execution policies, data location, and run history.
We package and validate applications, deploy the service on your OpenStack infrastructure, integrate licenses where required, and provide ongoing operations.
Finite-volume CFD for incompressible, compressible, and multiphase flows, plus heat transfer between fluids and solids, parallelized with MPI across the cluster.
Classical molecular dynamics at scale (from atomistic to coarse-grained and mesoscale models) with the simulation space divided among MPI processes.
High-throughput biomolecular dynamics for proteins, lipids, and nucleic acids, with replica ensembles and multi-node MPI.
Electronic-structure modeling (geometry optimization, frequencies, and reaction pathways) using an organization-provided license.
Plane-wave DFT for electronic structure, band structures, and materials modeling, distributed among MPI processes and k-point groups.
Monte Carlo simulation of particles passing through matter for detector design, dosimetry, medical physics, and space research.
The CERN framework for analyzing petabyte-scale experimental datasets (histogramming, fitting, and columnar storage) with C++ and Python interfaces.
Large-scale scientific visualization with client–server rendering, so you post-process results next to the data instead of moving terabytes to a local workstation.
The Weather Research and Forecasting model for mesoscale numerical weather prediction and regional climate research at high resolution.
Industrial CFD and integrated simulation of heat transfer and related physical effects for product engineering, using the organization’s license on an HPC cluster.
They choose an available application from the software catalog. Its version and run method are defined before they configure the simulation.
They set inputs, node profile, core count, and a stop policy. The platform validates the request, checks quota, and projects cost before submission.
When they submit the request, WECORE prepares a compute cluster for the simulation, creates the files needed to run it, and sends the run to the workload scheduler.
Configuration, simulation IDs, status history, and available output are stored in one project record that they can revisit or use to create a new request.
For every application in the catalog, its version and run method are defined, so your infrastructure team knows exactly what is available.
Configuration, simulation IDs, status, and run history remain available after the cluster is released.
Inputs connect to project storage, and outputs are written back there or archived according to the request.
Review quota, node and core counts, runtime cap, storage, and projected cost before the simulation is submitted.
Each of these applications is curated in the catalog and is packaged and validated for your deployment when you commission it. You ask, and we reply within two working days; a short scoping conversation then defines the deployment: there is no self-service checkout, because every service is deployed and operated for a specific organization.
Marketplace runs on the WECORE HPC platform deployed beside it: each simulation gets its own managed compute cluster in your OpenStack project, created for the run and released when it completes. The engagement deploys both together, or adds Marketplace on top of your existing HPC platform engagement.
WECORE packages and validates the applications, deploys the service, and operates it: we monitor service health, coordinate upgrades, and work incidents within the responsibility split agreed for your deployment. Your infrastructure team owns the approved applications and versions, licenses, access, resource quotas, and data location; your researchers own their runs and results.
Open-source applications like OpenFOAM need no commercial license. Commercial applications (Gaussian and Ansys Fluent in today's catalog) run using an organization-provided license: your organization supplies the license, and we integrate it into the deployment.
In your OpenStack project, on infrastructure your organization owns or leases. Inputs connect to project storage, and outputs are written back there or archived according to the request; the run record (configuration, simulation IDs, status, and run history) remains available after the cluster is released.
Through a deployment engagement: WECORE deploys and operates the service for your organization, and rating and commercial terms are defined for the deployment. Each simulation shows quota and projected cost before it is submitted, and commercial-application licenses are supplied by your organization.
Tell us. The catalog is curated per deployment, so we evaluate the application you name (its packaging, execution model, and license) and confirm during scoping whether it can be integrated into your service.