# Security & Isolation (https://tenki.cloud/docs/trust/security)

> For the complete documentation index, see [llms.txt](https://tenki.cloud/llms.txt)

How Tenki isolates customer workloads and secures CI infrastructure, operating under the SOC 2 Type II program of its parent company Luxor.



Security at Tenki rests on three pillars: **ephemeral per-job VMs**, **isolation enforced at the hypervisor layer**, and **an audited compliance posture inherited from our parent company, Luxor**.

Ephemeral, single-use VMs [#ephemeral-single-use-vms]

Every job, Linux x64 or macOS, runs in a fresh VM that is provisioned at job start and destroyed at job end. VMs are never reused across jobs or across customers. There is no persistent state on the runner between jobs.

This is the property mobile-signing and supply-chain-sensitive teams typically require. Confirmed properties:

* New filesystem on every job
* No shared memory or process space between jobs
* VM teardown happens immediately on job completion, regardless of success or failure
* No background workload reuses the VM

Isolation model [#isolation-model]

| Runner family | Compute                                                  | Isolation                                               |
| ------------- | -------------------------------------------------------- | ------------------------------------------------------- |
| Linux x64     | Bare-metal AMD EPYC compute, owned and operated by Tenki | Each job runs in a dedicated VM                         |
| macOS M4 Pro  | Apple Silicon hardware in our fabric                     | Each job runs in an isolated VM destroyed on completion |

macOS hardware is multi-tenant at the hardware level (resources are shared across customers), but jobs themselves always run in isolated VMs that are destroyed after each job. There is no shared filesystem, no shared keychain, and no shared user account between jobs.

Secrets [#secrets]

Tenki does **not** operate a secrets store. Secrets are managed by GitHub Actions and injected into the job at runtime through the standard `secrets.*` mechanism. See [Secrets](/docs/runners/secrets-and-signing) for more on the ephemeral-VM model.

Compliance [#compliance]

Tenki is operated by **Luxor**, a company founded in **2017** that is profitable and cash-flow positive with over 100 employees. Luxor holds:

* **SOC 1 Type II**, renewed annually
* **SOC 2 Type II**, renewed annually
* Yearly audited financial statements

Most of Luxor's largest customers are publicly traded companies operating in the data-center (Bitcoin mining / AI-HPC) space, with the security and compliance bar that implies.

Tenki operates under the SOC 2 Type II program of its parent company Luxor.

> **Need a SOC 2 Type II report?:** Tenki operates under the SOC 2 Type II program of its parent company Luxor Technology; the report is available under NDA — email hello@tenki.cloud to request it.

GitHub App scopes [#github-app-scopes]

The two Tenki GitHub Apps (Runner and Code Reviewer) request the minimum permissions required for their respective functions. See [GitHub App access levels](/docs/github/gh-app-access-level) for the full permission table and the rationale for each scope.