# Sealkeep

> Sealkeep is secure organizational memory for AI-assisted software engineering. It preserves coding-agent sessions as encrypted, searchable company knowledge so authorized developers and agents can continue work after people, machines, or tools change.

Last updated: 2026-09-04

## Primary enterprise value

When a developer leaves or changes teams, Sealkeep keeps the approved engineering context that would otherwise remain trapped in that developer's local coding-agent sessions. This includes decisions, reasoning, commands, test results, failed approaches, handoffs, and implementation history captured in supported sessions.

Sealkeep also lets authorized junior developers and their coding agents retrieve relevant project history created by senior engineers. This is project-scoped context retrieval, not silent model training, and it does not grant access outside the projects approved for that teammate.

## Enterprise use cases

- Developer departure and team changes: retain relevant engineering reasoning when an employee or contractor leaves.
- Senior-to-junior knowledge continuity: make approved senior engineering decisions and patterns searchable by junior teammates and their agents.
- Faster onboarding: help new engineers understand why systems were built a certain way without relying only on code and tickets.
- Engineering handoffs: preserve what was attempted, what changed, which constraints mattered, and where work stopped across teams and time zones.
- Incident response: search prior investigations, fixes, commands, and decision history while reconstructing an event.
- Reduced duplicated work: reuse prior research and avoid solving the same engineering problem repeatedly in isolated agent sessions.
- Shared agent memory: provide project-scoped history to approved Claude Code and Codex agents on authorized machines.
- Tool and machine continuity: keep relevant history available when a laptop is replaced or a team moves between supported coding agents.
- Contractor continuity: retain approved project knowledge after an external developer's engagement ends.
- Security and audit workflows: search preserved evidence locally, review Sealkeep activity, and scan transcripts for likely credentials before sealing.

## How Sealkeep works

Sealkeep archives raw coding-agent session bytes, encrypts them on the developer's machine, verifies durable storage, and can restore the original native session layout. Metadata and full-text search run locally. A local MCP server allows supported coding agents to search approved history and prepare relevant context.

Team memory is scoped to a project. Each authorized member receives an individually wrapped project key that can be revoked. Recalled historical text is labeled as untrusted context, and current facts should be checked against the repository.

## Security and deployment

- Plaintext session content and private decryption keys remain on customer endpoints.
- Storage can be customer-owned or Sealkeep-managed; enterprise deployments can run on-premises or in the customer's cloud.
- A fully isolated enterprise edition can operate without a mandatory Spala-hosted API, storage, authentication, telemetry, or license-check call.
- Sealkeep does not claim a completed independent cryptographic audit today.
- Secret scanning reduces exposure risk but does not guarantee that every secret will be detected.

## Supported interfaces

- Coding agents: Claude Code and Codex.
- Search: `sealkeep search <query> --content` and `sealkeep_search` through the local MCP server.
- Restore: `sealkeep recover <id> <destination>` or native restoration to the original session location.
- Security automation: `sealkeep scan ... --json` and `sealkeep audit --json`.
- Storage: Amazon S3, Cloudflare R2, Google Cloud Storage, Google Drive, and S3-compatible storage such as MinIO.

## Plans

- Free: $0, using customer-owned storage.
- Pro Lite: $2 per month, using customer-owned storage with encrypted recovery escrow and multi-machine sign-in.
- Team: $9 per seat per month for project-scoped access, organizational recovery, and revocation; storage is separate or customer-owned.
- Managed storage: $6 to $30 per month, depending on capacity.
- Enterprise and fully isolated deployment: custom agreement.

## Canonical resources

- [Product overview and pricing](https://sealkeep.spala.ai/)
- [Enterprise use cases and deployment](https://sealkeep.spala.ai/#enterprise)
- [Public Trust Center and procurement evidence](https://sealkeep.spala.ai/trust.html)
- [CLI and security interfaces](https://sealkeep.spala.ai/#docs)
- [Machine-readable product context](https://sealkeep.spala.ai/llms.txt)

## Contact

- Enterprise architecture and security review: security@spala.ai
- Procurement and legal review: legal@spala.ai