Skip to main content
Short, honest answers to the questions teams ask most before and after they start using Hive. Each answer links to the page with the full detail.

Product

Hive is an AI operations layer for your business. It connects to the tools you already run, watches for work that is slipping — an overdue invoice, a stalled deal, an email waiting on a reply — explains what it found, and proposes a safe next step. You decide how far it may go: the member who owns each connected account sets it to Read, Draft or Act, and agents and workflows carry out only the actions you select for them. Start with What is Hive? and the quickstart.
No. Hive reads your systems in place through connectors. Nothing migrates. New accounts start on Act: in Ask and Signals, Hive takes the action and tells you what it did, within your workspace’s safety checks. Set an account to Draft to approve each of those actions first, or to Read so Hive only searches and summarises there. See Connect an app and Accounts and autonomy.
A signal is something Hive caught in a connected tool that is at risk of being missed, with the evidence behind it, why it matters and a proposed next step. You can act on it, snooze it or dismiss it. See Signals overview.
Yes, within your limits. Every action is a typed proposal that passes a deterministic policy check before anything runs. In Ask and Signals, the level of the connected account decides: on Act, where new accounts start, Hive takes the action and tells you what it did; on Draft it asks for your one-click approval; on Read it tells you what it found and takes no action. Money, legal and irreversible actions, and any action a safety check holds back, still become an approval card there. Each member sets the level of their own accounts; Owners and Admins can only lower it with a workspace ceiling. Agents and workflows follow the same level and ceiling: on Act they carry out the actions selected for them straight away, on Draft each one waits for approval, and on Read they take none. Even on Act, an action waits for your approval when where it sends came from something they read rather than from their instructions or your own words, as does a workflow at an Approval step. The kill switch, spend caps, the hourly action limit and credit budgets apply to all of it. See Accounts and autonomy and Autonomy and blast radius.
Owners and Admins can engage the Kill switch. It halts every autonomous action and approval across the workspace until someone resumes. See Safety and control.
Not necessarily. Hive can only raise signals from what it observes. Open the Matters tab to see what Signals has read from each connected account, and check the account’s tile in Integrations. To be told when something specific happens, ask Hive to keep an eye on it.
A workflow is a graph of steps that runs from one trigger — a button, a form, a public form, a schedule or an event from a connected app — and gets a version number each time you deploy it. An agent in Agent Studio is a specialised assistant you configure for a job, grounded in your Business Brain, that people use from Ask Hive, on a schedule or as a step in a workflow.
There is no webhook URL you can point at a workflow. A workflow starts from one of five triggers: Manual, In-app form, Public form, Schedule or Connected app event. A Connected app event trigger starts a run when an app the workflow’s owner connected sends an event, such as a new HubSpot deal — see Connected app event. To let any other outside system start a workflow, have it submit a public form through the public form API. Incoming webhooks feed Signals, not workflows — see Incoming webhooks.
No. Test runs execute the current draft with real models, but every action is shadowed: recorded as what it would have done and never sent. Past runs shows such a step as “Not sent: this was a test run”, with what it would have sent. Every button that tries your draft is called Test run and says so before it starts — Test run, Test run from here, Test run this step only, Test run full flow. To run the published version for real, use Run live now in the builder header; it asks you to confirm and lists the actions it will take in other apps first. See Test and deploy.
Yes, for conversation. Install the Slack or Teams channel, then mention @Hive or send it a direct message to ask questions. Signals and approvals stay inside Hive. See Slack and Teams.
Only about billing. Owners and Admins get an email when the trial is ending or has ended; when Hive sends the workspace an offer, and again three days before that offer expires; at usage alerts, unless they have muted usage alerts; when the plan or an add-on changes, or the workspace goes over an add-on’s allowance; when a subscription is cancelled or reactivated; when a payment fails; and when an overdue payment makes the workspace read-only. A usage alert about a member’s own monthly credit limit, or about a workflow they own, is also emailed to that member. Each also appears in the app. Stripe, Hive’s payment provider, emails receipts and invoices, and its own failed-payment notice. Everything else appears in the in-app bell, and your notification preferences filter what the bell shows.
Your own. Hive stores every time in UTC and shows it in the timezone your browser uses, so a run at 15:00 UTC reads 11:00 EDT in New York and 20:30 GMT+5:30 in India. Times that include a clock name their zone, and a time you type, such as when a publication expires, is read in your timezone. Calendar dates such as a billing period or contract term end name the same day for everyone. A schedule’s cadence follows the timezone set on that schedule. See Schedules and forms.

Data, privacy and security

No. Every record carries your workspace’s identity, taken from your verified session, and the database enforces row-level security on top of the application’s own filtering. See Security overview.
The Hive API runs on Fly.io in Frankfurt, and the database is Postgres on Supabase in Frankfurt (eu-central-1). The full list of providers is on Infrastructure.
OAuth tokens for managed connectors are held by our connection provider, Nango. Secrets Hive holds itself — MCP server tokens, webhook signing secrets and a bring-your-own model key — are encrypted with a key unique to your workspace (AES-256-GCM) and are never shown to an AI model. See Data protection.
Hive does not train AI models on your workspace’s content. Its own decision model for Signals is trained only on invented example mail. Your workspace has a Data sharing setting, off unless an Owner or Admin turns it on, that governs whether Hive may use your chat and workflow data to improve its product; content from Google services is never included. How each AI provider handles the requests it processes is governed by that provider’s terms; see AI and models for which providers are involved.
Hive staff signing in with a Hive company account can open a workspace. Hive staff open your workspace only when you ask, and each time is recorded internally. Otherwise they open it only when it is needed to keep Hive secure or to comply with the law.
Sign-in is handled by our identity provider, Clerk. Hive does not currently publish a SOC 2 report or offer SAML single sign-on configuration. Talk to your Hive account team about your requirements.
Deleting the workspace engages the kill switch, makes a last pass to delete files members had already deleted, stops scheduled work, and stops live updates from connected apps (the connections are kept, so a restored workspace keeps them). It also cancels the subscription at once, with no refund for the time left in the period, and voids the workspace’s unused credits. To keep using the workspace until the end of the period you have paid for, cancel the subscription in Settings → Billing → Plan instead, and delete the workspace after it ends. After 30 days, the workspace’s Business Brain is permanently deleted unless the workspace has been restored. Other workspace data is retained so that a returning organisation can be restored. Contact support if you need data removed: Hive completes a deletion request within 30 days. See Leaving Hive.

AI models

Hive works with models from OpenAI, Anthropic, Google and xAI. The model picker lists only the models available to your workspace, so the exact list depends on your configuration, and Admins can restrict it to an allowlist. When a provider retires a model, Hive stops offering it, and anything set up on it — a default or a saved agent — runs on the next model in the same tier instead. See Models.
Yes, on Business and Enterprise (and on Team). Owners and Admins add an OpenAI or Anthropic key in Settings → Models. Ask and agents then run their model calls on your key and your provider bills the tokens: on Business those calls use none of your AI credits, and on earlier plans Hive charges 1 credit per model call for orchestration. Seat prices stay the same. See Bring your own key.
They use credits faster. Hive Auto, the default, answers most questions on efficient models; a typical answer costs about 4.4p. When you pick a model yourself, the picker shows how much faster it uses credits, such as about 2.7× or about 7×. See What your credits buy.
Ask Hive answers with citations to the documents, emails, live reads, signals and Brain facts it used. If a live lookup failed, the answer ends with “Live sources were not checked” and tells you it relied on stored data. See Ask Hive.

Billing

Per seat, and every member holds one. Business is sold online and Enterprise by contract, after a 7-day free trial. Every seat has every feature and differs only in the AI credits it includes, which are the holder’s own:
  • A Basic seat, £19.20 a month billed annually (£24.00 monthly), includes £5 of AI credits a month.
  • A Pro seat, £59.00 a month billed annually (£73.75 monthly), includes £30 of AI credits a month.
  • A Max seat, £119.00 a month billed annually (£148.75 monthly), includes £60 of AI credits a month.
Every seat also includes 2,500 workflow runs a month, and the execution add-on adds more for the whole workspace. There are no free seats, and nothing else is limited. Prices are in GBP, excluding VAT. See Billing and plans.
Yes. A new workspace gets a 7-day trial of Business features, except workflows started by connected app events, your own model key and Balanced background, with no card required. Every member given a seat holds a Basic seat with £5 of AI credits and 2,500 workflow runs. There is one trial per business email domain, or per address on a personal email service such as Gmail, and a connected account can be used in only one trial. A workspace for a domain that has already had a trial starts read-only until you choose a plan. See Trial and payments.
Money for AI work: one credit is 1p, and each member has their own. Hive spends credits at what the work costs it, with no mark-up: a short answer on Hive Auto costs under 1p and a typical answer about 4.4p, so £100 buys about 2,200 typical answers. Approvals use none. On Starter, Team and the earlier Business plan, credits are a unit of work shared in one pool: see Earlier plans. See Credits and usage.
Not by default. Extra usage is off, so nothing is charged beyond your seats and add-ons. If an Owner or Admin turns it on, each member can spend only up to their top-up limit (£50 a month unless you set another) on top of their included credits, and the whole workspace only up to its monthly maximum (£1,000 to start, which you can change). Owners and Admins get alerts at 50%, 80% and 100% of that maximum. See Usage and spend limits.
A member who has used their included credits stops, unless the workspace has extra usage on: then they carry on up to their top-up limit. Other members keep their own credits. Scheduled runs whose owner has no credits left wait for up to 72 hours, and background work on that member’s accounts waits for a later pass. A member at their limit can ask for a higher one with Request a higher limit, if the workspace allows usage requests. During the trial, choose Business to go on. See When credits run out.
The workspace keeps working for 14 days while the payment is retried. On Business, members keep using the AI credits they have, while extra usage, schedules and app triggers wait; on earlier plans, work that uses credits pauses beyond each Pro or Max member’s quick answers. If the invoice is still unpaid after 14 days, the workspace becomes read-only until it is paid. Nothing is deleted. See If a payment fails.
Yes, on Business, Starter and Team, however you pay. An Owner cancels in Settings → Billing → Plan, and the subscription ends at the end of the current billing period, or of the annual term on annual billing. Until then it can be reactivated. Afterwards the workspace is read-only and your data is kept. An Enterprise agreement runs to the end of its term: contact your Hive team to change it. A workspace on the earlier Business plan changes or ends its plan with the Hive team too. See Cancel and reactivate.
Owners and Admins. Only an Owner can cancel the subscription. Other members see that commercial and payment data is restricted to Owners and Admins, and can see their own credits, extra usage and workflow runs in Settings → My usage. See Roles and permissions.
Yes, for organisations that need an annual contract, invoices, or custom prices, credits and runs, from £30,000 a year. See Enterprise.

Integrations

Accounting, payments, CRM, support, project, email, calendar and file tools — including Xero, Stripe, HubSpot, Gmail, Outlook, Jira, GitHub and Google Drive. See the integrations catalog.
Yes, if they hold a Pro or Max seat, once an Admin has enabled the provider for the workspace. Each connection belongs to the member who made it, and Admins see only metadata about members’ personal connections. See Accounts and autonomy.
Yes. Connect any MCP server by URL, or send signed events from any system with an incoming webhook. See MCP servers and Incoming webhooks.
Not today. The supported programmatic ways in are the Hive MCP server (for AI clients, signed in with OAuth as you), incoming webhooks and public workflow forms. See Build on Hive.
Hive syncs right after you connect, then on an hourly loop, plus realtime events where the provider forwards them. There is nothing to start by hand: Owners and Admins see when the next run is due at the top of the Signals page and on the Connectors tab in Integrations.

Troubleshooting

Fix common problems step by step.

Glossary

Every Hive term in one place.