Costs and current beta limits

Who pays what

The private beta offer is a 30-day pilot without a Barge platform or worker fee. Each beta user gets a personal allowance of 30 cloud worker hours. You bring a supported provider credential and remain responsible for the provider’s charges, credits, subscription terms, and rate limits.

Worker hours measure how long your cloud worker exists. They are separate from provider billing; session cost estimates do not replace your provider’s bill.

Your 30 hours

Tasks on your account use your personal 30-hour allowance. For example, a two-hour task followed by a one-hour task uses three hours and leaves you with 27 hours. Other beta users have separate allowances; their tasks do not use your hours.

Your 30-day pilot starts with your first admitted cloud task, rather than when you create your account. Starting another task or signing in on another device does not reset your hours or restart your pilot.

Worker time includes provisioning, active work, time kept open for follow-ups, and time spent on runs that fail or are cancelled. Retries and follow-ups also use your allowance when they run a worker. Time waiting in the queue without a worker does not consume hours.

You can have one active worker at a time. An individual task is limited to two hours, or your remaining allowance if that is smaller. The default task size is 2 CPUs and 4096 MB memory; deployment settings may lower those limits.

Look at your hours and pilot end date

Before your first cloud task, Settings → Beta worker allowance may say that your 30-day pilot starts with your first cloud run.

After your first task is admitted, look at this card for your remaining hours and pilot end date. The dashboard warns when five hours or less remain.

Barge reserves hours while a worker runs. When the worker stops, Barge returns unused reserved hours and records the actual runtime.

If the card or pilot end date is missing after your first task is admitted, stop and report the blocker. Do not assume that a missing balance means unlimited compute.

Additional hours and unavailable compute

When your hours run out or your pilot expires, new compute is blocked and running workers are stopped. You can still access existing results. There is no automatic charge or paid conversion.

You can request additional hours through the blocker-reporting route using a public-safe request. An administrator can grant extra hours, but a grant does not extend an expired pilot. There is no promise that extra hours will be granted. Do not create extra accounts to bypass a limit, or send payment details or provider credentials in a request.

If a start, retry, or follow-up is refused, read the error and review existing sessions before trying again. Retrying can incur provider charges and use more of your worker hours. Keep your GitHub PR links so you can review already-pushed results independently.