Skip to main content

Getting Started

landing · Reviewed 2026-07-31

Rescale runs engineering simulation on cloud HPC. You pick software, input files, and hardware; Rescale provisions a cluster, runs the job, and returns results. Everything runs in the browser, with nothing to install.

Pick your path​

You want toStart here
Run a simulation nowYour first job — end to end in about 15 minutes
Understand the platform firstCore concepts
Set up an account or workspaceAccount setup
Work interactively in a GUIWorkstations
Drive it from codeREST API · CLI
Look up a termGlossary

The five things you'll do​

Run batch jobs. Submit a simulation to an HPC cluster Rescale provisions on demand. Choose the coretype, core count, software, and input files per run. This is the core of the platform: see jobs.

Work interactively. Launch a workstation (a cloud desktop with real GPU hardware) for CAD, meshing, model setup, and post-processing. Most people use one to look at results without downloading them.

Manage data. Upload inputs, keep outputs, and reuse data across runs. Five storage options, and Files & storage explains which to pick.

Chain work together. Workflows and DOE run one job many times over a parameter space, or connect multiple steps into a pipeline.

Administer and control cost. Budgets, usage dashboards, policies, and identity: see Administer.

What Rescale gives you​

  • 1,000+ engineering applications, with on-demand licensing for many, plus your own licenses and self-published software.
  • Hardware across AWS, Azure, Google Cloud, and Oracle Cloud — see hardware and coretypes.
  • No queue for capacity. Clusters are provisioned per job rather than shared, so your run starts when you submit it.
  • AI assistance grounded in your own engineering data — see Rescale Edison.

The three ideas worth learning early​

These are where new users most often get surprised.

A job is immutable once it runs. Its inputs and outputs are a fixed record. To iterate, duplicate the job rather than editing it. That is the intended workflow, not a limitation.

Hardware choice drives both cost and speed, non-obviously. More cores isn't always faster, and the cheapest coretype is rarely the cheapest run. See hardware.

Archiving is not deleting. Storage charges continue until files are permanently deleted from the trash, see the file lifecycle. This is the single most common billing surprise.

In this section​

  • Account setup — signing in, workspaces, and what you need before your first submission
  • Core concepts — jobs, workflows, workstations, coretypes, software, files
  • Your first job — the guided walkthrough
  • Tutorials — by software, by task, and video
  • Glossary — Rescale-specific terms

Getting help​

The Rescale Help Center covers troubleshooting these docs assume away. For a specific failing job, share it with Support. They can't see your work otherwise.