Pricing
Custom, and we mean it.
There is no number on this page because we do not have an honest one to put here yet. Here is exactly what we would need to know to give you one.
Why no price
We quote it on a call instead of guessing on a web page.
Individual seats on the consumer product are self-serve. Company-wide rollouts are not — pricing depends on seats, which systems you connect and how much history you want ingested, so we quote it properly on a call instead of guessing on a web page.
Those three variables are not marketing shorthand. Seats decide how many separate memories get built. Which systems you connect decides how much there is to read. How much history decides how long the first ingest runs and how large the stored extract is. A company with 40 people and one shared Drive is a different job from a company with 40 people and years of mail each. We would rather ask than publish a figure that is wrong for one of you. Two of those dials have fixed edges today, and you should know them before the call rather than after it: Drive is read on a five-year lookback with a ten-thousand-file ceiling per sync, and the mail window is set per person by us, not by you in a settings screen.
Three shapes
Pick the seat band. We price the rollout.
CustomTalk to us for a quote
Up to 25 seats
- Globus text chat for every seat, each with its own private memory
- Each person connects their own Google Drive and Gmail
- The shared company knowledge base, searched alongside their own files
- Agents granted per person from the admin console — they draft, a human sends
CustomTalk to us for a quote
Up to 100 seats
- Everything in Team
- A guided rollout: we sit with each team while they connect their accounts
- We load the shared company knowledge base from a Drive folder you nominate
- We set the agent grants with you rather than leaving them at the default, which is none
CustomTalk to us for a quote
100+ seats
- Everything in Business
- Self-host instead: Globus is published under AGPL-3.0, so you can read the source and run it on your own infrastructure — with the caveat below
- Anything on the list below is a build, not a switch — we scope it with you on the call, before you buy
What the tiers do not do is gate features. Every capability listed below is on every seat in all three bands. The bands differ by how many people we onboard and how much of the rollout we do with you. If that changes, this page changes with it.
One more thing we will say here rather than on the call: the agent fleet is ours. It runs Globussoft’s own desks and several agents are wired to our products. We make them visible and runnable to your staff, and they always draft for a human. They are not yet configurable per company, and a new agent for your workflow is a build we would scope, not a setting we would flip.
Included everywhere
What every tier includes.
Five things, on every seat, in every band.
01 A Globus for each seat
Every employee gets their own assistant with their own memory. The identity comes from a signed session cookie, every tool call carries that email, and every query filters on it in SQL. One colleague cannot read another’s files by asking nicely, or by guessing an id — a read by id is ownership-checked, not just filtered.
Chat on the corporate portal is text. Voice exists on the individual product and is not wired to this portal yet.
02 Drive and Gmail, connected per person
Each employee connects their own Google account. Drive files are listed, classified and extracted — Docs, Sheets, Slides, PDF, DOCX, XLSX, PPTX and the plain-text formats. Gmail is read on a rolling 90-day window by default, spam and trash excluded.
Google is the only connector on the corporate portal today. Telegram, WhatsApp and Teams exist in the product but are not wired to this host.
03 The shared company knowledge base
One reserved shared space that is unioned into every employee’s search and folded into every employee’s context. The assistant is told plainly that this block is shared and not private to the person reading it, which is the honest way round.
It starts empty. We fill it during rollout from a Drive folder you nominate — playbooks, SOPs, product one-pagers, whatever every desk should know.
04 Agents that draft, never send
Sixteen agents can be granted to a person, a team or everyone from the admin console. The default is none: an agent is invisible until someone grants it, and the grant is re-checked server-side on every run, so a hand-crafted request cannot reach one.
An on-demand run is forced into draft mode. It produces a draft for review instead of posting to a live channel. No agent sends mail to your customers.
One honest exception, because it is the assistant and not an agent: in chat, an employee can ask Globus to draft a reply in their own Gmail and then send that exact draft. It cannot compose and send in one move — only a draft it has already shown them. That is the single path where something we generated leaves your mailbox, and a person triggers it.
05 The right to walk away with it
The stack is open source under AGPL-3.0 at github.com/Build-With-Sumit/globus — server, scripts, schema, a Dockerfile and a compose file. If you would rather run it yourself than pay us to host it, that is a supported answer to this whole page.
We have not published an install-time claim for it, so do not expect a one-command deploy. Read the repo before you decide.
Not for sale yet
What is not included at any price.
Better said here than discovered on the call.
Does not exist today
- SSO or directory provisioning. No SAML, no SCIM, no Okta or Entra integration, no directory sync. Sign-in is a 6-digit code to a company email address.
- Per-seat self-serve billing. There is no seat counter, no seat limit, no card on file for a company and no invoicing inside the product. Billing is a conversation and an invoice from us.
- A compliance certification. No SOC 2, no ISO 27001, no HIPAA. We have not been audited, and we are not going to put a badge on this page that says otherwise.
- A customer-facing audit log. There is no screen an admin can open to see which employee asked what, which documents were read, or who ran which agent.
- Offboarding from the console. An admin can grant and revoke agents and set a person’s team and role, but there is no remove-seat button. Taking someone’s access away today is a manual change we make on the server.
- Voice on the corporate portal. The voice assistant is a feature of the individual product at the moment. Corporate chat is text.
If one of these is the thing that decides it for you, say so on the call. Some are a build we can scope. None of them are a switch we can flip this afternoon, and we would rather lose the deal than say otherwise and be found out in month two.
The process
How buying actually works today.
Four steps, none of them automated. That is the honest description, not a soft-launch euphemism.
-
A call
You leave your name, company, email, phone number and a good time on the contact page. That writes one row and pings us. We call you and ask about seats, which systems you want connected and how far back you want to go.
-
A scoped rollout
We agree what the first ingest covers and which teams go first. We register your company email domains against your organisation, and we load the shared company knowledge base from a Drive folder you nominate.
-
Manual invoicing
We invoice you directly for the scope we agreed. There is no in-product billing for a company, no seat meter and no self-serve upgrade. If the seat count changes, it changes on the next invoice, by conversation.
-
Seats enrol by company email domain
Anyone at a registered domain requests a 6-digit code, enters it, and is enrolled. The domain match is exact, and a code is only sent to a domain that belongs to your organisation. Everyone else is refused with an identical message, so the form cannot be used to discover who works for you.
The flip side is the one on the list above: enrolment is permanent until we remove it by hand. Ask us about that before you point 200 people at it.