Automation API adds high memory and GPU machines for Revit jobs

Share

Autodesk Platform Services has opened a public beta of three new compute options for the Automation API (formerly Design Automation), starting November 16, 2026. Revit is the first engine to get all three: bigger machines, GPU machines and a faster queue.

What’s new

Each option is a single parameter added to the existing POST /workitems request. Jobs that do not use them run exactly as before.

  • High Memory: add "memoryGb": 64 to run a job on a 64 GB machine instead of the standard 32 GB. Only 32 and 64 are accepted.
  • GPU: add "gpu": true together with "memoryGb": 64 to run on an NVIDIA GPU machine. A GPU request with 32 GB is rejected. Autodesk says large-model sheet, 3D view and floor plan exports ran about 1.7 to 2.1 times faster on GPU during the private beta.
  • Priority Pass: add "priority": "P1" to move a job ahead of standard P3 jobs in the queue. Autodesk is clear that it “does not guarantee a completion time”. P2 is not available yet.

High Memory and GPU are Revit only for now. Priority Pass works with Revit today, with AutoCAD, Inventor, 3ds Max and Fusion listed as coming soon. You can check an engine with GET engines/:id and look for "priorityPass": true.

Beta limits and pricing

  • Per APS app (client ID): up to 5 High Memory jobs and 5 GPU jobs in progress, and one P1 job at a time. Requests over the limit are rejected.
  • During the beta, High Memory and GPU jobs are billed at the current work item rate with no extra charge. Priority Pass is free.
  • At full release, planned for early 2027, the larger machines will be priced above the standard rate and Priority Pass is expected to become a paid add-on. Autodesk says final pricing is not set yet.

Autodesk also notes it may rerun some GPU work items on a standard machine for benchmarking, without billing them.

Why it matters

Teams that batch-process Revit models in the cloud often hit memory limits on large federated or detailed projects, and sheet exports can sit in the queue at busy times. These options target exactly those pain points without changing existing code paths.

If you run Revit jobs on the Automation API, the beta is a low-risk window to measure the gain: rerun your heaviest exports with 64 GB and GPU, compare time and failure rates, and decide before paid pricing arrives. Keep in mind that limits are per app and that the beta terms can change.

Source

Get the Revit news that matters

AI, releases, add-ins and API updates for Revit users. One short email, no spam, unsubscribe anytime.

Editor of revit.news and founder of HEXABIM. 25 years in civil engineering and digital modelling. Articles are prepared with the help of automated tools from linked public sources and published under his editorial responsibility.

Get the Revit news that matters

AI, releases, add-ins and API updates for Revit users. One short email, no spam, unsubscribe anytime.

Read more

Latest Revit news