Solo · complete product for one person

One person. Every connected agent. One memory.

Firekeep keeps your decisions, sessions, runbooks and proven fixes available across Claude Code, Codex, Kiro and OpenCode. Use as many personal agents, terminals and devices as you need, on infrastructure you control.

Install Solo free Explore the capabilities

Free for one person
No feature-reduced tier
Unlimited personal agent identities and devices

your continuity layer

Illustrative flow · useful context follows your workone self-hosted server

Adapters included

CLClaude Code CXCodex KIKiro OCOpenCode

Corpus knowledge base

Stop teaching every new agent the same things.

Put runbooks, architecture notes, API documentation and operating procedures into a searchable knowledge layer that every one of your connected agents can use.

Searchable immediately. Firekeep chunks and indexes ingested content for ordinary memory recall.
Useful beyond storage. When a generation model is configured, procedural material can become draft Skills for you to review.
One source of continuity. Corpus knowledge and lessons from your own sessions surface through the same retrieval path.

Your knowledge sources · illustrativesearchable

ADRArchitecture decisions18 indexed chunksready

OPSRelease runbook11 indexed chunksready

APIInternal API notes26 indexed chunksready

Relevant context returned

Before rotating the key, preserve the current credential ID and verify the protected health route—not only the public health check.

Everything in Solo

A full continuity stack, not a trial.

The commercial boundary is another person—not the tools that make Firekeep useful. Solo includes the complete current capability set.

Cortex + Skills01

Memory that compounds

Recall prior decisions, incidents and successful fixes. Author reusable playbooks, or review procedure drafts derived from your documents.

semantic + graph recall · confidence · lifecycle

Bridge02

Sessions that survive interruption

Preserve explicitly recorded plans, decisions, progress and file knowledge through context compression, restarts and recoverable crashes.

durable shadow · resume · completion distillation

Relay03

Your agents can coordinate

Assign tasks, leave bulletins and messages, and use expiring fenced leases when several of your agent identities work in parallel.

tasks · channels · DMs · best-effort presence

Symdex04

Focused local code context

Search symbols, callers and impact locally instead of loading an entire file when a known symbol is enough. In an audited 360-lookup benchmark, direct known-symbol retrieval used about 55% fewer estimated context tokens on average than sending the containing file.

Decisions + Replay05

Answers and traces you can inspect

Collect several choices in a local Decision Board, then inspect Firekeep-mediated session events and the exact or nearest saved context when work needs review.

human answers · recorded timeline · likely-contributor narrowing

Sentinel06

Configured environment signals

Watch selected repositories, files or containers and make relevant changes available to later agent work.

opt-in watchers · environment events

Vault + Policy07

Secrets stay out of memory

Keep credentials encrypted and separate from recall, with scoped retrieval and supported pre-action policy checks.

encrypted at rest · explicit retrieval

Dashboard08

One operational view

Inspect memories, sessions, knowledge sources, Skills, coordination, policy events and replay traces from one local web interface.

review · manage · troubleshoot

The Solo knowledge loop

Each tool picks up where the last one stopped.

Firekeep does not replace your coding agents. It gives them a durable place to put what should survive the conversation.

01 · ground

Add durable knowledge

Index runbooks, architecture notes and other context you should not have to paste repeatedly.

02 · work

Record what matters

Preserve explicit plans, decisions and non-obvious fixes as your sessions progress.

03 · return

Recall from any client

Start the next task in Claude Code, Codex, Kiro or OpenCode with relevant prior evidence available.

04 · refine

Review and reuse

Promote useful procedures into Skills and inspect the recorded trace when something needs explanation.

Self-hosted by design

Your working knowledge stays under your control.

Firekeep's server services, datastores and default inference path run on infrastructure you control. Optional external connectors or model providers are contacted only when you configure them.

One Linux Docker host

The server stack is designed for a single-host deployment; 16 GB RAM is recommended for the default local-inference configuration.

Your everyday machines

Use supported clients from Linux, macOS or Windows while Symdex stays local to the working tree it indexes.

Closed by default

Application services bind to loopback by default, with authenticated client connections when access is enabled.

Private-work cutoff

Personal mode makes Firekeep dormant for work you do not want recorded; it is separate from the Solo edition.

Solo is available

Install the complete one-person edition now.

Install the public Firekeep client, provision the self-hosted server with firekeep init, and attach additional workstations with single-use join codes. Downloads resolve through the checksum-verified public release channels.

Install Solo Client installation Free for one person. No account, payment or license document required.

Solo FAQ

One person does not mean one agent.

What does “free for one person” mean?

Solo permits production use by one natural person in one workspace and deployment. That person can use unlimited personal devices, terminals, agent identities and background workers.

Is Solo missing Team features?

No. Solo includes the complete current Firekeep capability set. Team uses the same product and adds additional people; Team onboarding and commercial availability are still being prepared.

Is Corpus useful for an individual?

Yes. Corpus gives all of your connected agents the same searchable runbooks, architecture notes and reference material. A generation model is needed only for optional procedure classification and draft-Skill creation—not ordinary search.

Does Firekeep capture every conversation automatically?

No. Firekeep preserves state and knowledge that its tools and supported lifecycle integrations explicitly record. Automation varies with the hooks each coding client exposes.

Can I install Solo today?

Yes. Install the client kit, run firekeep init on a Linux Docker host, then connect your workstation. The installation guide uses the live public client and server channels.