> ## Documentation Index
> Fetch the complete documentation index at: https://site.aspect.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Aspect Enterprise

> Aspect Enterprise is an isolated deployment of Aspect Workflows for one organization, hosted by Aspect, or self-hosted in your own AWS account or GCP project.

export const gatedAccess = (user, group) => {
  const loggedIn = !!(user && user.loggedIn);
  const groups = user && user.tenantMetadata && user.tenantMetadata.docsGroups || [];
  if (loggedIn && (!group || groups.indexOf(group) >= 0)) {
    return "entitled";
  }
  return loggedIn ? "signed-in" : "anonymous";
};

export const GatedLink = ({access, href, group, children}) => {
  const note = group ? "Aspect Enterprise customers" : "free Aspect account";
  const muted = {
    fontSize: "0.85em",
    opacity: 0.7,
    whiteSpace: "nowrap"
  };
  if (access === "entitled") {
    return <a href={href}>{children}</a>;
  }
  if (access !== "signed-in") {
    return <span>
        <a href={"/login?redirect=" + encodeURIComponent(href)}>{children}</a>
        <span style={muted}> (sign in: {note})</span>
      </span>;
  }
  return <span>
      {children}
      <span style={muted}> ({note})</span>
    </span>;
};

Aspect Enterprise is an isolated deployment of Aspect Workflows for one organization: CI runners, remote cache, remote execution and the Build Results UI on infrastructure and data no other customer shares. It's for teams that need remote execution or CI runners today, or whose policy rules out shared infrastructure.

## What it adds over Aspect Cloud

Every deployment includes:

| Capability                                                                            | On Aspect Enterprise                                                                                                                                                                                                                                                                                                                                                                                           |
| ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **[Remote execution](/docs/aspect-workflows/platform/features/remote-execution)**     | Linux workers, [macOS](/docs/aspect-workflows/enterprise/guides/macos-remote-execution), and GPUs, plus workers on your own hardware for any worker type                                                                                                                                                                                                                                                       |
| **[CI runners](/docs/aspect-workflows/platform/features/ci-runners)**                 | Managed runners for GitHub Actions, Buildkite, GitLab and CircleCI: Linux VMs (x86, Arm, GPU) on any AWS or GCP instance type, with fully customizable images, in [runner groups](/docs/aspect-workflows/enterprise/ci-runners/runner-groups) with [warming](/docs/aspect-workflows/enterprise/ci-runners/warming). macOS and OCI image-based runners coming soon. Or bring your own runners, on any CI system |
| **[Selective delivery](/docs/aspect-workflows/platform/features/selective-delivery)** | Pushes only the artifacts whose Bazel outputs changed, to your bucket or registry                                                                                                                                                                                                                                                                                                                              |
| **Developer access**                                                                  | An [external endpoint](/docs/aspect-workflows/enterprise/connect/local-setup#the-external-endpoint) for laptops and your own CI, sharing CI's cache and executors or running a separate set                                                                                                                                                                                                                    |

Also available:

| Option                         | What it is                                                                                                                                                                                                                                        |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **SSO**                        | SSO through Aspect sign-in, connected to your identity provider                                                                                                                                                                                   |
| **Your own identity provider** | Your identity provider in place of Aspect sign-in, with no Aspect accounts. [Changes how CI authenticates](/docs/aspect-workflows/enterprise/connect/ci-setup#if-the-deployment-uses-your-own-identity-provider)                                  |
| **SCIM provisioning**          | Users synced from your directory into Aspect sign-in. Not needed with your own identity provider, which manages users and groups itself                                                                                                           |
| **Private endpoints**          | AWS PrivateLink or GCP Private Service Connect from your VPCs, alongside the authenticated public endpoints                                                                                                                                       |
| **VPC peering**                | Route exchange with your VPCs, for actions that must reach private services on your side                                                                                                                                                          |
| **Your own DNS domain**        | Endpoints on a subdomain you delegate, instead of Aspect's domain                                                                                                                                                                                 |
| **Who operates it**            | Hosted by Aspect: Aspect. Self-hosted: Aspect-managed, co-maintained, customer-managed with operational or read-only access for Aspect, or no Aspect access. See [Who operates it](/docs/aspect-workflows/enterprise/self-hosted#who-operates-it) |

[Talk to us](/contact) about a [30-day trial of Aspect Enterprise](/docs/aspect-workflows/enterprise/evaluation/greening) on your own repository before you commit.

## Hosted, self-hosted or on-prem

<CardGroup cols={3}>
  <Card title="Hosted by Aspect" icon="cloud" href="/docs/aspect-workflows/enterprise/hosted/overview">
    In an isolated account in Aspect's cloud. Aspect provisions, monitors, upgrades and restores it. You configure runner groups and remote execution pools by asking, not by applying Terraform.
  </Card>

  <Card title="Self-hosted" icon="server" href="/docs/aspect-workflows/enterprise/self-hosted">
    In your own AWS account or GCP project, deployed by Terraform. Source, secrets and artifacts stay in your network. Covers air-gapped and GovCloud.
  </Card>

  <Card title={<>On-prem <span className="coming-soon-chip">Coming soon</span></>} icon="building" href="/contact?topic=on-prem">
    On your own hardware, deployed with a Helm chart.
  </Card>
</CardGroup>

## Which one

The platform is identical. What differs is whose cloud account it sits in, who holds the credentials, and how a configuration change gets made; [choosing between them](/docs/aspect-workflows/platform/choosing#side-by-side) has the full comparison.

**Hosted by Aspect** is the default. You get isolation without an infrastructure project.

**Self-hosted** is for when you require data ownership: build inputs, secrets and artifacts staying inside infrastructure your company owns. It's also the only option for air-gapped networks and GovCloud.

**On-prem** is coming soon; [join the early access list](/contact?topic=on-prem). Remote execution workers on your own hardware are available today on any deployment.

<Callout icon="cloud" color="#71717a">
  Azure and Oracle Cloud are planned. [Contact us](/contact) if you're interested.
</Callout>

## The path

<Steps>
  <Step title="Evaluate it on your own repository">
    A [30-day trial of Aspect Enterprise](/docs/aspect-workflows/enterprise/evaluation/greening) gets your build green on a
    deployment, then [measures the result](/docs/aspect-workflows/enterprise/evaluation/measuring) against
    your current CI.
  </Step>

  <Step title="Stand it up">
    [Hosted by Aspect](/docs/aspect-workflows/enterprise/hosted/overview): Aspect
    provisions it from [what you provide](/docs/aspect-workflows/enterprise/hosted/setup).
    [Self-hosted](/docs/aspect-workflows/enterprise/self-hosted): Terraform into your AWS
    account or GCP project.
  </Step>

  <Step title="Register runners with your CI">
    The deployment's runners join GitHub Actions, Buildkite, GitLab or CircleCI. Hosted by
    Aspect, Aspect does this from what you provide. Self-hosted, you do it with
    <GatedLink access={gatedAccess(user, "workflows-subscriber")} href="/docs/aspect-workflows/enterprise/self-hosted/runner-registration/overview" group="workflows-subscriber">runner registration</GatedLink>.
  </Step>

  <Step title="Connect developers and pipelines">
    [Local setup](/docs/aspect-workflows/enterprise/connect/local-setup) for laptops, and
    [CI setup](/docs/aspect-workflows/enterprise/connect/ci-setup) for pipelines, on Workflows
    runners or your own.
  </Step>
</Steps>

## Security

Aspect is SOC 2 Type 2 certified. The [security overview](/security-overview) covers compliance, and [security and data handling](/docs/aspect-workflows/platform/security) has the detail, including what data a deployment holds and who at Aspect can reach it.

## Releases

Aspect Enterprise deployments run versioned releases of Aspect Workflows, numbered `MAJOR.MINOR.PATCH` without following semantic versioning: a minor release can carry breaking changes, and a patch release avoids them. Minor releases typically ship every one to three months, and patches ship as fixes need them.

Each release has <GatedLink access={gatedAccess(user, "workflows-subscriber")} href="/docs/aspect-workflows/enterprise/release-notes/overview" group="workflows-subscriber">release notes</GatedLink> and, where it needs one, an upgrade guide.