Skip to main content
See the pricing page for current rates and your dashboard for usage and billing.

CPU capacity tiers

CPU workloads can choose a capacity tier: See current rates. New accounts default to Performance, and workloads opt into Shared or Spot; omitting the tier keeps an existing account’s default. When Performance capacity is full, Performance workloads may run on Shared hosts, still with no CPU sharing. GPU workloads and private pools keep their own pricing and placement. Tiered VMs and VM-backed sandboxes require at least 1 vCPU / 1 GiB. Ordinary containers support fractional resources. Requires beam-client >= 0.2.236 or @beamcloud/beam-js >= 1.1.7. Python decorators accept cpu_tier="shared"; JavaScript configuration uses cpuTier: "shared". CLI deployments accept --cpu-tier shared. A workload keeps its tier’s prices from its first run, even if rates change later; a new deployment starts at current rates. GPU-attached CPU and RAM keep the GPU rates. The $20/month plan still includes $20 in usage credits. Spot work waits for spare capacity instead of adding machines. Functions and sandboxes fail if none frees up within 20 minutes; deployments keep trying while they have requests, queued tasks or min_containers, and replace interrupted containers the same way. Spot functions retry interruptions within their configured retry limit. Interrupted HTTP requests fail; Beam does not transparently replay them. Set application timeouts and retries for your own requests.

Serverless Compute

You are charged whenever a container is running. This includes: You are not charged for waiting for a machine to start or pulling your container image.

Reserved Machines and Your Own Hardware

Reserved machines are billed by the hour until they’re released, even when apps are idle. Leases renew hourly while your workspace has credit, so a reservation can outlast its original TTL. See How Reserved Nodes Are Billed. Your own hardware has a Beam management charge. Hosted model rates appear in the endpoint catalog.

Credits

Buy $20 in credits each month with the $20/month Developer plan in Settings → Credits. Unused monthly credits expire at renewal and do not roll over. Monthly credits are spent first. You can buy extra credits at any time; extra credits do not expire. Prepaid workloads stop when the balance runs out.

What About Storage?

Storage is not billed yet. Planned pricing is $0.0001 per GB-hour of data stored, with no free allowance.This will use the same usage credits as compute and cover retained VM disk, volume, and snapshot data, including while compute is stopped. Empty disk capacity, shared base images, and internal copies are excluded. 1 GB = 1 billion bytes.
See the pricing page for current rates.

Default Container Spin-down Times

After handling a request, Beam keeps containers running (“warm”) for a certain amount of time in order to quickly handle future requests. By default, these are the container “keep warm” times for each deployment type: Always-on settings keep containers running. Sandboxes use a lifetime instead of an idle timer; the Python default is 600 seconds.

Real-World Example

You’ve deployed a REST API. You’ve added two Python Packages in your Image(), which are loaded when your app first starts. You’ve also added a keep_warm_seconds=300, which will keep the container alive for 300 seconds (5 minutes) after each request.
app.py
Let’s pretend you deploy this and call the API. Suppose it takes:
  • 1s to boot your application and run your on_start function.
  • 100ms to run your task.
  • 300s to keep the container alive, based on the keep_warm_seconds argument.
You would be billed for a total of 301.1 seconds.