Written for Teams who want a real remote cache without an infrastructure project.
What problem it solves
Everything Aspect does well has, until now, required a deployment.
Even when we own the cloud, there is still an account, a provisioning conversation and a contract before anyone gets a cache hit. That is correct for a large platform organisation, and a wall for everyone else.
So the teams with the most to gain get nothing. Their builds hurt and their platform headcount is zero, so either they go without, or they stand up open-source Buildbarn themselves and inherit an operational job nobody was hired for. Multi-tenancy removes the provisioning step altogether. Time-to-value goes from a project to a login.
And a way up when you outgrow it
You don’t pick a tier and hope. You start where you are and move when you need to.
If you need isolation, or remote execution and CI runners today, you move to Aspect Enterprise: hosted by Aspect, or in your own account, including air-gapped and GovCloud. Same platform, same tooling, no new vendor; moving changes endpoints and credentials, not your build. The answer to “what happens when we get big?” is a path rather than an apology.
Test runs across languages from Aspect’s public workflows template, on Aspect Cloud.
- Not a reduced-visibility tier. You get the same Build Results UI as Aspect Enterprise customers, scoped to your organization.
- Not a replacement for Aspect Enterprise. Air-gapped, GovCloud and regulated customers who need isolation route to Aspect Enterprise, and that stays first-class.
- Your CI stays. Your pipelines keep running on the CI you already use, with the cache in front of them. Aspect Cloud CI runners are coming soon.
Where it runs
Three ways to run this, and the axis that separates them is isolation, not hosting.
| Option | Infrastructure | Cloud account | Operated by |
|---|---|---|---|
| Aspect Cloud | Shared, scoped to your organization | Aspect’s | Aspect |
| Aspect Enterprise, hosted by Aspect | Isolated, yours alone | Aspect’s | Aspect |
| Aspect Enterprise, self-hosted | Isolated, in your account | Yours | Aspect, or your team |
The last two are the same product, Aspect Enterprise. What differs is whose account it runs in and who holds operational control. Holding that control yourself is usually the point. Plenty of teams in finance, healthcare and government are not allowed to give a third party production access. For them we work over the shoulder: we guide and diagnose, their hands stay on the controls. It is what makes air-gapped and GovCloud deployments possible at all.