# Atlantic-hosted

> The engine run for you by Atlantic: what that means for your data, regions and access.

**Atlantic-hosted** means the engine runs in a dedicated AWS account in Atlantic’s AWS organisation, in the region you choose, managed and billed by Atlantic. It is the same engine and the same stack as [AWS](/clouds/aws/), run for you.

## How to ask for it

1. In LightHouse, **Setup and admin → Where agents run**, choose **Atlantic-hosted**, a region and a profile (ephemeral by default), and optionally a reason.
2. Choose **Ask Atlantic to host it**. Nothing is created yet: the request goes to Atlantic’s engineers. One request is open at a time; withdraw it to ask for a different region.
3. Atlantic approves or declines it. Once approved, an engineer creates the account and applies the stack; the request then shows **Provisioned**, and the deployment appears in LightHouse.

By API, as a `client_admin`: `POST /api/v1/run-targets/hosted-requests` with `{"region": "eu-west-2", "profile": "ephemeral", "reason": "..."}`, `GET` to follow it, and `DELETE /api/v1/run-targets/hosted-requests/{rid}` to withdraw it. See the [Read reference](/api/reference/read/#post-hosted).

LightHouse itself cannot create accounts: a person does, after approval.

## Where it runs, and whose account

- A dedicated AWS account for your tenant, created in Atlantic’s organisation and placed under its guardrails. No other client shares it.
- Atlantic’s organisation policies apply to it: it stays in the organisation, the audit trail cannot be turned off, and models are called only in the regions your contract names.
- The account’s security baseline is applied before the stack.

## Regions and residency

eu-west-1 (the default), eu-west-2, eu-central-1 and us-east-1. Everything the stack creates is pinned to the region you choose, as on [AWS](/clouds/aws/#regions). See [Residency by cloud](/data-sovereignty/residency-by-cloud/).

## Who can see what

Your content is in that account, read in place, as in your own cloud. Atlantic’s engineers operate the account; what they may see of your content in LightHouse is still governed by your access rules. See [Who can see what](/data-sovereignty/access/).

## Cost

Quoted as managed infrastructure: there is no cloud bill of yours to compare, so LightHouse shows no estimated saving for it.

## Moving to your own cloud later

Choose your own cloud in **Where agents run** and apply its stack. Changing the choice moves nothing on its own: the hosted deployment keeps running until it is taken down, so you can move when the new one is ready.

Source: https://docs.atlanticagenticlabs.com/clouds/atlantic-hosted/