Corpus knowledge base
Ingest documents, pasted material or bounded public documentation. The retained source becomes searchable immediately instead of disappearing inside one agent session.
Corpus · sources · semantic retrievalFirekeep for teams · Coming soon
Your team’s working knowledge, available to your AI agents.
Firekeep for teams is the planned paid, multi-person edition of the same self-hosted Firekeep product. It will help teams carry recorded decisions, source material, reviewed procedures and session context across the AI coding clients they use.
Clear product boundary: Teams is not available yet. Solo is available now as the free one-person edition.
One knowledge layer across
CLClaude Code
CXCodex
KIKiro
OCOpenCode
The shared knowledge loop
Turn scattered work into reusable team knowledge.
Chat transcripts alone are not a knowledge system. Firekeep separates source material, learned operational memory and reviewed procedures, then retrieves the part that matches the work in front of an agent.
Built into Firekeep
Corpus, Cortex and reviewed Skills are implemented in the current Solo product. Teams is the coming-soon product for using that same knowledge loop across multiple people.
Cortex memory
Keep decisions, incident lessons and proven fixes that agents explicitly record, then retrieve relevant memories in later work through semantic and graph recall.
Cortex · evidence-backed recallReviewed Skills
When a generation model is configured, procedural material can become a draft for human review. Approved skills then participate in later recall; drafts stay out until reviewed.
Draft · review · approve · reuseContinuity across the work
Let the next agent inherit more than a ticket.
Firekeep connects the durable context around a task: what was decided, where work stopped, what changed and which agent is handling the next part.
- Bridge preserves explicitly recorded goals, plans, decisions, progress and file notes across interruptions and context compression.
- Relay coordinates agent identities through tasks, channels, direct messages, best-effort presence and renewable resource leases.
- Replay exposes recorded Firekeep events and nearby saved decision context when a team needs to reconstruct what happened.
Bridge
Recorded session shadow
restorableGoal · plan · decisions · files · next step
Relay
Work and coordination
shared stateTasks · messages · leases · catch-up
Replay
Inspectable event trace
traceableTool events · timestamps · nearby context
Board
Grouped human decisions
reviewableQuestions · evidence · visual comparisons
Your infrastructure
Share knowledge without surrendering the control plane.
Firekeep runs its server, datastores and default inference path on infrastructure you control. Teams is planned around the same self-hosted product and the same client gateway as Solo.
- One Firekeep connection for every supported coding client.
- Authentication enabled and application ports bound to loopback by default.
- Knowledge sources, session records and operational memory remain in your deployment.
- Symdex indexes code on each workstation and returns only requested tool output.
- Dashboard, encrypted Vault, Sentinel signals and policy checks stay part of the same platform.
One controlled deploymentself-hosted
One product · two stages
Start with one person. Bring the team when Teams is ready.
Solo is designed as the complete Firekeep product for one person, not a temporary feature trial. Teams will be the paid path for multiple people sharing Firekeep.
Firekeep Solo · free
The public Solo release provides the complete current capability set for one person on infrastructure you control.
- Unlimited personal agents, terminals and devices
- Corpus, Cortex, Skills, Bridge, Relay and Replay
- All supported clients and built-in Symdex
Firekeep Team · paid
The planned multi-person edition of the same Firekeep platform. Pricing, availability and the final onboarding experience will be announced before launch.
- Shared working knowledge across multiple people
- The same supported agents and self-hosted deployment model
- A clear paid boundary based on adding people
Frequently asked
Before you join the waitlist.
Is Firekeep for teams available today?
No. The multi-person edition is coming soon. Solo is available now for one person and contains the complete current capability set.
How will Teams differ from Solo?
Solo is for one natural person using any number of personal agents and devices. Teams is planned as the paid edition for multiple people sharing the same Firekeep knowledge and continuity platform. Final availability, pricing and onboarding details will be announced before Team launches.
What becomes shared knowledge?
Firekeep works with information that is deliberately recorded or ingested: Corpus sources, Cortex memories, reviewed Skills and explicit Bridge session state. Retrieval is relevance-based; Firekeep does not treat every raw agent conversation as durable organizational truth.
Will Teams require a hosted Firekeep cloud?
The planned Team edition keeps Firekeep’s self-hosted deployment model. Public downloads and update checks use the release channel, while optional model providers or integrations make external requests only when an operator configures them.
Which AI coding clients will work with Teams?
Teams is planned around the same Firekeep gateway and adapters used by Solo: Claude Code, Codex, Kiro and OpenCode. Other MCP-capable clients can be configured manually, though lifecycle automation varies by client.
Help shape Firekeep for teams
Tell us where your team loses context.
Share your team size, the coding agents you use and the handoffs or knowledge gaps you want Firekeep to solve. We will contact you about Team availability.
Or email sales@firekeep.ai. No account or payment is required to join.