What draws down the balance
A training job that fails because of Veri’s hardware or provisioning (
error.attribution is platform) has its cost credited back to the workspace automatically; the job shows the credit under refund. See Who the failure belongs to.
Every charge records which member launched the resource. In a team, each monthly statement on the billing page breaks spend down by member, and veri billing transactions shows the member on each debit.
See Deployment billing for deployment billing states and scale-to-zero behaviour.
Training job charges
A training job is charged once, when it ends, for its GPU time: from the moment its instance boots (setup and model download before the first training step included) until the job ends, at the per-GPU rate times the GPU count. Rates on the rate card are rounded to the cent; the charge uses the exact rate. The checkpoints and the final model the job keeps are billed separately, by the month (see Checkpoint storage and Model storage). The total is rounded to the cent. For example, an L4 job (exact rate $1.0462/GPU-hour, listed as $1.05) that boots in about 6 minutes and then trains for about 60 minutes is billed 3,948 seconds of GPU time: $1.15. A job that never gets a GPU is not charged at all. Cancel before training starts and you pay nothing. A job you cancel before it reachesrunning is not charged (no GPU time, and it has saved no checkpoint to store), and the job page and veri jobs get show “Cancelled before start, not billed”. A job cancelled after it reaches running is charged for its whole run, setup included.
Checkpoint storage
Checkpoints are kept until you delete them, so the GiB of checkpoints you keep are billed every month at about $0.03 per GiB-month, prorated by the days each checkpoint is kept in that month. A job that keeps no checkpoint, such as one cancelled before its first save, adds nothing. Checkpoints thatcheckpoint_keep rotation deleted are not charged. Deleting a job deletes its checkpoints and ends their charge. The final model a completed job keeps is billed the same way (see Model storage).
For example, a full fine-tune of a 4B model that keeps three 22.4 GiB checkpoints (67.2 GiB) for a whole month adds about $2.01 to that month; if it wrote them on the 16th of a 30-day month, about $1.00. The month is settled on the first days of the next month, like volumes. The first month billed is November 2026.
Model storage
A completed training job keeps its final model in Veri storage until you delete the job: the final checkpoint (for a LoRA run, the adapter) and, for a LoRA run, the merged weights a deployment loads. The GiB it keeps are billed every month at the same rate as checkpoints, about $0.03 per GiB-month, prorated by the days kept in that month from the day the job completed. A job that failed or was cancelled adds nothing. Saving the model to your library or deploying it does not add a second charge: both use the job’s weights. Deleting the job deletes its final model and ends the charge; the month you delete it in is not charged for it. For example, a full fine-tune of a 4B model keeps about 7.5 GiB of weights: about $0.22 a month, or about $0.11 for a 30-day month it completed on the 16th. Model storage is settled with checkpoint storage on the first days of the next month, as its own line. The first month billed is November 2026.Personal and team workspaces
Switch between your personal workspace and your teams from the sidebar. The billing page, the balance in the sidebar, and every CLI or API call follow the active workspace.
A team owner is a member with the admin role in the team.
A team’s balance is linked to the team itself, not to the person who created it. When a member is removed, work they launched keeps running and keeps billing the team; an owner can stop it. If the last member leaves, everything still running is terminated: its training jobs and deployments end as
failed with the reason workspace_empty, and their final usage is settled.Adding funds
Open Settings > Billing in the workspace you want to fund and choose an amount (minimum $5). Payment goes through Stripe Checkout; the credit lands on the active workspace’s balance as soon as the payment completes. To avoid running dry, an owner can turn on auto-reload: when the balance drops below a threshold you set, Veri charges the saved default card for a fixed amount and adds it to the balance.- Both the threshold and the reload amount are between $5 and $1,000.
- A saved card is required. Save one under Payment method first.
- Veri checks balances every few minutes and reloads at most once per hour per workspace. Pick a reload amount larger than an hour of your usual burn so a single reload covers you.
- If the charge fails (declined card, no card), the billing page shows the reason and the owners receive an email. Nothing is reloaded until the card is fixed.
Plans
Every workspace starts on Free. The Pro pack is a one-time purchase under Settings > Credits: $20 that lands on the workspace's balance as $20 of credit and switches the workspace to the Pro limits for 30 days. It is not a subscription: nothing renews. Buying another pack while one is active adds 30 days to the current end date. When the pack ends the limits return to Free on their own; the credit stays.
The pack applies to the workspace you buy it in. In a team workspace the credit and the limits land on the team, and the buyer’s team-workspace allowance and the team’s seats are raised.
veri whoami and GET /v1/me report the workspace’s plan (free or pro) and, while Pro, plan_until. The current limits of every plan are public at GET /v1/plans (no key needed). Need more than Pro? Contact support for Enterprise limits.
Budget alerts
An owner can set a monthly spend threshold under Spend alert. Veri emails when spend for the calendar month crosses 75% and again at 100% of the threshold, once each per month. For a team, every owner receives the email. Alerts are informational: they never stop work. To stop work at a limit, stop the resource or rely on the $0 rule below.Low-balance alert
Veri warns by email when a workspace balance runs low, because running work stops at $0. For a team, every owner receives the email. Alerts are informational: they never stop work.- Default: a one-time warning at $25, sent while training jobs, deployments or agent sessions are running and auto-reload is off. It is not sent again.
- Your own threshold: set an amount under Low-balance alert on the billing page to be warned every time the balance drops below it. A top-up back to that amount or above re-arms the alert.
- Veri checks balances every few minutes. An owner can turn the alert off on the billing page.
What happens at $0
Veri does not extend overdraft. Each workspace is enforced on its own balance:- While work runs, Veri counts the cost accrued since the last settlement against the balance, so a long job cannot outrun its credit before the next settlement.
- When the effective balance drops below $0, every running training job, deployment and agent session in that workspace is terminated and its final window is settled. Work in your other workspaces is not affected.
- Terminated resources show a reason of
insufficient_credits. Add funds, then launch again. A training job stopped this way is charged for the time its GPU ran, even if it had not reachedrunningyet: only a cancel you make is free.
hours_remaining at the current spend rate.
Submitting work without a billing account
Every workspace gets a billing account when it is created. If a workspace has none (for example, a team created seconds ago that Stripe has not indexed yet), creating a job or deployment, or starting or forking an agent session, returns402 Payment Required with the message No billing account is linked to this workspace yet. Open the billing page for that workspace once, or wait a minute and retry. Running work is never stopped for this reason.
Credit codes
Redeem a promotional or support credit code from Settings > Billing. The form shows which workspace the credit will land in; switch workspaces first if it is the wrong one. Through the API, pass the target explicitly:workspace_id credits the active workspace.
Each code can be redeemed once. Codes are issued in batches (one per event or promotion), and each batch allows one code per account and one per workspace. A second code from the same batch returns 409 with “You already redeemed a code from this batch.”, or “This workspace already redeemed a code from this batch.” when a teammate already redeemed one into that workspace. Codes from different batches stack.
Statements and history
GET /v1/billing/transactions (or veri billing transactions) lists every credit and debit on the active workspace’s balance, newest first. Each debit carries the resource id and the launching member in its metadata. The billing page groups the same history into monthly statements, with a per-member breakdown for teams, and offers a PDF for each month.
Volumes free tier
Storage is averaged over the month across every volume in the workspace. The first 512 GiB-months are free; usage above that is billed at $0.085 per GiB-month on the first day of the next month. A team shares one allowance; a personal workspace has its own.Deleting a team workspace
An owner can delete a team from Settings > Workspace. Deletion is refused while any job, deployment or agent session is active (a paused session counts), while a final settlement is still pending, while a refund on a job is waiting for review, or while the balance is negative. Stop the work and clear the balance first. Deleting also removes the team’s triggers, environments, secrets, skills and webhook endpoints. Leftover positive credit on a deleted team is not refunded automatically; contact support before deleting if you want it moved.Reference
GET /v1/billing/balance,GET /v1/billing/transactions,GET /v1/billing/burn_rate,POST /v1/credits/redeem: see the API reference.- CLI:
veri billing balance,veri billing transactions,veri whoami(shows the active workspace). See the CLI reference.

