Pricing
Cost model for Alien Daemon resources.
Daemon has no separate Alien infrastructure charge.
Local
Local daemons run on the developer or operator machine. There is no cloud provider bill from Alien.
Kubernetes / On-Prem
Kubernetes daemons consume the cluster resources requested by their image and runtime environment. The cost is whatever the cluster operator pays for nodes, storage, networking, and registry pulls.
| Component | Applies When | Notes |
|---|---|---|
| Cluster nodes | Always | The daemon runs as a pod on existing cluster capacity. |
| Registry storage and pulls | Image-based daemons | Charged by the configured registry. |
| Logs and telemetry | If enabled by the environment | Cost depends on the cluster observability stack. |
| Kubernetes Secrets | Linked resources with secret material | Usually included in cluster control-plane/storage costs. |
AWS, GCP, Azure
Daemon is not currently supported on AWS, GCP, or Azure. There is no cloud pricing model until those platforms are supported.
Cost Control
- Keep daemon images small to reduce registry pull time and transfer.
- Use Container instead of Daemon when you need explicit CPU, memory, scaling, ports, or persistent storage.
- Use Worker instead of Daemon when work can be handled as bounded request-response execution.