Atlas Q · 11/11 IPFS · Integrations & SDKs
How systems integrate with Atlas Q
Atlas Q is designed to sit beneath existing applications as a secure storage and integrity layer. The focus is on simple, composable integration points rather than a heavy, proprietary platform.
Integration patterns
- Gateway API: HTTP/JSON endpoints for encrypting objects, committing QHASH manifests, and retrieving data.
- Direct SDK usage: Client libraries handle encryption, key wrapping, and manifest creation before calling the gateway.
- Batch / archival: Existing systems export data sets that are ingested into 11/11 IPFS as immutable archives with residency and audit guarantees.
In all cases, Atlas Q is responsible for encryption and integrity logic; applications retain control of their own business workflows and user experiences.