> ## Documentation Index > Fetch the complete documentation index at: https://docs.holos.io/llms.txt > Use this file to discover all available pages before exploring further. # Holos Foundry > Dedicated, secure compute that builds trackable objects for your organization. Holos Foundry is available to **select customers only**. If your organization needs dedicated processing capacity or wants sensitive scans to stay on your own hardware, [contact us](mailto:hello@holos.io) to request access. **Holos Foundry** is the compute layer that turns a 3D model into a **trackable object**: the reference descriptor that lets [Holos Capture](/capture/index) recognize a specific real-world object and follow its position throughout a session. Building a reference object is a heavy, Apple-toolchain-only job: it can take many hours per object and has to run on a Mac. Foundry is the managed fabric that runs that work, a fleet of Macs (**runners**) that pull queued jobs, train the reference object, and upload the result back so the object flips to **Trackable** in your [Objects](/dashboard/objects) library. 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 With bring-your-own-Mac runners, source captures and 3D models are processed on hardware your organization controls. Sensitive assets never leave your environment. Reserved runners mean your training jobs aren't waiting behind anyone else's queue. Add Macs to train more objects in parallel. Runners only ever pull work over outbound HTTPS: no inbound ports, no SSH. They authenticate with short-lived, scoped, revocable machine tokens. Enroll, monitor, and revoke runners from the dashboard. Builds auto-update, so your fleet stays current without manual maintenance. ## How it fits together 1. Someone on your team [enables object tracking](/dashboard/objects#enabling-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** claims the job, downloads the source model, and trains the reference object locally on its Mac. 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. The whole flow is anchored in your Objects library: you request tracking there, and Foundry is what fulfills it. See [Object tracking](/dashboard/objects#object-tracking) for the request side. ## The Foundry dashboard Organizations with Foundry access see a **Foundry** section in the [dashboard](https://app.holos.io) with two pages: Watch training jobs move through Queued → In Progress → Done, with live progress per job. Enroll and name the Macs that do the work, monitor their status, and rotate or revoke their credentials. The Foundry section only appears for members granted the **Foundry Manager** role. If you have Foundry access but don't see the section, ask your admin to grant you the role. ## Requesting access Foundry is offered as part of an engagement with the Holos team, tailored to your capacity and data-residency needs. Tell us about your object catalog and any data-residency requirements, and we'll help you set up dedicated runners.