Atlas Q · 11/11 IPFS · Roadmap

A deliberate path from architecture to deployment

Atlas Q is being built for long-lived, high-value workloads. The roadmap is structured around real milestones: architecture, pilots with defined datasets, integration tooling, and eventual deployment as a shared storage layer for multiple institutions. Timing will adjust as pilots evolve, but the sequence and priorities are stable.

Current focus Next phase Future expansion

Phase 1

Architecture & public surface

Complete: 11/11 IPFS architecture, QHASH model, audit design.
Complete: Public overview site with whitepaper and architecture pages.
In progress: Refinement of demo flows and pilot-specific configurations.

Phase 2

Pilot environments

Current focus: Run pilots against synthetic or de-identified datasets.
Exercise residency pinsets (US / EU / APAC / private) under realistic policies.
Collect operational data for encryption, pinning, and audit throughput.

Phase 3

SDKs & integration tooling

Release lightweight Python and TypeScript SDKs for client-side encryption and QHASH handling.
Publish gateway API documentation and reference configurations.
Provide sample integrations for EMR, document vaults, and identity systems.

Phase 4

Enterprise rollout

Offer Atlas Q as a storage and integrity layer under formal agreements.
Support multi-tenant deployments with strict residency requirements.
Expand compliance mapping and support for audits and certifications.

The roadmap is intentionally conservative. Atlas Q aims to become infrastructure that remains relevant over decades, not a short-lived product cycle. Each phase is gated on real-world validation, not just code completeness.