Skip to main content
Holos Foundry is available to select customers only. If your organization needs dedicated processing capacity or wants captures and scans processed on your own hardware, contact us to request access.
Holos Foundry is the compute layer that processes your organization’s captures and objects: a fleet of Macs (runners) that pull queued jobs, do the work locally, and upload the results. Foundry started as the way to build trackable objects — the reference descriptor that lets Holos Capture recognize a real-world object and follow it through a session — because that job is Apple-toolchain-only and takes hours on a Mac. It now runs the capture pipeline too: preparing a video’s poster and scrubber previews, transcribing its audio, and extracting procedure steps from the transcript. See Services and data residency for the full list and where each one runs. For most organizations this happens automatically on Holos-operated infrastructure and needs no setup. Foundry becomes visible to your team when you run dedicated runners: either capacity we manage on your behalf, or Macs your own organization operates.

​
Why a dedicated Foundry

Keep sensitive material in-house

With bring-your-own-Mac runners, captures and 3D models are processed on hardware your organization controls. Most services keep everything on the machine; the residency table names the exceptions rather than leaving you to assume.

Dedicated capacity

Reserved runners mean your jobs aren’t waiting behind anyone else’s queue. Add Macs to process more captures and train more objects in parallel.

Secure by design

Runners only ever pull work over outbound HTTPS: no inbound ports, no SSH. They authenticate with short-lived, scoped, revocable machine tokens.

Managed and monitored

Enroll, monitor, and revoke runners from the dashboard. Builds auto-update, so your fleet stays current without manual maintenance.

​
How it fits together

Every service follows the same shape. Using object training as the example:
  1. Someone on your team enables object tracking for an object, choosing a view mode and training mode. This creates a training job.
  2. The job lands in the Foundry queue as Queued.
  3. An available runner that advertises this service claims the job and downloads what it needs.
  4. The runner streams progress back while it works, then uploads the finished reference object.
  5. The object’s Trackable field flips to Yes and it becomes available in Holos Capture.
Capture jobs work the same way but are enqueued for you: uploading a video capture queues its video prep, and each finished stage queues the next, so a capture arrives with a poster, scrubber previews, a transcript, and extracted steps without anyone requesting them. A runner can hold one job per service at a time, so a Mac granted several services works on several jobs at once rather than serializing everything behind an eight-hour training run.

​
The Foundry dashboard

Organizations with Foundry access see a Foundry section in the dashboard:

Job queue

Watch jobs move through Queued → In Progress → Done, with live progress and the service each one belongs to.

Runners

Enroll and name the Macs that do the work, choose which services they take, and rotate or revoke their credentials.
The Foundry section is visible to organization admins and managers. The Runners page additionally requires that your organization be enabled for its own runners — if it isn’t, the page says so and we can turn it on.

​
Requesting access

Foundry is offered as part of an engagement with the Holos team, tailored to your capacity and data-residency needs.

Contact us about Foundry

Tell us about your object catalog and any data-residency requirements, and we’ll help you set up dedicated runners.