Welcome
Alien is infrastructure for software outside your cloud: the part of your product that has to run in a customer's AWS, Google Cloud, or Azure account, their Kubernetes cluster, or a site with no connection at all.
Your code needs to run in the customer's environment when sensitive data can't leave, you need access to services behind their firewall, or their security team requires it. The usual answer is self-hosting — but then you lose control. No auto-updates, no logs, every customer on a different version.
With Alien, your software runs in their environment while your team keeps the operating loop: releases, telemetry, remote commands, rollback, and revocation. Your handlers and telemetry configuration determine what leaves the environment; Alien does not infer which application data is sensitive.
Quickstart
Build a worker, test it locally, and deploy — no cloud account needed.
How Alien Works
Stacks, deployments, updates, commands — the mental model.
Kubernetes
Customers install a Helm chart once; releases, logs, and requests flow through your manager.
Self-Hosting
Run the manager yourself with Docker, Kubernetes, or Amazon ECS.
Operate Existing Environments
Attach Alien to BYOC deployments you already ship.
Infrastructure
Workers, storage, queues, KV, vaults, and artifact registries.
Permissions
Least-privilege access control across AWS, GCP, and Azure.