Billing & Refunds
Effective 14 August 2026 · Version 3.0
This page explains exactly how NovaBuild charges, what a credit is, how each agent run is priced, and what happens when you upgrade, downgrade, cancel or ask for a refund. It sits alongside the Terms of Service, which governs the commercial relationship.
Plain language summary
- You pay for a plan, and metered work is drawn from credits.
- Free workspaces receive a one time welcome grant with no refill. Paid plans include a monthly allowance that resets and does not roll over.
- Credit packs sit on top of the allowance and do not expire while the account is in good standing.
- Unused credit packs can be refunded within 14 days of purchase. Consumed credits and elapsed subscription time are not refundable.
- Cancelling keeps access until the end of the paid period.
The summary is for orientation only. The numbered sections below are the operative text.
1. What you are buying
Two things are billed. First, a plan, which sets your feature set, private project capability, member limits, support targets and included monthly allowance. Second, credits, which meter the compute we spend on your behalf: model tokens for planning and code generation, sandbox time for installs, typechecks and builds, and production deployments.
2. Plans
| Plan | Intended for | Projects | Credits |
|---|---|---|---|
| Free | Trying NovaBuild and building in public | Public by default | One time welcome grant, no refill |
| Pro | Individuals shipping real products | Private by default | Monthly allowance plus purchased packs |
| Team | Small teams with shared workspaces and roles | Private, with member roles | Larger monthly allowance, pooled per workspace |
| Enterprise | Procurement, security review and custom terms | Private, with controls | Committed volume under an order form |
Current prices, allowances and feature detail are shown in the app on the pricing page and in workspace settings, which is the authoritative source at the time of purchase.
3. Credit grants and allowances
- Welcome grant: a one time balance added when a workspace is created, so you can build something real before paying.
- Monthly allowance: added at the start of each paid billing period, and it expires at the end of that period without rolling over.
- Purchased packs: added immediately, consumed after the allowance is exhausted, and they do not expire while the account is active and in good standing.
- Order of consumption: allowance first, then the oldest purchased pack, so the balance that expires soonest is used first.
- Balances are per workspace, are not transferable, have no cash value, and are forfeited if the workspace is deleted.
4. How a run is priced
Each agent run is metered from three inputs: the model used, the number of input tokens sent, and the number of output tokens returned. Rates per million tokens are published per model in the app. Long conversations cost more because the context sent to the model grows, which is why starting a fresh thread for a new task is usually cheaper.
Worked example
A medium edit on a mid tier model sending 60,000 input tokens and returning 4,000 output tokens is priced from the input rate applied to 60,000 tokens plus the output rate applied to 4,000 tokens, rounded up to the nearest credit. The exact ledger entry for every run, including tokens and model, is visible in workspace credit settings.
5. What consumes credits
- Agent runs, including planning, code generation, tool calls and summaries.
- Automatic fix loop attempts that you asked for, or that follow from your own instruction to keep going.
- Long running sandbox sessions beyond the included allotment for your plan.
- Production builds and deployments.
- Image generation and other multimodal calls made on your behalf.
6. What does not consume credits
- Browsing the app, reading docs, opening projects and viewing previews that are already running.
- Retries caused by our own platform failure, which we do not charge for.
- Actions the interface explicitly labels as free.
- Failed runs that produced no model output because a provider rejected the request before processing.
If you believe a run was charged incorrectly, email billing@novabuild.dev with the run timestamp and project name. Where we made the mistake we credit the workspace.
7. Bring your own key discount
When a run uses a provider key you stored in the workspace vault, the model provider bills you directly and NovaBuild charges a reduced platform rate for orchestration, sandboxes and hosting. The reduced rate is shown in the app. You remain responsible for whatever the provider charges you, including any spend caused by an agent running longer than you expected.
8. Credit packs and the price ladder
Credit packs are sold in tiers, with the effective price per credit improving as pack size grows. The ladder in the app is authoritative. Packs are charged once, are added immediately on successful payment, and appear as a single ledger entry.
Spend controls
NovaBuild does not auto purchase credits for you. When a balance runs out, metered actions stop and the app prompts you to top up, so a runaway agent cannot silently generate an invoice.
9. Invoices, currency and tax
- Invoices and receipts are issued by our payment processor and are available in workspace billing settings.
- Prices are shown in United States dollars unless the app states otherwise, and your bank may apply a conversion fee.
- Prices exclude tax unless stated. VAT, GST or sales tax is added where required by your location.
- Business customers can add a tax identifier before purchase so it appears on the invoice. We cannot reissue an invoice to change the legal entity after payment.
- If you are required to withhold tax, the amount payable to us is grossed up so that we receive the invoiced sum.
10. Renewals, upgrades and downgrades
| Change | When it takes effect | Credit treatment |
|---|---|---|
| Upgrade mid period | Immediately | Prorated charge, and the higher allowance is added at once |
| Downgrade | At the end of the current period | Allowance drops at renewal, purchased packs are unaffected |
| Renewal | Automatically at period end | New allowance replaces the expiring one |
| Cancellation | At the end of the current period | Allowance expires, purchased packs remain until the workspace is deleted |
11. Failed payments and dunning
If a charge fails we retry over several days and email the workspace owner. Agent runs and deployments pause once an invoice is materially overdue, while your data stays readable and exportable. Access is restored as soon as payment succeeds. Accounts left unpaid for 60 days may be suspended, and after 90 days we may delete workspace content after notice.
12. Refunds
Credit packs
Unused credits from a pack purchased in the last 14 days are refundable in full on request. Partially used packs are refunded pro rata for the unused portion at the price you paid. Credits already consumed are not refundable, because the compute has been spent.
Subscriptions
Monthly subscriptions are not refunded for elapsed time. Annual subscriptions can be refunded pro rata for whole unused months within the first 30 days. If you cancel later, access continues to the end of the paid period.
Always refunded
- Duplicate charges and charges caused by a billing error on our side.
- Credits consumed by a defect in the platform, which we credit or refund at your choice.
- Any amount required by mandatory consumer law in your country, including statutory withdrawal rights.
Not refunded
- Credits consumed by runs you started, including runs that produced output you did not like.
- Spend on your own provider key, which is between you and that provider.
- Periods where access was suspended for breach of the Acceptable Use Policy.
Approved refunds are returned to the original payment method within 10 business days, and the corresponding credits are removed from the workspace balance.
13. Cancellation and deletion
Cancel at any time from workspace billing settings. Cancellation stops future renewals and keeps access until the end of the paid period. Deleting a workspace is separate and immediate, it removes projects, files, chat history and credentials from live systems, and it forfeits any remaining balance. Export what you need first.
14. Billing disputes and chargebacks
Contact billing@novabuild.dev first and we will investigate within 5 business days. Raising a chargeback without contacting us usually freezes the workspace while the processor investigates, which is slower for everyone. Repeated unfounded chargebacks may lead to termination and to a requirement to prepay.
15. Price changes
Plan prices and credit rates can change as model and infrastructure costs move. We give at least 30 days notice of a plan price increase before it applies to your renewal, and credit rate changes are shown in the app before they apply to new runs. Credits already in your balance keep their credit value, not a fixed token conversion, because provider pricing shifts underneath.
16. Fair use and anti abuse
Credit systems attract abuse. Creating multiple workspaces to farm welcome grants, manipulating referral rewards, sharing accounts, or using automation to consume compute for resale all breach the Acceptable Use Policy. We may reverse fraudulently obtained credits, refuse a refund tied to abuse, and suspend the accounts involved.
17. Contact
Billing and refunds: billing@novabuild.dev. Include the workspace name and the invoice or run reference so we can answer in one round trip.
This document is published by the NovaBuild team as general information about the service. It is not legal advice, and it is not a certification or an independent audit of NovaBuild or of any third party. If anything here is unclear, or you need a countersigned copy for procurement, email legal@novabuild.dev.