Clouds
The engine runs where you choose: in your own AWS, Azure or Google Cloud account, on your own servers with Docker, or in a dedicated account Atlantic runs for you. LightHouse is the same in every case.
Choosing where it runs
Section titled “Choosing where it runs”In LightHouse, Setup and admin → Where agents run (client_admin): choose the cloud, the region and the deployment profile. LightHouse shows the estimated saving of ephemeral against always-on, then:
- for your own cloud or servers, gives you the files to apply: a bootstrap that creates the identity your pipeline deploys with, and the stack itself as Terraform (Compose on your own servers). Your own pipeline applies them, as a reviewed merge request. LightHouse never applies infrastructure in your account, and the bootstrap grants Atlantic no access to it;
- for Atlantic-hosted, records your request for Atlantic to review. See Atlantic-hosted.
Changing your choice later moves nothing: the old deployment keeps running until your own pipeline takes it down.
The same choice by API: GET and PUT /api/v1/run-targets, and GET /api/v1/run-targets/stack for the files. See the Read reference.
What is the same everywhere
Section titled “What is the same everywhere”- The engine’s components: the gateway, the orchestrator and jobs, the telemetry relay, the content reader and the command channel.
- The telemetry contract: counts and timings to LightHouse, never content.
- Every component dials out to LightHouse over HTTPS; nothing in your account listens for Atlantic.
- Your content, your index and your model calls stay in your account and region. See Data sovereignty.
- The stack is a pinned, tagged version of Atlantic’s infrastructure modules, upgraded by a reviewed change. See Upgrades.
At a glance
Section titled “At a glance”| AWS | Azure | Google Cloud | On-premises | Atlantic-hosted | |
|---|---|---|---|---|---|
| Bootstrap | CloudFormation | Bicep | Terraform | Compose | Atlantic |
| Stack | Terraform | Terraform | Terraform | Compose | Atlantic |
| Regions in LightHouse | eu-west-1, eu-west-2, eu-central-1, us-east-1, us-west-2 | westeurope, northeurope, uksouth, eastus, westus2 | europe-west2, europe-west1, europe-west4, us-east4, us-central1 | Yours | eu-west-1, eu-west-2, eu-central-1, us-east-1 |
| Models | Amazon Bedrock | Azure OpenAI | Vertex AI | Any backend the gateway supports | Amazon Bedrock |
| Profiles | Both | Both | Both | Both | Both |
| Estimated saving, ephemeral | $314.78 a month | $179.62 a month | $254.10 a month | No cloud bill to compare | Quoted as managed infrastructure |
The first region listed is LightHouse’s default. Savings are for a small deployment at list prices in the first region, and are estimated: see Deployment profiles.