Skip to main content
A runner is a Mac enrolled with Foundry that pulls jobs from the queue, does the work locally, and uploads the results. The Runners page (Foundry → Runners in the dashboard) is where you enroll runners, watch what they’re doing, and manage their credentials.
Foundry runners are available to select customers only. This page is visible to organization admins and managers whose organization is enabled for its own runners. Contact us to set that up.

​
Runner status

Each runner reports a live status derived from when it was last seen, whether it holds a job, and what it says about its own health: For each runner the page also shows its name, host machine, who enrolled it, when it was last seen, and how many jobs it has recently completed. Hovering a runner’s name lists the services it serves. You can give each runner a custom icon and color to tell your fleet apart at a glance.

​
Enrolling a runner

The easiest way to enroll a Mac is from the Foundry app itself — no credentials to copy or paste.
  1. Install the Foundry app on the Mac (the Holos team provides it as part of your setup).
  2. Open it and sign in to your Holos organization.
  3. Click Enroll this Mac.
Foundry mints the machine credentials, stores them securely in the Mac’s Keychain, and the runner starts pulling jobs right away. It shows up on this page within moments, permitted to serve the services that build of the app supports.

​
Enroll from the dashboard (alternative)

If you’d rather create the credentials yourself, you can add a runner from the dashboard and configure the Mac by hand:
  1. Click Add runner and give it a name.
  2. Foundry generates a client ID and client secret.
  3. Configure the runner Mac with the client ID and secret.
The client secret is shown exactly once, at creation. Copy it immediately and keep it somewhere safe. Foundry never displays it again. If you lose it, rotate the secret to get a new one.
Either way, the runner Mac uses its credentials to mint short-lived access tokens on its own. Nothing about enrollment opens an inbound connection to the Mac: the runner only makes outbound requests to Foundry.

​
Setting up the runner Mac

The runner software is a small macOS app the Holos team provides as part of your Foundry setup. Once it’s enrolled, it runs in the background, polls for queued jobs, and works on one job per service at a time. It updates itself automatically, so the Mac stays current without manual maintenance. The app’s Settings → Services switches decide what that Mac actually takes on, within what its credentials allow — useful when a machine should train objects overnight but stay out of the capture pipeline, for instance. See Services and data residency.
Object training is disk-intensive: a runner Mac needs roughly 64 GB free to claim a training job, and reports Low disk instead of claiming when it doesn’t have it. The capture services need far less.

​
Managing runners

From each runner’s menu you can:
  • Rotate secret: issue a fresh client secret and invalidate the old one. Use this on a schedule or if a secret may have been exposed. The new secret is shown once.
  • Revoke: permanently disable the runner’s credentials so it can no longer claim jobs. Use this when you retire a Mac.
  • Rename and restyle: update the display name, icon, and color.
  • Copy client ID: for matching a dashboard row to a machine.
Day-to-day control of a runner lives on the Mac itself, in the Foundry app: pause it so it takes no new jobs, choose its services, release the job it’s currently working on back to the queue, rotate its credentials, or remove its enrollment. Pausing is safe mid-job — the job in flight finishes first.
Changing which services a credential is permitted to serve is a Holos-side change: ask us and we’ll widen or narrow the grant. What the Mac takes on within that permission is yours to set, in the app.
Rotating or revoking takes effect on the runner’s next request. A runner mid-job will finish or lose it depending on timing; the job requeues automatically if interrupted.

​
Where your data is processed

Selecting Where is my data processed? on this page opens the full per-service, per-provider table: which services keep everything on the runner, and which hand material to an external provider. It always reflects what your fleet currently runs. See Services and data residency for the same table alongside what each service does.