# Atlas Cloud: accounts and updates without touching your code

> Atlas Cloud is the optional control plane for Atlas. It handles accounts, entitlements, releases, and telemetry, and is designed to never receive repo contents, prompts, diffs, or credentials.

Atlas Cloud is the optional commercial control plane for Atlas. It manages accounts, entitlements, release manifests, and allowlisted telemetry, while the agent keeps running on your machine with your own model keys. By design the control plane never requires repo contents, prompts, diffs, terminal output, local indexes, embeddings, model outputs, provider request bodies, file paths, filenames, or credentials.

## Key takeaways

- Atlas Cloud is optional; the agent still runs locally with your own keys.
- The control plane handles accounts, entitlements, releases, and telemetry only.
- It is designed to never receive code, prompts, diffs, embeddings, or credentials.
- Telemetry accepts only allowlisted event fields and rejects prompt or code-looking values.

## What the control plane does

Atlas Cloud is split into three services: a cloud API for accounts, entitlements, releases, devices, sync, and telemetry intake; a model router for optional hosted routing; and a worker for billing reconciliation, usage rollups, and release validation.

This is the commercial layer around the local agent. It answers questions like is this seat entitled, what is the current stable release, and which devices are registered. It is deliberately separate from the runtime: the local product consumes Atlas Cloud through published API contracts only, so cloud availability never blocks local work.

## What it is designed never to see

The privacy boundary is explicit. Ordinary control-plane operations must not require repo contents, prompts, diffs, terminal output, local indexes, embeddings, model outputs, provider request bodies, file paths, filenames, or credentials.

That list is a design constraint, not a policy promise. Because your source, prompts, and keys are never part of a control-plane request, there is nothing of that kind for the cloud to log, cache, train on, or leak. Privacy is preserved by what the API accepts, not by what a retention policy says will be discarded later.

## Telemetry stays allowlisted

Telemetry intake accepts only an allowlisted event envelope. It rejects values that look like prompts, model output, provider bodies, or file paths before they are ever stored.

Install and usage signals move through a narrow, typed contract so product analytics never becomes a backdoor for code or content. Entitlement and usage reads are gated by token in staging; release and installer manifests expose only public, non-entitlement artifact metadata.

## FAQ

### Does Atlas Cloud see my code or prompts?

No. The control plane is designed so ordinary operations never require repo contents, prompts, diffs, embeddings, model outputs, provider request bodies, file paths, or credentials.

### Is Atlas Cloud required to use Atlas?

No. The agent runs locally with your own model keys. Atlas Cloud is the optional commercial control plane for accounts, entitlements, releases, and telemetry.

### What is Atlas Cloud actually for?

Accounts and entitlements, release and installer manifests, device registration and sync, optional hosted model routing, and allowlisted telemetry and billing.

### What telemetry does it collect?

Only an allowlisted event envelope. Values that look like prompts, model output, provider bodies, or file paths are rejected before storage.

---

Canonical HTML: https://runatlas.sh/resources/features/atlas-cloud
Source of truth: aeo_pages row `/resources/features/atlas-cloud` (segment: Platform) (this file is generated from it, never hand-edited).
Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.