WECORE HPC
Available on request
Managed HPC for your organization or customers
Commission a complete HPC platform for your teams or customers. WECORE Cloud deploys and operates it on infrastructure you own or lease.
Three deployment models
- On-Premise One infrastructure location you own or lease
- Hosted management A hosted panel for capacity you operate
- Hybrid Manage infrastructure you control across locations
HPC console preview with sample data; the cluster, jobs and states are illustrative only.
One HPC platform for your organization or customers
Use it for internal research and engineering teams, or offer managed HPC to customers on compute capacity you control.
For organizations
Give researchers and engineers a governed HPC environment without asking your team to assemble and maintain the software stack.
For service providers
Turn infrastructure you control into an HPC service with a catalog, access controls, usage records, and customer-ready operations.
What your users can do
Submit and track computational jobs from the browser, use preconfigured scientific software, and retrieve results through one workspace.
What your infrastructure team gets
Defined compute pools, storage, networking, access policies, quotas, cost estimates, platform status and usage records, and lifecycle controls.
How WECORE deploys and operates it
We design the platform with your team, deploy it on infrastructure you own or lease, validate it, and provide ongoing operations. If you don't run a cloud foundation yet, the engagement can include deploying the open-source infrastructure layer the platform runs on.
A governed HPC service
through one Cloud Panel workflow.
Your organization gets a defined platform, current operational status, and a ready software stack in every deployment model.
Guided platform definition
The deployment plan captures the approved HPC template, runtime-ready image, node sizes, network, SSH access, and storage. Your infrastructure team can review resource quota and estimated infrastructure cost before approving a platform request.
Compare deployment models →
Multi-pool compute
The deployment can separate compute nodes into pools for general-purpose, high-memory, or other workload-specific needs, with an approved size, node count, and disk policy for each pool.
Talk to our team →
Software ready with the platform
Job submission and queue tracking are part of the platform's web panel, and preconfigured scientific software ships in the platform image. Users can access them after setup is complete.
Request a briefing →
What the deployment request captures
Project teams request complete platforms when they need them: one deployment request captures the controller, login nodes, compute pools, shared storage, and user access. The platform recommends node sizes and counts, your infrastructure team approves quota and estimated cost, usage is metered, and expired platforms are reclaimed automatically.
One platform, three deployment models.
Use the same HPC platform in any model, based on where workloads run and data stays.
| On-Premise At one location | Hosted management Through a hosted panel | Hybrid Across controlled locations | |
|---|---|---|---|
| Infrastructure | One location you own or lease | Capacity you operate through a hosted panel | Two or more locations you own, lease, or operate |
| Platform management | WECORE deploys and operates on your infrastructure | The panel, usage reporting, and service management are hosted for you | One hosted panel manages every location |
| Available capacity | Capacity at the On-Premise location | Capacity connected to the hosted panel | Capacity across the locations you control |
| Where data stays | At the On-Premise location | At the connected infrastructure location | At the location chosen for each HPC platform |
| Pricing | Tailored quote for one location | Based on connected capacity and hosted services | Tailored quote across your locations |
| Best for | One location and strict data-location requirements | Service providers that want hosted management for their capacity | Organizations operating infrastructure in more than one location |
Same workload scheduler
Browser job portal + preconfigured software
One management workflow
Platform capabilities
Every deployment combines the same user capabilities with defined controls for your infrastructure team.
HPC platform topology
WECORE deploys controller, login, and compute nodes as one coordinated platform. Authorized users get SSH access and can submit computational jobs with standard Slurm commands or through the browser.
Predefined resource sizes
Your infrastructure team approves capacity for controller, login, and compute nodes through platform templates and predefined HPC node sizes, without hand-building each environment.
Purpose-built compute pools
The deployment can include high-memory, general-purpose, or other workload-specific pools so each workload is routed to the right compute pool. GPU node sizes can be included per deployment where the platform image supports them.
Monitor and manage the job queue
Authorized users can view active jobs, partitions, status, run times, users, and node counts. The queue updates automatically, and permitted users can cancel jobs.
Submit and track jobs in the browser
Users can submit, track, and cancel jobs directly in the browser.
Capacity governance & lifecycle
Approved quotas and expiry policies govern each platform. WECORE records platform status and coordinates lifecycle actions under the agreed operating model.
FAQ
Managed HPC questions, answered
What the engagement covers, what users get, and where the boundaries are
We design the platform with your team, deploy it on infrastructure you own or lease, and validate it together. After setup is complete, authorized users sign in and submit jobs from the browser or over SSH: the queue, partitions, and accounts are already configured.
WECORE deploys the platform and operates the agreed responsibilities, monitoring platform health, coordinating upgrades, and working incidents within the responsibility split agreed for your deployment. Your infrastructure team owns capacity, access policy, and quotas; your researchers own their jobs and data. Panel access is role-based, and administrative actions are recorded in tamper-evident audit records. Hardware and facility stay with the infrastructure owner unless included separately; the pricing page carries the full responsibility and access model.
The platform image ships with preconfigured scientific software, and the application catalog can add tested applications as a managed service on the same cluster. What your deployment includes is agreed during solution design.
You bring hardware you own or lease: servers, storage, and network. If you don't run a cloud foundation yet, the engagement can include deploying the open-source infrastructure layer the platform runs on.
You can: this platform exists for teams that don't want to own that layer. What the engagement adds to a self-assembled stack is the operated product around the scheduler: platform templates and approved node sizes, browser job submission and tracking beside standard Slurm commands, preconfigured scientific software in the platform image, usage records against the deployment rate card, and agreed operations, on the same platform that runs your Kubernetes, applications, and research services.
Yes. Organizations deploy it for their own researchers and engineers; service providers offer managed HPC to their customers on capacity they control. The deployment model (On-Premise, through WECORE Hub, or hybrid) is chosen during solution design.
Further reading Cloud HPC: a guide to high-performance computing in the cloud era
Match the right model
We help you choose templates, node sizes, compute pools, and access rules that fit your workload.
Talk to our team