Billing

Billing is prepaid. You top up your org's balance, and OpenResearch deducts compute and storage charges as you use them. A non-positive balance blocks new hosted compute until you top up.

Where to find it

Open Org settings > Billing. The page shows your current balance, in-flight charges, current storage usage, and recent activity. Click Top up to add funds via hosted checkout.

What you're charged for

• Hosted compute — billed per millisecond a sandbox is running. Charges accrue continuously and post in whole-cent slices.
• Storage — logs and artifacts kept in R2. The first 50 GB per organization is free; anything above that is billed at $0.0165/GB-month on the overage only. Measured against your current footprint, accrued continuously.

Self-managed instances (RunPod, Lambda, anything you SSH into) are billed by your provider directly, not by OpenResearch — only the logs and artifacts they produce count toward storage.

The In flight tile on the billing page shows an estimate of charges accumulating on currently-running sandboxes since their last billed tick — useful when you want to know what a long run is costing you in real time.

Activity log

The Recent activity section shows every billing event: top-ups, compute and storage charges (with the time window they cover), refunds, and manual adjustments. Each entry shows the amount; positive entries add to your balance, negative ones deduct.

Running out of balance

OpenResearch checks your balance when you try to provision new hosted compute — a non- positive balance blocks the request and surfaces a top-up link. Already-running sandboxes keep going and can leave you with a negative balance; top up before starting more compute. Self-managed instances aren't gated by balance at all.