Portable AI sessions, governed for enterprise.

SessionFS captures AI coding work across tools, turns it into portable sessions, and lets teams resume, hand off, audit, and coordinate that work. Personas, tickets, and AgentRuns reduce custom orchestration while the knowledge base grows from every captured session.

Easy handoffs from humans to agents. Same sessions, same tickets, same knowledge, same system.

The shadow AI problem

AI coding agents are already on your network. The question is whether you can see what they do.

80.9%

of engineering teams run AI agents without full security approval

24.4%

have visibility into AI agent communications

$670K

more per incident when shadow AI is involved

Sources: Gravitee 2026, Microsoft Data Security Index 2026

Session Portability + Agent Coordination

Every agent run starts as a captured, portable session your team can inspect, resume, or hand off. Personas claim tickets. AgentRuns enforce CI policy. The orchestration layer your team would otherwise build in-house — portable across 9 local tools and cloud-agent-ready for AWS Bedrock, Google Vertex, and custom API clients via integration docs.

Claude Code Codex Gemini Copilot Cursor Amp Cline Roo Code Kilo Code
session list
$ sfs list --today
Sessions (12)
ID Tool Msgs
ses_a1b2claude-code47
ses_c3d4codex31
ses_e5f6gemini23
ses_g7h8cursor52
ses_i9j0amp18

Organizational Memory

Memory is not a loose summary. It is derived from captured sessions with transcripts, file changes, commands, git state, and provenance. Every session distils into knowledge claims your agents read — and write back to. Architecture decisions, debugging patterns, API contracts, environment quirks. Your codebase documents itself.

LLM Judge cross-references every AI claim against actual tool output and feeds verified findings into the same knowledge base. Trust scores surface in GitHub PR and GitLab MR threads.

audit report
$ sfs audit ses_a1b2
Trust Score: 87%  |  Claims: 23  |  Verified: 18  |  Contradictions: 2
CRITICAL [CWE-393] Confidence: 94%
Claim: "All tests pass with exit code 0"
Evidence: exit code 1, 3 tests failed
HIGH [CWE-552] Confidence: 78%
Claim: "Created config.yaml with database settings"
Evidence: File not found in workspace

Compliance Built In

DLP scans every session archive server-side — 14 PHI patterns + 19 secret patterns, with BLOCK / REDACT / WARN modes set per organisation. Every captured manifest carries instruction provenance, persona, ticket, and the AgentRun that signed off. Audit-ready by construction.

HIPAA-ready managed or self-hosted deployment. Helm chart hardened with non-root UID 10001, read-only rootfs, RuntimeDefault seccomp. Deployed at a major healthcare system on AWS EKS.

dlp scan
$ sfs push ses_abc
DLP scan...
AWS_ACCESS_KEY detected in message 23
CONNECTION_STRING detected in message 41
Policy: REDACT
2 secrets redacted. Session pushed.

Easy handoffs from humans to agents.

Same tickets, same knowledge, same system — whether the operator is an engineer or an AI agent. The transition happens one persona at a time.

1

Engineers load personas

Every engineer assumes a persona (atlas, sentinel, scribe…) on their tickets. Sessions inherit the persona's rules, context, and identity. Captured work flows back into the knowledge base.

Where most teams start. No AI autonomy yet — just consistent rules and a growing audit trail.

2

Routine personas operate

Trusted personas run autonomously on routine tickets — security review, dependency bumps, doc sync — under human supervision. AgentRuns enforce CI policy; LLM Judge flags contradictions before they merge.

Hybrid operation. The persona does the work; the engineer reviews the AgentRun like a pull request.

3

Autonomous on routine; humans on exceptions

Whole categories of routine work move to autonomous personas. Humans handle exceptions, novel problems, and the work that requires judgement. The audit trail is the same regardless of which side of the line did the work.

The endgame. Custom orchestration was never built — the same tickets and knowledge base carry the workload through every phase.

Your data. Your boundary.

Session data never touches shared infrastructure. Choose how you deploy — we isolate the data either way.

MOST POPULAR

Managed · Single-Tenant

We operate it. Your data stays yours.

Dedicated database and storage bucket — no shared infra. We handle updates, monitoring, scaling, and support. Zero DevOps on your side.

  • Dedicated PostgreSQL
  • Dedicated storage bucket
  • Managed updates & patches
  • 99.9% uptime SLA
  • Zero Kubernetes required
Contact Sales

Self-Hosted · Your Cloud

You operate it. We support it.

Helm chart deploys to AWS EKS, GCP GKE, Azure AKS, or on-prem. Full network isolation. Bring your own PostgreSQL and object store.

  • Full network isolation
  • Air-gapped option
  • Your RDS / Cloud SQL
  • Your S3 / GCS bucket
  • HIPAA BAA available
helm deploy
$ helm install sessionfs ./charts/sessionfs \
--set license.key="sfs_helm_xxx" \
--set license.mode="local" \
--values values.prod.yaml
API ready
Dashboard ready
Migrations applied
View Helm docs

Both options include dedicated support, custom SLA, and 14-day trial license.

Security & compliance

Designed for regulated industries and security-conscious teams. SessionFS self-hosted gives you complete control over access, storage, and audit trails.

Ask about compliance requirements →
HIPAA-ready deployment
Air-gapped install with no external network calls. All session data stays within your VPC.
SAML SSO
Integrate with Okta, Azure AD, or any SAML 2.0 identity provider for centralized access control.
Full audit log
Every session write, push, handoff, and audit is logged with user, timestamp, and IP. Exportable for SIEM.
Organizations + RBAC
Admin and member roles with organization management. Team-scoped session visibility with per-repo isolation and tier-based feature gating.
DLP / Secret scanning
18 PHI identifiers, BLOCK/REDACT/WARN policies per organization. Detects API keys, connection strings, and tokens before sync. (Coming v1.0)
License management
Trial keys, paid licenses, cloud or local validation. Self-hosted license server for air-gapped environments.
SLA & dedicated support
Guaranteed uptime SLA, named support contact, and direct Slack channel for enterprise accounts.
"A major healthcare organization deploys SessionFS on AWS EKS with full network isolation for HIPAA compliance."

— Enterprise deployed, HIPAA environment

Talk to the team

Self-hosted deployment, compliance requirements, custom SLA, and pricing for large teams.

14-day trial license available for self-hosted evaluation.

We typically respond within one business day.

Contact Enterprise Sales