Beam currently publishes a strong free-developer offer: the Developer plan is listed at $0 per month plus usage, and Beam-authored material says new accounts include $30 in credit refreshed monthly. That sounds like a straightforward recurring free-compute allowance.
The operational details are less straightforward. Beam’s live onboarding page tells users that workloads draw from a credit balance, pause at $0, and asks them to add credits before running work. That makes one distinction important enough to surface explicitly:
an advertised recurring credit is not the same thing as a confirmed spendable balance in a specific account.
Bump Models therefore records the current Beam Developer monthly credit as an advertised benefit rather than proof that every newly created account has already received $30. For anyone evaluating the offer, the right first action is not to estimate a month’s free GPU capacity. It is to verify whether the workspace actually shows the credit.
Beam’s own public surfaces support both sides of the distinction
Three current Beam surfaces establish the useful facts.
The live Beam pricing page lists the Developer tier at $0 per month, plus usage. It also shows the underlying metered pricing: serverless RTX 4090 GPU time is listed at $0.000191667 per second, H100 PCIe at $0.000972 per second, and CPU and memory are billed separately for serverless workloads. The same page lists a 5-container GPU concurrency limit for the Developer tier.
A Beam-authored July 2026 article, Serverless GPU for Reinforcement Learning, says that new accounts include $30 in credit refreshed monthly. This is direct first-party evidence for the recurring-credit claim rather than a third-party coupon listing.
But Beam’s current Get started flow says that workloads draw from the workspace credit balance and pause when the balance reaches $0. It then presents buttons to add $20, $50, $100, or a custom amount, and describes optional auto top-up.
Those statements are not necessarily contradictory. A platform can advertise recurring credits while still showing a generic funding flow. What they do mean is that the public marketing claim alone does not establish whether a particular account has been credited, when the refresh occurs, or whether some eligibility or provisioning condition applies behind the account boundary.
That is why the current Resource is marked for verification rather than treated as guaranteed received value.
The $30 matters because Beam is usage-priced, not actually free compute
The Developer plan’s $0 monthly fee removes a subscription charge. It does not make compute itself free.
At the current published serverless rates, the GPU component of an RTX 4090 is about $0.69 per hour before CPU and RAM. The H100 PCIe GPU component is about $3.50 per hour. If a full $30 balance is available and can be applied to those workloads, that is roughly 43 RTX 4090 GPU-hours or 8.6 H100 GPU-hours before adding separately metered CPU and memory.
Those are illustrations, not promises about what a credit covers. Beam also offers on-demand machines, sandboxes, storage, and bring-your-own-cloud billing, each with a different cost structure. The important point is simply that a recurring $30 balance would be economically meaningful for experiments, agent sandboxes, small inference tests, or short GPU jobs. It is large enough to influence platform choice for light development, but small enough that an unnoticed paid balance or auto top-up can change the economics quickly.
This is why the Credits market should distinguish three values:
- the acquisition cost of the program;
- the advertised credit value;
- the balance a specific account has actually received.
For Beam’s Developer offer, the first is currently $0. The second is advertised as $30 refreshed monthly. The third cannot be inferred from a public webpage.
A safer activation sequence is only three checks
For a new Beam account, the practical verification path is short.
First, sign in and inspect the actual workspace balance before deploying anything. A visible $30 balance is stronger evidence than a marketing page because it establishes that the benefit has reached that account.
Second, confirm whether the balance changes after a minimal workload. Beam’s onboarding makes clear that usage draws down a credit balance. A tiny CPU or GPU test is enough to prove that the balance is spendable without turning the verification itself into a meaningful bill.
Third, leave automatic top-up disabled until the recurring-credit behavior is understood. If a workload pauses at $0, that is a bounded failure. If auto top-up is enabled first, a test intended to validate free credit can silently become paid usage.
This is a general rule for cloud-credit programs: verify receipt before optimizing around face value. It is especially useful for recurring programs because the value compounds only if the refresh really reaches the account on the expected cadence.
Why the current offer is still worth tracking
The uncertainty around account provisioning does not make the Beam offer uninteresting. The opposite is true.
A $0 Developer subscription, usage-based billing, and a recurring $30 advertised credit create a potentially useful low-friction environment for small serverless and sandbox workloads. Beam’s current pricing also makes the benefit easy to translate into real compute experiments rather than an abstract promotional number.
What changes the decision is evidence quality.
If the $30 balance appears automatically and refreshes monthly, the offer behaves like a recurring free-development allowance and deserves to be evaluated against other recurring developer credits. If an account instead shows $0 and asks for a top-up, the public claim should not be used as though the benefit has already been received. That account needs clarification from Beam before the credit is counted as available value.
The market signal therefore remains positive, but the correct status is advertised and worth verifying, not guaranteed received.
For current terms and pricing, check Beam’s pricing page, the first-party article that states the recurring $30 benefit, and the live onboarding flow before committing a workload. The linked Resource card remains the current-state reference; this article records the evidence and decision rule as of the snapshot below.