Roadmap

The gates we are building toward

Hive is not built feature by feature. It is built against a small number of gates, each one a claim we have to be able to prove before we move on. Every item further down this page is tagged with the gate it unlocks.

• Items on the roadmap55
• Shipped7
• Building now17
• Next19
• Later12

Ask Hive

One question, every system — grounded, cited and auditable. The surface everyone in the company touches first.

• Grounded answers with sources on every claim — ShippedRead across the connected stack and answer with the sources and the time it took, so an operator can check the work.
  Pilots
• Multi-source reads across the core stack — ShippedSlack, Gmail, Drive, Sheets, HubSpot and Xero in a single answer rather than one connector at a time.
  Pilots
• Generative artefacts, not just replies — BuildingThe spreadsheet, the doc and the deck built from the answer and handed back ready to send.
  Pre-seed
• Threads that remember the workspace — BuildingFollow-ups inherit the context, the decisions and the exceptions from earlier conversations.
  Pre-seed
• @-mention an agent from the composer — NextHand a question straight to a named agent, with the same approval boundary as any other run.
  Pre-seed
• Voice: dictation and back-and-forth — NextTalk to the brain hands-free, and have it talk back, for operators who are not at a desk.
  Seed
• Overnight runs from a single prompt — LaterSchedule the heavy pull once and read the result in the morning instead of waiting on it.
  Seed

Business Brain

The owned context: how the business actually runs, learned by doing the work rather than by being documented.

• Read-only connect and first context graph in a day — ShippedNothing to migrate. Hive maps the stack before it is ever asked to act on it.
  Pilots
• Entity resolution across tools — BuildingOne customer, one deal, one invoice — resolved across the CRM, the ledger and the inbox.
  Pre-seed
• Decision memory: the exception and the reason — BuildingCapture why an operator overrode Hive so the next run does not need the same correction.
  Pre-seed
• Export and delete workspace memory — NextThe memory is the customer’s: exportable and deletable on request, and never used to train shared models.
  Pre-seed
• Department brains with scoped access — NextFinance, revenue and ops each get their own slice, so adding a team never widens everyone’s blast radius.
  Seed
• Compiled context for repeat runs — NextThe first run thinks; every run after replays a compiled plan, halving the tokens the same work costs.
  Seed
• Cross-customer signal, private by construction — LaterThe groundwork for AGBI: learn from operational reality in aggregate without a workspace ever leaking into another.
  Beyond

Signals

The brain watching the business between questions — catching what slipped before anyone thinks to ask.

• Watchers over the connected stack — BuildingThe overdue invoice, the slipped deal, the handoff that stalled — surfaced without a prompt.
  Pre-seed
• Signal inbox with severity and a drafted action — BuildingEvery signal arrives with the recommended move already written, so the operator only says yes.
  Pre-seed
• Thresholds and quiet hours per workspace — NextOperators tune what is worth interrupting them for, by team and by time of day.
  Seed
• Signals into Slack, WhatsApp and email — NextDelivered where the team already works, with the approval inline. No new dashboard, no new tab.
  Seed
• Learned signals proposed by Hive — LaterIt notices the check you keep running by hand and offers to watch it for you.
  Series A

Agents

Custom agents for the recurring work, each with a provable identity and a receipt for every step.

• Step-by-step runs with receipts — ShippedEvery read, every check and every draft shown as it happens, and kept afterwards.
  Pilots
• Agents built from a plain-English brief — BuildingDescribe the job once. Hive turns it into an agent instead of asking anyone to configure one.
  Pre-seed
• Scoped identity and credentials per agent — BuildingAn agent gets exactly the access its job needs, and that access is auditable on its own.
  Pre-seed
• Hand-off between agents inside policy — NextOne agent passes work to the next without either of them stepping outside the approved boundary.
  Seed
• It finds the busywork, then builds the agent — NextHive spots the pattern you repeat every week and proposes the agent for it, ready to approve.
  Seed
• Agent Marketplace: publish and install — LaterProven agents packaged and shared across workspaces, so the layer compounds outside one company.
  Beyond

Workflows

The routine, described once and run the same way forever — or found and built for you.

• Builder with approvals, loops, lookups and guardrails — BuildingThe full step vocabulary — agent, brain, approval, loop, lookup and guardrail — in one canvas.
  Pre-seed
• One instruction, hundreds of operations — BuildingLoop a workflow over every record in a list and keep one receipt per row.
  Pre-seed
• Hive-authored workflows from observed work — NextIt watches the busywork, drafts the automation, and asks for a single yes to turn it on.
  Seed
• Publish workflows across the workspace — NextPromote a proven workflow so every team runs the same version, on the Pulse edition and up.
  Seed
• Industry workflow templates — LaterAccounting, wealth, legal, creative and managed IT starting points rather than a blank canvas.
  Series A
• Cross-department workflows on shared memory — LaterOne deal closes and four departments move, coordinated on the same context.
  Series A

Integrations

Plugged into everything the business already runs, read-first and write-on-approval.

• Core connectors, read-only — ShippedSlack, Gmail, Drive, Sheets, Calendar, HubSpot, Xero and Stripe — the stack most partners run on.
  Pilots
• Write actions on the core set, behind approval — BuildingSend, update and file inside the tools the team already uses, never without a yes.
  Pre-seed
• Past a hundred connectors — NextThe long tail of CRM, finance, support, ads and project tooling the mid-market actually runs.
  Seed
• Generic REST and MCP connector — NextReach anything without a first-party connector, so the tail is never a blocker for a pilot.
  Seed
• Customer- and partner-built connectors — LaterThe internal system nobody else has, connected by the customer rather than waiting on our queue.
  Series A

Trust & guardrails

The layer that makes it safe to hand over the keys — hard limits, not good intentions.

• Untrusted-input firewall on everything Hive reads — ShippedPrompt injection in an email or a document is quarantined before it can reach an action.
  Pilots
• Approval thresholds per action class — BuildingIt acts when it is sure and asks when it is not, at the boundary the workspace sets.
  Pre-seed
• Audit log with reversible actions — BuildingEvery action logged with who approved it, and undone from the same record.
  Pre-seed
• PII and policy checks as a workflow step — BuildingGuardrails available inside any workflow rather than only at the platform edge.
  Pre-seed
• GDPR DPA and subprocessor register — NextThe paperwork a European buyer asks for on the first call, published rather than requested.
  Pre-seed
• SOC 2 Type II — NextIndependent assurance over security, availability and confidentiality controls.
  Seed
• EU data residency option — NextHosted in Europe for teams that need the data to stay there.
  Seed
• On-prem and own-cloud deployment — LaterFor the strictest requirements, the brain runs inside the customer’s own boundary.
  Series A
• ISO 27001 — LaterThe second certification enterprise procurement asks for after SOC 2.
  Series A

Orchestration

One cockpit over every team, tool and agent — the difference between running a process and running the business.

• Inbox: everything waiting on a human — BuildingOne queue for every approval, exception and drafted action across the whole workspace.
  Pre-seed
• Live run view across teams — BuildingWhat is running, what is waiting and what failed, in one place, as it happens.
  Pre-seed
• Roles, permissions and per-department thresholds — NextDifferent teams get different autonomy, set by the people accountable for them.
  Seed
• Group and multi-entity view — LaterFor rollups and PE: every acquisition lands on the same operating layer and reports up.
  Series A

Platform

The foundation under all of it: models, access, and the ways the brain reaches the rest of your software.

• Model-agnostic routing with automatic fallback — ShippedThe best model for each job, and a live fallback when a provider degrades.
  Pilots
• Right-sized model per task — BuildingSpend matched to the difficulty of the work instead of the largest model for everything.
  Pre-seed
• Public API — NextConnect the brain to the customer’s own applications, with the same guardrails as the product.
  Seed
• Webhooks and an event stream — NextPush runs, approvals and receipts into the systems that already watch the business.
  Seed
• Self-serve onboarding — LaterGenesis without a call: connect, watch it learn, and turn the first routine on.
  Series A
• Mobile — LaterApprove, ask and read receipts from a phone, for operators who are rarely at a desk.
  Series A

How this is kept honest

Dated targets are targets, not promises: a gate moves when the proof arrives, not when the quarter ends. Anything marked Shipped is running for founding pilots today. Anything marked Building is in flight and has an owner. Next is scoped and unstarted; Later is committed but deliberately unscheduled, because we would rather move a date than ship a half-guardrailed action into someone's live business.

Nothing is deleted from this page when it ships — it changes status, so the roadmap reads as a track record rather than a wish list. If something you need is missing, or a date matters to your decision, tell us: hello@get-hive.ai. Founding pilots shape this list directly.

• Want it sooner? Apply for founding access — pilots set the order of the next gate.
• Backing the layer? The thesis behind these gates is on the investors page.
• Building it with us? The roles we are hiring for are on the careers page.