- A trial becomes the Business trial and keeps its end date. Every member gets a Basic seat, and what is left of the trial’s shared credits is split equally between them as their own trial credits, at least £5 each. An invitation still waiting gets £5 of trial credits when it is accepted.
- A complimentary plan becomes complimentary Business. Max and Pro seats stay as they are, and Approver seats become Basic seats. Each member then has their seat’s own monthly credits: the shared credits Hive gave the plan end, and any other credits in the pool move to the Owner, as below.
- In Change plan, once you choose Business, the Approver seats you pay for are added to your Basic seats, and a note under the seat cards says “Approver seats become Basic seats on Business.” You can lower the count before you preview.
- When the change applies, each member on an Approver seat moves to a Basic seat and keeps their access: they can now use everything in Hive, with a Basic seat’s own AI credits each month. They and the Owners and Admins are told, for example “Ana Silva now has a Basic seat”, and the audit log records each move. An invitation to an Approver seat becomes an invitation to a Basic seat.
- The Approver seats end with the move itself, not at the end of the billing period, so the move is one change rather than an upgrade and a reduction to make separately.
- Fewer Basic seats than people: the Approvers who have held their seat longest take the Basic seats there are, and the preview names who would be left without a seat and asks you to confirm.
Plans and prices
These are the prices of Starter, Team and Enterprise before Business went on sale. A workspace on one of them keeps these prices, for the seats it adds too, until it changes plan. Prices are per seat, a month:- Billed annually
- Billed monthly
Paid once a year, in advance: a Team Max seat is £900 a year.
- Annual billing saves about 17% compared with paying monthly.
- An everyday answer is a typical answer on Hive Auto, about 27 credits. Answers on stronger models, or that read long files, use more. See What a credit buys.
- Approver seats add no credits. A workspace can hold up to 2 Approver seats for each Pro or Max seat, on top of the plan’s range.
- Starter and Team need at least 1 Max seat. Enterprise starts at Team’s limits and credits, and its contract can change them.
- A solo founder on Starter with one Max seat: £49.
- A 10-person team on Team, with 6 Pro and 4 Max seats: 6 × £30 + 4 × £75 = £480, with 35,000 credits a month in the pool.
- A 25-person firm on Team, with 14 Pro, 6 Max and 5 Approver seats for the partners who only sign off: 14 × £30 + 6 × £75 + 5 × £5 = £895, with 65,000 credits a month in the pool.
Seats
Each member holds one seat. The seat decides what Hive does for them; their role decides what they can see, approve and change. What each seat costs is in Plans and prices.- An Approver opens only what is routed to them, and can ask Hive 10 questions a month about items routed to them, in the app. The seat never raises their role’s approval tier. See The Approver seat. On a move to Business, each Approver seat becomes a Basic seat: see Approver seats become Basic seats.
- Signals on a Max seat watches one mailbox, the holder’s own, once an Owner or Admin turns Signals on for the workspace. See Signals overview.
- A member without a seat can do nothing in the workspace. Owners and Admins choose and move seats on the Members page. See Team and workspace.
- Fewer seats than members move people first. When fewer Pro or Max seats are in force than members hold, members over the limit move to a free seat of the other type before anyone loses a seat: a Max member to a free Pro seat, and a Pro member to a free Max seat, which turns on Signals for them. They and the Owners and Admins are told. Owners keep their seat type first, then the members who have held theirs longest. A suspended member gets a seat back on their own type first and, on a paid plan, on the other type once one is free. See Team and workspace.
What each plan includes
The main differences between the plans. Per-seat figures count Pro and Max seats only, and Enterprise starts at Team’s figures.- Signals within these figures never uses the pool. Above them, it draws credits for each item, up to a cap you control. See Signals fair use.
- Postpaid overage lets work carry on once the pool is empty, billed afterwards at 1p a credit, up to a ceiling you set. See Postpaid overage.
- Hard limit: on Starter, uploads and indexing stop at the allowance. On Team, add-ons buy more. See Plan limits.
- Per-member and platform limits, such as Slack and Teams answers, images and AI client work, are in the Limits reference, which marks the figures that apply on these plans.
- Dictation: 5 hours per Pro or Max seat a month, then 1 credit a minute.
- AI client reads of Hive’s own records: 20,000 per Pro or Max seat a month, then 1 credit per 250 reads.
- Agent tests: 200 test credits per Pro or Max seat a month. They do not roll over.
Balanced background
On Team and Enterprise, an Owner or Admin can run a chosen Max seat’s Signals on Balanced models instead of Efficient ones. On the Members page, choose More seat options beside the seat, then Signals background; the seat then shows Balanced in the Seat column. A seat that changes type, whether an Owner or Admin changes it or Hive moves it when the plan’s seats change, goes back to Efficient, and an Owner or Admin can choose Balanced again once it is a Max seat. A Max seat suspended over the limit that gets its seat back as a Max seat keeps its choice. The extra cost comes from the pool, and Hive shows it before you switch: about 4,700 credits a month for a light mailbox, 12,400 for a typical one and 32,600 for a heavy one. If the pool runs dry, the seat goes back to Efficient and Owners and Admins are told.Bring your own key (BYOK)
On Team and Enterprise, Owners and Admins can add the organisation’s own OpenAI or Anthropic key in Settings → Workspace → Models. Ask and agents then send their model calls to your provider, which bills you for the tokens. On these plans Hive charges 1 credit per model call for its own part of the work, shown in usage as Own-key fee. Images, web search and Hive’s other services still run on Hive’s accounts and use credits as usual, and seat prices do not change. See Bring your own key.Add-ons
On Team, add-ons buy more of what the seats include, by the month. Starter sells none, and on Enterprise the contract sets these limits.- Settings → Billing → Add-ons compares what the workspace uses with what it has. If you go over, Hive tells Owners and Admins how many units would cover it. It never adds or charges for an add-on without you.
- Adding units takes effect at once, and you pay only for the time left. Removing units takes effect at the end of the month, on annual billing too.
- Add-ons are never discounted. Credits are not add-ons: buy them as credit top-ups.
- Client ledgers never count as extra connected accounts. See Accounting organisations.
- The Practice add-on for accounting practices, the Collections add-on and Deal rooms are not on sale yet.
Enterprise on earlier terms
An Enterprise agreement signed on these terms keeps them until it is renewed:- Seats: Team’s list price plus 15%, rounded to the nearest pound: £35 per Pro seat, £86 per Max seat and £6 per Approver seat a month.
- Minimum: £30,000 a year, with no platform fee.
- Volume discounts: 10% from 100 Pro and Max seats, 15% from 250, and up to 5% more for a multi-year term, capped at 20% in total unless Hive agrees otherwise. They apply to seats only.
- Credits: the same allowances as Team, released monthly. Committed credits cost 0.8p each from 1 million a year, or 0.75p from 10 million.
- Overage: 1p a credit, up to a ceiling set in the contract (by default 50% of the monthly contract value), invoiced with the monthly usage.
- More capacity: extra connected accounts, file storage and search index are set in the contract instead of bought as add-ons.
When you reach a plan limit
- Settings → Usage → Plan limits shows each limit, what the workspace uses of it and what raises it. See Plan limits.
- When a limit stops something, Hive says what the plan allows and how to raise it. Owners and Admins are offered the change that raises it, at most once for each limit in a billing period: Business, the plan sold today, since Starter and Team are no longer sold. Other members are told to ask an Owner or Admin.
- At the plan’s most Pro and Max seats (5 on Starter, 300 on Team), Add seats links to Business, which takes up to 300 Basic, Pro and Max seats. At Team’s 300 it points you to sales instead. For more Approver seats, add a Pro or Max seat first.
- When 80% of the period’s credits are used, or the forecast passes the pool, Settings → Billing → Credits suggests buying credits. Dismiss hides it until the next period.
The credit pool
Hive measures the work it does for you in credits. One credit is worth 1p. Every Pro and Max seat adds an allowance of credits to one shared pool each month, and everyone in the workspace draws on it. What a seat already includes, such as each Max seat’s Signals within fair use, never touches the pool. Owners and Admins see the pool at a glance and buy credit top-ups in Settings → Billing, and see the workspace’s usage, each member’s cap and the Spend controls in Settings → Usage. Every member can see their own use and limits in Settings → My usage.What the seat covers
These never draw on the pool:- Signals within fair use for each Max seat: finding what needs attention in their accounts, matters, watches, and prepared replies and actions. See Signals fair use.
- Business Brain upkeep.
- The first read of a newly connected account, up to the seat’s account allowance in any 90 days (3 accounts on Starter, 6 on Team and above, 2 during the trial), with the indexing of what it reads, and indexing your connected sources within the plan’s monthly page allowance. Identical files, such as a logo attached to many emails, count once against the page allowance and are charged at most once a billing period. A further first read uses credits from the pool at measured cost, about 100 to 450 credits an account, within the member’s monthly credit limit and the workspace’s maximum monthly spend, and Connectors says so before you connect it. An account connected before its member held a Max seat is never charged for its first read: beyond the included ones, it waits for one to be free. An account connected before your workspace’s first plan or trial began is read in the seat without using an included first read, and is never charged. One that waits for credits or a limit raises a Needs you card for the member and for Owners and Admins, saying what lets it go ahead; the card clears once the account is read, however the read is paid for, when the account is disconnected, and when its member leaves the workspace or, at Signals’ next hourly pass, no longer holds a Max seat.
- File storage and the search index within your allowance.
- Approving, denying and undoing actions, and the audit log.
- Dictation: 5 hours per Pro or Max seat a month, shared across the workspace.
- AI clients reading your data: 20,000 database-only reads per Pro or Max seat a month, shared across the workspace.
- Agent test runs in Agent Studio, from 200 test credits per Pro or Max seat a month. Test credits do not roll over, and a test run larger than a preview (an agent allowed more than 5 model calls, or a call over 100,000 input or 8,000 output tokens) draws on the pool. Workflow test runs are not covered: they draw on the pool like live runs.
What uses credits
Everything else Hive runs on its own model accounts draws on the pool:- Ask, in the app or in Slack or Teams.
- Agents and workflows, from any trigger, including drafts, shadow runs and workflow test runs. Usage lists workflow test runs as Workflow tests, apart from live Workflows. An agent that only shadows (its highest rung is Shadow) runs on an Efficient model, unless your workspace’s model allowlist leaves the Efficient model out; then it runs on the model you chose for it.
- Building and evaluating: the agent and workflow builders, the skill drafter and evaluation runs. The builders, the skill drafter, evaluation judges and chat summaries run on Hive’s Efficient model, with no model to choose.
- Deep research and images.
- Public agent links and public forms, from a public budget of at most a quarter of the month’s included credits.
- Signals above fair use, up to each member’s Signals cap.
- Indexing beyond the allowance, on a paid plan: 67 credits per 1,000 text pages, and 779 per 1,000 scanned pages. A trial is never charged for indexing: past its page allowance, a file is stored but not indexed. Each 1,000-page block is charged once: a file whose pages fit in a block already paid for this month is indexed with no further charge. If the credits for a file’s pages are not there, the file is stored but not indexed, and Hive does not read a scanned file or image with its vision model. A file you attach to a chat is the exception: Hive always reads it, so you can ask about it, even when it cannot be indexed. A later read of the file, for example after it changes, checks again. A document that is not indexed because the credits ran out does not use up the page allowance; it counts once if it is indexed later. Each file is counted and charged at most once a billing period, however often Hive reads it again.
- Dictation beyond the allowance: 1 credit a minute.
- AI client reads beyond the allowance: 1 credit per 250 database reads. Reads that call a connected app or another service are measured from the first call.
- Your own model key: on Team and Enterprise, 1 credit per model call for orchestration. The model call itself counts no credits in your usage, because your provider bills its tokens; usage shows only the fee, as Own-key fee. See Bring your own key.
What a credit buys
Typical credits for common actions:
£100 (10,000 credits) buys about 370 everyday answers on Hive Auto, or about 830 on efficient models. An everyday answer is a typical answer on Hive Auto, and it is how Billing and plans shows what each seat’s credits do.
Annual plans keep their rates for the term. On an annual plan, the credits an action uses stay at the rates in force when your term began. A lower rate applies at once; a higher one waits for your next term, unless a model provider raises its own list price by more than 15%.
Rate rises come with 30 days’ notice. Hive publishes a rise in the credits an action uses at least 30 days before it takes effect, and tells Owners and Admins in the Inbox (under Needs you), by email and, if they have linked Slack or Teams, as a direct message. The notice names the models affected, the day the new rates start, and whether each rise applies on annual plans too. This notice cannot be muted. A rise never takes effect sooner than 30 days after Hive first sent that notice: if the notice goes out later than planned, the old rates stay until 30 days after it, and the notice gives that later date. One rise is scheduled: from 1 January 2027, work on Gemini 3.8 Flash uses about twice the credits, because Google’s introductory price ends. That is a provider rise of more than 15%, so it applies on annual plans too.
Your choice of model changes the rate. Hive groups models into three tiers: efficient, balanced and frontier. Hive Auto picks a model for each chat turn: short, routine questions go to the workspace’s Fast model and longer or harder ones (coding, research, analysis) to its Powerful model. An admin chooses both under Auto mode in Settings → Workspace → Models, and can then make Hive Auto the Default chat model. Until then, chats use the deployment default. Hive Auto’s Fast model must be an efficient model, or a custom or unpriced model that only your organisation’s own key runs; see Hive Auto’s Fast model. The credit figures above assume a balanced Powerful model. When you pick a model yourself, the model picker shows how much faster it uses credits than Hive Auto: about 2.7× for a balanced model and about 7× for a frontier model.
Large actions ask first. Before an action estimated at more than 500 credits (£5) starts, such as exhaustive research or a large company overview, Hive shows the estimate and asks you to confirm, and the action is then held to the estimate you confirmed. A workflow run or form submission that could take more than 50 agent steps asks too, and a scheduled, app-event or public-form run pauses before its 51st until an Owner or Admin approves it. See Runs past 50 agent steps.
Allowances
Each Pro and Max seat adds its allowance to the pool every month:
Every member holds one of these seats. An Approver seat is paid but adds no credits: the questions an Approver asks about items routed to them are paid from the pool. A workspace on the earlier Business plan keeps its own allowances.
When credits arrive
- Monthly plans get the month’s credits when that month’s invoice is paid.
- Annual plans release the allowance one month at a time. Once the annual invoice is paid, the workspace can also draw up to two further months ahead, so three months’ credits can be available at once.
- Invoice terms: a workspace that pays by invoice gets the credits when the invoice is issued, without waiting for its payment terms. If that invoice is voided or written off, Hive takes back what is left of those credits (any that work running at that moment is counting on, once it finishes), and gives it all back if the invoice is paid after all. Card payments add the credits when the payment goes through.
- A seat added part-way through adds a prorated allowance when its prorated charge is paid by card, or when it is invoiced on invoice terms. The allowance follows the seats added, not the amount charged, so a negotiated seat price or a discount does not reduce it.
- A seat changed part-way through follows the money. Changing a Pro seat to a Max seat adds the difference in allowance for the rest of the period, or of the annual term. Changing a Max seat to a Pro seat within the first 60 days of an annual term credits you the price difference, and takes back the difference in allowance for the rest of the term. Credits from that difference that were already used, this month’s or months drawn ahead, are taken from the term’s later months instead; if those cannot cover it, the rest comes off the next allowance the workspace is granted. Until then, Settings → Usage and Settings → Billing → Credits show the credits still owed back. Changing a seat back and forth never adds credits. An upgrade adds only the difference between the plans’ allowances, whatever price the seats were on. Moving from monthly to annual billing likewise takes back the unused part of the month’s credits, along with the unused part of the month’s price, for seats added earlier that month too: their credits for the month are granted once.
- A trial has its own trial credits, described in Trial and payments.
Rollover and expiry
- Monthly plans: unused included credits roll over for one month, up to one month’s allowance. They roll over even if a payment is overdue at the renewal. Rolled-over credits stay tied to the invoice that paid for them: if that invoice is later refunded, lost in a payment dispute, or voided or written off unpaid, they are taken back with the rest of its credits.
- Annual plans: unused allowance lasts until the end of the annual term. It does not roll into the first month after you move to monthly billing.
- Credit top-ups last 12 months and survive plan changes. Changing to Business moves what is left of them to the Owner’s own credits, with the same expiry: see What is left in the pool moves to the Owner.
- Refund credits for failed runs last 12 months.
- Trial credits end with the trial, and test credits do not roll over.
Which credits are used first
- Credits that expire this period, such as rolled-over credits.
- This period’s included credits (on annual plans, the released months first, then the months drawn ahead).
- Bonus credits, such as credits from an offer, refund credits for failed runs and credits Hive has added.
- Credit top-ups and Enterprise committed credits, soonest-expiring first.
- Postpaid overage, on plans that have it, up to its ceiling.
- Then work that needs credits stops, as described in When credits run out.
Credit top-ups
During the trial, Credit top-ups says only that top-ups open once you choose a plan, and a complimentary plan does not show it. On an active paid plan, buy more credits at any time in Settings → Billing → Credit top-ups:- Top-ups are charged as a one-off invoice to the payment method on file: the default you set under Payment, address and VAT, or else the card you subscribed with. With neither, you pay through a secure checkout; back in Hive, Credit top-ups says the payment is being confirmed, so there is no need to buy again. The credits arrive when the invoice is paid.
- One at a time. A top-up’s credits arrive when its payment goes through, so the pool can still look empty just after you buy. While an earlier top-up from the last week is still on its way, Hive says so and links its invoice instead of buying again; choose Buy another anyway if you need more credits before it arrives. Auto top-up waits for it too.
- Payments your bank wants confirmed. If your bank asks you to confirm a card payment and you leave it unfinished, no credits arrive until you do. Buying again then says the earlier top-up is waiting for its payment to be confirmed, with a link to finish paying it. Choosing Buy another anyway instead cancels the unfinished one, so you can never pay for both. Any top-up bought later cancels it the same way, auto top-up included.
- Not while the subscription is ending. Once the subscription is cancelled and set to end, top-ups cannot be bought, because the workspace becomes read-only when it ends and could not use them: Credit top-ups shows the end date instead. Reactivate the subscription in Settings → Billing → Plan to buy one. Once it has ended, it can no longer be reactivated: choose a plan again to buy top-ups. An Enterprise agreement’s term end is not a cancellation.
- They last 12 months, survive plan changes and are never discounted. Changing to Business moves what is left of them to the Owner’s own credits, with the same expiry.
- Declined payments: if the card is declined, nothing is charged and no credits are added. Update the payment method under Payment, address and VAT, then choose Confirm purchase again.
- Refunds: a top-up none of whose credits have been used can be refunded in full within 14 days of purchase, from the same page. See Refunds for how account credit and failed refunds are handled.
Auto top-up
Auto top-up is off by default. When an Owner or Admin turns it on, Hive buys a 5,000-credit top-up (£50) whenever the pool falls below 500 credits, up to a monthly ceiling you set. Each top-up counts toward the calendar month it is charged in, so no month is charged more than the ceiling. The ceiling starts at a suggested £50 a month on Starter and £100 on Team, which you can change. On an annual plan, the months you can draw ahead count as part of the pool, so no top-up is bought while they last. The ceiling must cover at least one top-up (£50) and can be at most 5 times your monthly seat bill, on every paid plan, invoiced ones included. If you later remove seats, auto top-up stops at 5 times the new seat bill even if the ceiling you saved is higher. Turning auto top-up on, or raising the ceiling, while the pool is already low buys a top-up straight away. Public links and forms never trigger an auto top-up. It is paid like any top-up, from the payment method on file, and buys one top-up at a time: the next waits until the last one’s credits have arrived. If the payment is declined, needs you to confirm it, or there is no payment method on file, auto top-up turns itself off and Owners and Admins are told. A top-up of its own that needs confirming is cancelled straight away, because nobody is there to confirm it, so it can never be paid as well as the top-up bought once auto top-up is back on. Once the payment method is fixed, turning auto top-up back on makes a new payment for the top-up, with the payment method now on file; it never repeats the declined one. Auto top-up also stops in three other cases, and Owners and Admins are told each time:- A disputed payment. While a payment to Hive is disputed with your bank (a chargeback), auto top-up is paused: it stays on but buys nothing, so the payment method in dispute is not charged again. It carries on once the dispute is resolved in Hive’s favour. If the dispute goes against Hive, auto top-up turns off.
- A cancelled subscription. When the subscription is cancelled, however it was cancelled, auto top-up turns off and cannot be turned back on until the subscription is reactivated.
- An ended subscription. Auto top-up turns off when the subscription ends, so it never starts buying again on its own when the workspace subscribes again.
Postpaid overage
Starter and monthly Team plans always stop when the pool and top-ups are used: you never receive an overage invoice. On annual Team, an Owner or Admin can turn off the hard stop in Spend controls. Work then continues past the pool as postpaid overage:- It is charged at 1p a credit, in arrears, and never discounted.
- It always has a ceiling: 50% of your monthly seat bill on Team. Hive works it out again whenever your seats, plan or billing interval change, so it follows the bill you pay now. A plan without postpaid overage turns the hard stop back on. When the ceiling is reached, work stops as it would with the hard stop on.
- Alerts go out at 50%, 80% and 100% of the ceiling.
- It needs a live subscription: if the subscription has ended, or Hive cannot add overage to it, the hard stop stays on and Spend controls says why.
- It is reported to Stripe every hour, and again whenever Stripe prepares an invoice for the subscription, so the overage used up to a renewal, a move off annual Team or a cancellation is on the invoice that change produces.
- Overage that reaches Hive after the invoice it belongs on was made is billed on a separate invoice at the same 1p a credit, due in 30 days: overage used in the last minutes before your subscription ends, overage used just before a change you pay for at once by card (see below), overage used after a plan change took the overage price off the subscription, or, rarely, overage recorded late for a billing period already invoiced. Each separate invoice gathers every such hour Hive found at once, and says which case it is. Stripe emails it to your billing email address.
- A change you pay for at once by card, such as added seats, also bills the overage Hive has reported so far in the month. Hive reports each hour’s overage once the hour ends, so the overage of the hour you make the change in (and of the hour before, if it was not reported yet) comes after that invoice: it is billed on a separate invoice of the same kind, as used before a plan change. If the payment for the change does not go through and the change lapses (it waits a day for the payment), Stripe drops the overage that was on the change’s invoice, so Hive bills it overnight on a separate invoice of the same kind, which names the plan change invoice it replaces.
Spend controls
Owners and Admins set these in Settings → Usage → Spend controls:
An Owner or Admin can also give one member a monthly cap of their own in Settings → Usage → Member caps: choose Change cap, enter the credits and Save, or choose Use the default to go back to the workspace’s member cap.
Each workflow also has its own monthly credit limit: by default 2,000 credits on Starter and Team, and 10,000 on Enterprise.
Other limits protect the pool without any setting: AI clients can start at most 500 credits of work per member a day; one answer can create at most 4 images; and on Team and Enterprise, and during the trial, each member can run up to 20 exhaustive research runs a day (Starter has Quick and Standard research only).
Usage alerts and forecast
- Alerts go out at 50%, 80% and 100% of the pool, of the public budget and of every ceiling: any overage ceiling, the workspace’s maximum monthly spend, each member’s monthly limit, each agent’s monthly limit, each workflow’s monthly credit limit (for a workflow with Usage alerts on in its settings) and the auto top-up monthly ceiling. Spend controls shows these thresholds but has no setting for them. Alerts go to Owners and Admins in the Inbox, by email and, if they have linked Slack or Teams, as a direct message. A member’s alert also reaches the member, and a workflow’s alert reaches the workflow’s owner. An agent’s alert names its limit, not the agent: Agent Studio shows which agent used the credits. Each can mute Usage alerts for themselves in Settings → Notifications, which also stops the email. During the trial, alerts say to choose a plan; on a complimentary plan, they say to contact Hive support, since neither can buy a top-up. Notices about the trial, payments and offers cannot be muted.
- A month-end forecast appears from day 7 of each period, projecting where usage is heading. On an annual plan it measures this month’s use against the credits you can still use: what is left of the months released so far plus what this month has used. For a period or trial that began before 12 October 2026, when Hive began taking payments, the credits used this period, the forecast and the suggestion to buy credits count from 12 October, measured the same way: what is left plus what has been used since.
See your usage
Settings → Usage shows Owners and Admins the workspace’s usage, this month and before:- Plan limits: each limit of your plan with what the workspace uses of it (see Plan limits below);
- This period: the credits available now and held by work that is running, what has been used against the pool, the month-end forecast, a Signals above fair use line, and any credits still owed back from an earlier seat change, which the next allowance repays first. A workspace with unlimited usage sees Unlimited usage and the credits used this period instead, covered by unlimited usage with nothing drawn from the pool, and no forecast;
- Credits used by month: a chart of the last 12 months, this month so far, with the monthly average drawn across it and, from day 7, this month’s month-end forecast as a dashed bar. Hover a month for its figures, or choose it to see its breakdown. Until the workspace has used any credits, it says No credits used yet;
- Breakdown: credits used over This month, Last month, the Last 3 months, the Last 12 months or any dates you choose, by member, product area, model, where the work ran or day, each row with its share of the credits used. Work no member started (scheduled, public and system work) is listed as No member, and per-item charges that use no model, such as web search, app reads and indexing, as No model. When two members have the same name, each one’s email shows beside it. You can download it as a CSV file;
- Member caps: for each member, the credits they have used this period against the credits their seat adds to the pool, and against their cap, as a bar. During the trial it says member caps start when you choose a plan, and on a workspace with unlimited usage that they do not apply;
- Credits in the pool: the pool’s balance by source: included, rolled-over, top-up and bonus credits, and when each expires. Only credits released so far are listed; on annual plans, the months still to be released this term are shown as one figure beneath, and any other credits held for later (such as committed credits or credits Hive has added ahead) are named with the date they become available, or with how much arrives on each date when they arrive in instalments;
- Spend controls. On a workspace with unlimited usage they are not applied, and the section says so; they take effect if unlimited usage ends.
Plan limits
Plan limits, at the top of Settings → Usage, lists each limit of your plan with what the workspace uses of it now, or so far this period:
Each row says what happens past the limit: the next one is refused, Signals above fair use draws credits from the pool, or an add-on your plan sells covers it. A bar turns amber from 80% and red at the limit. Each row also says what raises the limit: Business, the plan sold today, which has no limit on accounts, file storage, the search index, workflows, agents, schedules, app-event runs, links or forms and takes up to 300 seats; an add-on your plan sells; or Talk to sales once Business cannot. Signals above fair use offers no plan: it draws credits. When a limit is close or reached, Owners and Admins get Upgrade to Business, which opens Change plan on Business, or an Add link to the add-on in Settings → Billing. A figure Hive can’t read at that moment says so instead of showing 0. During the trial, which carries Team’s limits, what the trial does not include reads Starts when you choose a plan and is the only thing offered, with Choose Business. The trial’s connected accounts, file storage and search index count the Pro and Max seats your members hold. A complimentary workspace is offered nothing: it changes what it includes with Hive.
On Starter, file storage, the search index and connected accounts stop at the allowance, because Starter sells no add-ons. An upload that would take the workspace past its storage allowance is refused (Library files, files added to chats and projects, and generated images alike). A file whose pages would take the search index past its allowance is stored but not indexed; a file you attach to a chat is still read, so you can ask about it. Connecting more than 3 accounts per Pro or Max seat is refused, and the accounts already connected keep working. Remove content, disconnect an account or move to Business to add more.
When credits run out
An empty pool never switches Hive off:- Each Max seat’s Signals keeps working within fair use, because it is part of the seat. Above fair use only the priority lane runs.
- Every member on a Pro or Max seat keeps 10 quick answers a day and 200 a month (days and months in UTC): short answers on an Efficient model, which can make one round of searches of your workspace’s knowledge, Business Brain and Signals, with no web search or attached files. Quick answers start as soon as the pool, or the member’s monthly limit, has too little left to pay for a full answer on the model the question runs on, so they also cover the last few credits, not only an empty pool. Ask says how many are left. An answer that fails before the model starts uses none of them. A member on an Approver seat has none.
- Paused until credits return: other Ask answers, agents, workflows, research, images, and public links and forms.
- Scheduled and connected-app-event runs wait for up to 72 hours and start by themselves when credits return. On an annual plan, the months you can draw ahead still count as credits, so runs do not wait while they last. A workflow with no AI step uses no credits and never waits, and a schedule keeps one run waiting at a time, so it runs once to catch up rather than once for every time it missed. After 72 hours a run stops waiting and does not start by itself: Owners and Admins get a Run when credits return? notice under Needs you. In Settings → Billing → Runs waiting for credits, choose Run when credits return and the run starts as soon as credits are back. The run’s owner can choose it too.
- Adding credits is one click away: on an active paid plan, Owners and Admins see a button in Ask that buys a 5,000-credit top-up at the price it shows, charged like any top-up. Add credits opens Settings → Billing for the other packs. A top-up does not lift a member’s monthly limit, so a member at their own limit sees Raise your limit in Settings → Usage instead.
Quick answers do not need credits, so they keep working in the first four cases. A read-only workspace has none until it is active again.
Failed runs
When an agent run, a workflow run or a public agent exchange fails because of a fault on Hive’s side, Hive gives back the credits it was charged, automatically. They arrive as refund credits, which last 12 months like a top-up.- Only what the run took from your paid credits (and any overage) comes back. Test credits a preview used, trial credits, work on your own model key or included with a seat, and anything past what your credits could cover were never charged, so they are not refunded.
- Each run is refunded once. If a refund cannot be made straight away, Hive retries it on its own until it is made.
- If Hive has to run a workflow step again on its own, for example after a restart, the credits the first try used come back in full, outside the month’s 5%, and the same credits are never returned twice.
- Refunds in a month add up to at most 5% of the credits your workspace used that month.
- These are charged as usual: a run that ran out of time because of its own size, a run you stopped, and a run a limit stopped (an agent run shows why). So is an agent run or public agent exchange the model rejected or refused, for example because its input was too long for the model or broke the model’s content policy; a model provider being down is still refunded, and so is a timeout or error in Hive’s own systems, such as its database timing out or a connected app’s API failing one of the agent’s actions. In a workflow, so is a step a model failed: it refused, its answer was cut off or did not fit, or it stayed unavailable after Hive’s retries.
- Workflow test runs are not refunded.
Signals fair use
Within fair use, a Max seat’s Signals never touches the pool:
Enterprise starts at Team’s fair use. Starter’s fair use is sized for a lighter mailbox. Signals watches one mailbox for each Max seat, the holder’s own (see Mail detectors). Fair use belongs to the seat: moving a Max seat to someone else during the month does not start it afresh. If a member on a Max seat leaves and nobody takes their seat, what they used stays with that seat, and the other Max seats keep their own fair use.
Above fair use, Signals keeps working from the pool, up to each member’s Signals cap (2,000 credits, or £20, a month by default; admins can lower it to 0):
- 1 credit for each new item analysed;
- 11 credits for each prepared action;
- 12 credits for each prepared client reply.
Related
Billing and plans
Business and Enterprise: seats, prices and the execution add-on.
Credits and usage
Each member’s own credits, extra usage and workflow runs on Business.
Trial and payments
Checkout, plan changes, invoices and failed payments.
Limits reference
Every limit Hive enforces today.