Skip to main content
Aspect Workflows runs on Aspect Cloud, Aspect’s multi-tenant service, or on Aspect Enterprise, an isolated deployment for your organization. The remote cache, the Build Results UI and the CLI are on both. What differs is where your build data lives, who can reach it, who operates it, and whether CI and developer machines share one cache.

​
Quick answer

Hosted by Aspect and self-hosted are the same product, Aspect Enterprise, in different cloud accounts. On-prem (coming soon) is a third deployment option, installed with a Helm chart on your own hardware. Hosted and self-hosted can start with a 30-day trial of Aspect Enterprise.

​
Pricing

Aspect Cloud has a Free tier and a Team tier, both on pricing. For Aspect Enterprise, talk to us.

​
Side by side

​
How to choose

Start with where your build data is allowed to sit.
  • If there’s no constraint, Aspect Cloud gets you cache hits today with nothing to provision.
  • If isolation is required but the data may live in a vendor’s cloud, Aspect Enterprise hosted by Aspect gives you isolated infrastructure and isolated data without an infrastructure project.
  • If build inputs, secrets and artifacts must stay inside infrastructure your company owns, choose Aspect Enterprise, self-hosted. This is common in regulated industries (healthcare, financial services, security) and in large enterprises, where the requirement is written down. Self-hosted is also the only option for air-gapped networks and GovCloud.
Both Aspect Enterprise options give you data isolation: no other customer shares your infrastructure or data. Self-hosted adds data ownership: your account, credentials and retention. Security and data handling has the detail. Then decide who operates it. When Aspect hosts, Aspect provisions, monitors, upgrades and restores, and nobody on your team learns the infrastructure. Self-hosted spans a range: Aspect can operate and maintain it while your team keeps access for visibility, or your team can own maintenance with Aspect read-only or advisory. Self-hosted deployment options lays out that range. Then decide how much to customize. A standard deployment (Aspect-managed, Aspect sign-in, endpoints on Aspect’s domain) is the same hosted by Aspect and self-hosted, includes every Aspect Workflows capability, and is the fastest to stand up, with the least work for your infrastructure team. Customizations are fully supported for organizations that require them for security, compliance, or data privacy:
  • SSO through Aspect sign-in, connected to your identity provider
  • Your own identity provider in place of Aspect sign-in
  • SCIM provisioning from your directory, with Aspect sign-in
  • Private endpoints (AWS PrivateLink or GCP Private Service Connect) and VPC peering
  • Endpoints on your own DNS domain
The cache and remote execution speak the standard Remote Execution API and your pipelines run vanilla bazel, so moving between Aspect Cloud and Aspect Enterprise, or between hosted by Aspect and self-hosted, changes endpoints and credentials, not your build. The new deployment’s cache starts cold, and build history stays where it was recorded.

​
Next