Question 1

What does Mycelium actually ship?

Accepted Answer

A multi-tenant memory-layer runtime, twenty-three live connectors across Communication, Knowledge, Engineering, CRM, Business systems, and Data, a typed-memory schema, a bi-temporal RESOLVER, an HMAC-validated webhook receiver layer with retry queue and dead-letter routing, an append-only audit log with per-tenant scoping, and a Server-Sent Events stream. Open core under MIT for the substrate; commercial license for the productized runtime.

Question 2

If the open-source repo is free, what does Mycelium actually sell?

Accepted Answer

The free repo (ai-brain-starter, MIT) is the recipe. It teaches the pattern, you can clone it and run it on a laptop. Mycelium sells what the recipe doesn't include. The hosted runtime that runs 24/7 with HMAC-validated webhook receivers, tenant-scoped JWT auth, audit log, and dead-letter routing. That's the production-grade infrastructure no buyer wants to operate themselves. The install: connector configuration, knowledge-graph densification, integration with their stack, training the team. The custom connectors for systems the open core doesn't ship with. Same shape as Vercel and Supabase: Next.js and Postgres are open source, companies pay Vercel and Supabase to host, scale, and operate them. The repo is the recipe. Mycelium is the chef, the kitchen, the security cameras, and the guarantee it doesn't burn while you're in another meeting.

Question 3

What does it cost?

Accepted Answer

Four tiers. Free is the open-source substrate at github.com/mycelium-hq/ai-brain-starter, MIT-licensed, install-yourself. Personal is $15 per month on annual or $18 per month on monthly billing. Team is $25 per user per month on annual or $30 per user per month on monthly billing, with a 2-user minimum. Enterprise is Contact sales with multi-year prepay (three-year 15% off, five-year 20% off plus early access to vertical packs at GA). Specific usage rates and SLA terms named in the engagement letter after a scoping call. Custom consulting is a separate surface at mycelium-ai.co/consulting.

Question 4

Why don't you bundle inference like Perplexity?

Accepted Answer

Two reasons. Commercial: per-token resale is a margin trap (Cursor's path) that prices Mycelium out of buyers who already pay for Claude Pro or ChatGPT Plus. We sell the memory layer plus the workflow runtime; inference is a separate decision the buyer already made. Procurement: BYO inference makes Mycelium structurally model-portable. The same memory runs under Claude, GPT, Gemini, or your own model without re-migration. Hosted Pass-Through is available as an opt-in at Team and Enterprise when procurement specifically asks; default is BYO.

Question 5

Do you offer help with setup?

Accepted Answer

Yes, at the Consulting page (mycelium-ai.co/consulting). Three boxed tiers: Setup Package $15K one-time (30-day install, vault migration, custom connector configuration, team training, 60-day post-launch Slack support); Custom Engagement $25K-$100K scope-based for custom connectors or workflow design; Strategic Advisory $500-$1K per hour or $10K-$25K per month retainer for AI strategy, agent architecture, pricing, or fundraising narrative work. Adelaida's weekly cap is 10-15 hours; advisory has limited slots.

Question 6

How long does install take?

Accepted Answer

Personal is same-day activation through the 4-step onboarding wizard with a 10-minute time-to-value target. Team is admin install plus member onboarding under 5 minutes per user once the company brain is populated. Enterprise is 90 days with a dedicated install engineer assigned the full window, then 12 months of runtime. Setup Package adds a 30-day guided install for Team or Enterprise customers who want hand-holding.

Question 7

Can it run inside our cloud or on-premise?

Accepted Answer

Mycelium Enterprise yes: single-tenant managed runtime in your AWS, GCP, or Azure account, or fully on-premise inside air-gapped infrastructure. Personal and Team are multi-tenant managed only.

Question 8

What's your SOC 2 / HIPAA / GDPR posture?

Accepted Answer

GDPR: yes, the runtime is built to be processor-grade with the controls in our DPA. HIPAA: BAAs are negotiable on the Mycelium Enterprise tier; not in scope on Personal or Team. SOC 2 Type II: not certified and no audit has been commissioned. Vendor selection, engagement signature, audit kickoff, compliance-platform onboarding, and the observation period are pending. The /security page is the canonical status surface.

Question 9

Does it work with our existing AI stack?

Accepted Answer

Yes. Mycelium is model-agnostic. Memory lives as plain-text typed entries you own; agents under Claude, GPT, Gemini, Llama, or your own model read from the same layer. Vector stores like Pinecone, search tools like Glean, and orchestration platforms like LangChain are upstream or downstream of Mycelium, not replaced by it.

Question 10

What if a connector we need doesn't exist?

Accepted Answer

Custom connectors are scoped on Week 0 of a Mycelium Enterprise engagement. The connector becomes a skill in your tenant; the source is shared as part of the deliverable so you can audit, fork, or maintain it after handoff.

Question 11

Who owns the data? Can we export everything?

Accepted Answer

You own it. Tenant data lives as plain-text Markdown under your vault root, version-controllable in your own git remote if you choose. There is no proprietary database lock-in. Audit-log exports are available on demand as gzipped JSONL signed with a tenant key.

Question 12

What happens to our install if Mycelium goes away?

Accepted Answer

Open-core architecture is our answer to vendor risk. The substrate (schemas, RESOLVER specification, skill contract, eval framework, reference connector implementations) is open-source under MIT at github.com/mycelium-hq/ai-brain-starter. Your tenant data, schema, and skills survive in plain text. The productized runtime is replaceable with a self-hosted equivalent built on the open core. Same shape as the Vercel + Next.js relationship.

Question 13

How is this different from mem0, Letta, Glean, Pinecone?

Accepted Answer

Different category for each. mem0 / Letta / LangMem / Zep tune chatbot memory at the conversation layer. Pinecone / Weaviate / RAG frameworks search a corpus that already exists. Glean / Notion AI search what's already written. Mycelium is the typed, version-controlled, write-back memory layer those systems read from and write back to. The Comparison section earlier on this page maps the axes.

Certification	Status	Target	Last verified
SOC 2 Type II	Not certified; no audit commissioned	Vendor, engagement, kickoff, platform onboarding, and observation start pending	No engagement signed
HIPAA + BAA-ready	Risk assessment + technical safeguards documented; BAA template available	Active by Q3 2026	2026-05-04
GDPR + DPIA	DPA published, DPIA template available	Active	2026-05-04
Penetration test	Not commissioned; vendor selection and engagement pending	Kickoff pending signed engagement	No report available
ISO 27001	On roadmap	Q1 2027 if European F100 demand materializes	Roadmap
FedRAMP Moderate	On roadmap; required for federal AI memory layers by 2027 per government memo	Q4 2027	Roadmap
BYOK + per-tenant encryption keys	Customer-managed encryption keys on Enterprise tier; namespace-level scoping reserved for Hyperscale custom installs	Active (Enterprise); Hyperscale on-deal	2026-05-26
Deployment isolation	Shared-tenant default with RLS plus per-tenant audit log plus per-tenant rate limits; single-tenant available on Hyperscale custom installs	Active (shared-tenant); Hyperscale on-deal	2026-05-26

Trust Center

1. Where we are

2. How to read this page

3. Data residency

4. Audit cadence

5. Incident response

6. Security contacts

7. Subprocessors

8. Documents available on request