ArchiveClarity for EnterprisePlannedDesign partners now
When people leave, their AI history shouldn't.
See what AI tools store on every machine in your fleet. Archive sessions under encryption keys your organization holds. Free disk space without breaking anyone's tools — and keep the reasoning behind your code when the laptop is reimaged.
- Per device
- $6/ monthBilled annually
- Storage
- $0.15/ GB-monthOr your own bucket
AI storage across the fleet
| Device · last archive | AI storage | Status |
|---|---|---|
| mbp-anaAna Ruiz · 2 h ago | Protected | |
| mbp-dev-14Dev Patel · 1 d ago | 6% disk free | |
| win-kofiKofi Mensah · 3 h ago | Protected | |
| mbp-leeSam Lee · 9 d ago | Sweep in 2 d | |
| ubu-ml-02Priya Nair · 5 h ago | Move models | |
| mbp-jtJ. Tanaka — left Sep 2026 · Final | Held 7 yrs |
- VS Code Copilot
- Gemini / Antigravity
- Agent browsers & npx
- Codex
- Claude Desktop
- Claude Code
- Cursor
- Model weights
IllustrationPlanned admin consoleNot customer data
01
AI history is a business record now
It holds why the code is the way it is — and today it lives in plaintext folders on each laptop, on each tool's schedule.
- Claude Code keeps transcripts unencrypted on disk — including anything a tool read, like .env files.
- Plaintext
Claude Code keeps transcripts unencrypted on disk — including anything a tool read, like .env files.
Source: Claude Code docs ↗
- Default before Claude Code and Gemini CLI delete history. Other tools keep everything until someone cleans up — every machine differs.
- 30 days
Default before Claude Code and Gemini CLI delete history. Other tools keep everything until someone cleans up — every machine differs.
Source: Claude Code docs ↗, Gemini CLI docs ↗
- When someone leaves and their laptop is reimaged, the reasoning behind their code leaves with it.
- Offboarding
When someone leaves and their laptop is reimaged, the reasoning behind their code leaves with it.
02
Your company holds the keys. We never do.
Same encryption as the personal app — the difference is who holds the recovery key. For a team, that's the organization.
01 · Device
Encrypted where it's created
Each device compresses, deduplicates and encrypts its archive with its own key before anything leaves the machine.
02 · Organization
Your org key wraps every device key
Device keys are wrapped to a key your organization holds — so archives stay recoverable when a laptop is lost or someone leaves.
03 · Storage
Ciphertext only, wherever it lands
Archives go to your own bucket or ArchiveClarity Cloud. Either way we store ciphertext and never hold a key that can open it.
Only people you give the recovery role can open an archive, and every restore is written to your audit log. Bring-your-own KMS is planned for teams that keep keys in AWS, Google Cloud or Azure.
03
One view of every machine
The same scanner as the desktop app, reporting up to a console your IT team owns.
- Fleet
Every device, every tool
What each machine stores per AI tool — sessions, caches, databases, model weights — with growth over time.
- Status
Last archive and policy health
Which devices are protected, which are behind, and which are about to lose history to a vendor's auto-delete.
- Alerts
Before disks fill up
Get told when a device drops below its free-space floor, before a developer's day stops.
- Offboard
Keep history when people leave
Archives stay with the company. Restore a departed engineer's sessions to whoever inherits the work.
- Audit
Every action on the record
Archives, restores, deletions and key use land in an exportable audit log.
04
Policies, not tickets
Set it once in the console; every device follows. Employees see company rules as managed settings.
Example policies
- Archive AI sessions older than 14 days
- Rescue history before Claude Code's and Gemini's 30-day sweeps
- Never archive auth files, API keys or .env contents
- Keep archives for 7 years; hold specific users indefinitely
- Write archives only to the company bucket in your chosen region
Fits the tools you already run
| Area | Planned support |
|---|---|
| Deployment | Jamf, Kandji, Microsoft Intune, Mosyle, Workspace ONE — silent install and managed config |
| Sign-in | SAML and OIDC single sign-on (Okta, Microsoft Entra ID, Google Workspace) |
| Provisioning | SCIM user and group sync |
| Storage | Your S3-compatible bucket (AWS S3, Cloudflare R2, Backblaze B2, MinIO) or ArchiveClarity Cloud |
| Keys | Organization recovery key; bring-your-own KMS (AWS KMS, Google Cloud KMS, Azure Key Vault) |
| Residency | Choose the region archives are stored in, including EU-only storage |
05
Per device, plus what you store
$6 per device per month billed annually, or $8 month-to-month. Storage on ArchiveClarity Cloud is $0.15 per GB-month; in your own bucket it's free.
Measured after compression and deduplication — text-heavy session history shrinks a lot.
- 50 devices × $6
- $300
- 600 GB × $0.15
- $90
Planned pricing, before tax. Over 500 devices, talk to us about volume pricing.
06
What security teams ask first
Can ArchiveClarity read our employees' conversations?
No. Archives are encrypted on each device and the keys that open them belong to your organization. We store and move ciphertext only.
Who in our company can open an archive?
Only people you grant the recovery role, and every restore is written to the audit log. Policies decide whose archives can be recovered and when — for example, only after offboarding.
Do we have to use your cloud?
No. Point the fleet at your own S3-compatible bucket and you pay only the per-device price. ArchiveClarity Cloud is there if you'd rather not run storage.
What do employees see?
The same ArchiveClarity app, with company policies shown as managed settings. They can still browse and search their own history.
Is it available today?
Not yet. Enterprise is planned after the macOS app, and we're starting with a small group of design partners. Tell us about your fleet below.
07
Become a design partner
Tell us about your fleet. We're working with a small group of teams first, and a person reads every request.