Enterprise data lands in a dedicated company retrieval layer hosted for that organization, not in a shared tenant pool.
Mercury Enterprise · Parent Billing · Governed Rollout
One company memory lane, controlled upward flow, and a real executive command layer.
Mercury Enterprise gives every seat its own protected working lane, routes team data into the right department, and lets leadership see governed company-wide rollups from one parent account. Raw seat work stays private by default. Approved knowledge climbs upward into the company memory plane without leaking sideways.
Parent billing + seat issuance Department-scoped lanes One company memory plane Approved upward rollups Audit trail + budget controls
Each seat starts with its own protected workspace before anything is promoted upward into department or executive rollups.
Executives get governed dashboards, exceptions, and approved summaries instead of unrestricted subordinate memory access.
Company systems feed the correct lane
Customer channels and internal systems land in Mercury first, then the lane router and policy layer decide what stays seat-private versus what graduates into the company memory plane.
Inputs
Telegram WhatsApp Discord GitHub CRM Docs
Controls
Lane Router Policy Filter Seat Vault
Company Memory
Company Index
Data climbs up
Seats and departments keep their own operating memory, then Mercury promotes approved context upward into the enterprise memory plane. Lower tiers never read up. Higher tiers inherit rollups, escalations, and approved knowledge instead of raw subordinate vaults.
Top
CEO / President / Master View
Company-wide summaries, budget signals, executive escalations, and approved org retrieval.
L2
Department Heads / VP Lanes
Department memory, policy-bound retrieval, lane ownership, and controlled escalations upward.
L3
Managers / Team Leads
Working memory for teams, approved department context, and operating retrieval for active seats.
Base
Seat Vaults / Private Workspaces
Raw chats, files, actions, and notes stay inside the assigned seat until policy says they can move.
Company Memory Plane
Dedicated enterprise retrieval host
Mercury Enterprise is designed around one dedicated company memory host per org. That gives the company a single governed retrieval layer for approved cross-seat knowledge while still preserving private seat and department boundaries underneath it.
One org host A dedicated company memory lane gives leadership the org-wide context they need without flattening private seat memory.
Free + slow or paid + fast Enterprise can choose slower local embedding on the company host or a faster managed embedding lane billed separately.
Governance Rail
Policy, budgets, and audit around every promotion
01
Role-gated reads
Every enterprise read is authorized server-side before retrieval, rollup, or rendering happens.
02
Budget controls
Parent billing, org credit pools, seat defaults, and optional per-seat or department caps stay visible from day one.
03
Lane-aware rollout
Seat issuance, deployment waves, and model defaults stay separate from the normal single-server customer lane.
04
Immutable lineage
Shares, escalations, approvals, and vault events stay attached to the enterprise audit ledger.
Parent Account Checkout
One purchase creates the org command layer
Enterprise checkout creates the parent account, org defaults, seat order batch, rollout lane, and the shared billing view that leadership actually needs.
- Seat quantity, channels, provider, model, and rollout defaults are captured once at purchase.
- Owners manage seat assignment, reporting, and org credits after Stripe instead of repeating one-seat checkout loops.
- Recurring seat spend and one-time OCI credit packs stay separated cleanly for finance.
Dedicated Memory Host
One company retrieval layer per enterprise
Personal users can host memory on their own VPS. Enterprise customers get one dedicated company retrieval host so the org can build a coherent top-level memory plane with its own spend, ingestion, and retrieval controls.
- Slow + free local embedding stays available on the company host.
- Fast managed embedding can be billed separately for higher-throughput enterprise usage.
- Executive retrieval is driven by the org memory plane, not by direct seat-level vault reads.
Enterprise Provisioning
Rollout waves instead of seat-by-seat chaos
Mercury provisions enterprise seats through the same base runtime but with enterprise-specific rollout tracking, org isolation metadata, and lane-aware defaults.
- Seats are invited and activated in controlled waves.
- Company defaults can include OCI credits or BYOK-ready provider settings.
- Admin and owner dashboards both see real rollout state, not placeholder demos.
Executive Visibility
Leadership finally gets the right surface
The point of enterprise Mercury is not just more seats. It is giving executives a clean command layer: company knowledge, issues that climbed the hierarchy, and budgets that can be governed without breaking operator flow.
- CEO, president, and master views can see org-wide summaries and approved retrieval.
- Departments keep their own lanes instead of becoming one flat memory blob.
- The admin console stays aligned with the same real customer-facing enterprise model.
Enterprise Checkout
Enterprise Parent Account Checkout
One parent billing checkout creates the org, seeds seat orders, stages rollout waves, and keeps enterprise provisioning isolated from the normal single-server customer flow.