Docs

Pricing

Cost model for Alien Container resources.

Alien provisions Containers in the customer's cloud. The customer pays the cloud provider for the underlying infrastructure, and Alien charges a small management fee. See Pricing for Alien's current rates.

Cloud cost for Containers is driven by machines, persistent storage, load balancers, data transfer, and any container registry storage or transfer.

Cost Components

ComponentApplies WhenNotes
MachinesEvery cloud container deploymentContainer replicas run on machines in the customer account. Autoscaling changes this cost over time.
Persistent disks.persistentStorage(...) or stateful cloud containersBilled by size, disk type, provisioned IOPS, and throughput where supported.
Ephemeral disks / local SSD.ephemeralStorage(...) or capacity groups with local disksPricing depends on selected instance families and local-disk options.
Load balancersA port is exposed publiclyBilled by provider-specific hourly, rule, capacity-unit, or data-processing dimensions.
NAT / egressPrivate services need outbound internet accessCreated networks use managed NAT; BYO networks use customer-managed egress.
Data transferPublic ingress/egress or cross-zone trafficCharged by cloud provider and region.
Registry storage and pullsImage storage and deployment pullsUses the configured artifact registry.

Provider Mapping

PlatformMachinesPersistent StoragePublic Exposure
AWSEC2EBSLoad balancer and target groups
GCPCompute EnginePersistent DiskGoogle Cloud load balancing
AzureVirtual MachinesManaged DisksAzure Load Balancer
Kubernetes / On-PremCluster nodesPersistentVolumeClaimsCluster ingress or service configuration
LocalLocal machineLocal Docker volumes / bind mountsLocal port forwarding

Example Cost Shape

For a public two-replica API with a 100 GiB persistent disk:

ItemQuantity
MachinesAt least two scheduled replicas plus cluster headroom
Persistent storage100 GiB per stateful replica that owns a volume
Load balancingOne public port
NetworkNAT and egress if replicas run on private subnets
RegistryImage storage plus image pull transfer

Notes

  • Autoscaling reduces idle replica count but does not remove the cost of minimum replicas.
  • Stateful replicas generally keep their disks after restarts and reschedules.
  • BYO networking shifts NAT, routing, and firewall costs to the customer-managed network.
  • GPU containers are priced by the selected GPU instance family and any attached disks.

Sources

On this page