Documentation Index
Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
Use this file to discover all available pages before exploring further.
Customer-Owned Data
Agentic Content Infrastructure (ACI) puts your content in infrastructure you own. Your content lives in your cloud storage bucket, in your own account. Gradial operates on your data but never owns it.How It Works
ACI stores three types of objects in your storage bucket:| Object | What It Contains | Format |
|---|---|---|
| Blobs | Content documents (pages, fragments, config) | JSON, deduplicated by content via SHA-256 |
| Trees | Directory structures mapping paths to blob hashes | JSON |
| Versions | Snapshots linking a tree, parent version, author, and timestamp | JSON |
main) that track the latest version.
Every object in your bucket is standard JSON. You can inspect it with standard cloud storage tools, query it directly, or process it with any tool that reads your storage provider. There is no proprietary binary format.
What This Means for You
Data residency and compliance
Data residency and compliance
Your storage bucket is in the cloud region you choose. Content never leaves that region unless you configure cross-region replication. This makes it straightforward to meet data residency requirements (GDPR, SOC 2, industry-specific regulations) because your data stays in infrastructure you control.
Backup and disaster recovery
Backup and disaster recovery
Your backup strategy is your cloud provider’s backup strategy. Enable versioning, configure lifecycle policies, set up cross-region replication, all with standard cloud tools. ACI’s immutable object model means even accidental deletion of a ref can be recovered by pointing it back to the correct version hash.
No vendor lock-in
No vendor lock-in
If you stop using ACI, your content stays in your bucket in a readable format: JSON blobs, JSON trees, JSON version records, all interpretable without ACI’s software. The version history gives you a full audit trail independent of any vendor.
Inspectability
Inspectability
You can audit exactly what ACI stores and when. Every object has a creation timestamp. Every version records the author. There are no opaque data transformations happening in a vendor’s infrastructure that you can’t see.
Projections and Caches
ACI’s deployed server maintains internal caches, indexes, and projections for performance: fast content lookups, workspace listing, reference resolution, dependency graph queries, and saving expensive recomputation. These are all derived from the blob storage. They are not the source of truth. Anything the server stores could also be computed from a full scan of your bucket; the indexes just make it fast. If any index or projection is lost or corrupted, ACI rebuilds it by replaying the version history from your storage bucket. No content is lost. No history is lost. Recovery is predictable and repeatable.Security Model
ACI accesses your storage bucket through a role that you configure. You control the permissions. You can restrict ACI to specific prefixes, require encryption, or add audit logging for complete access transparency. Gradial’s infrastructure never stores a copy of your content. Rendered pages pass through ACI’s build pipeline and are deployed to your CDN, but the canonical data always lives in your bucket.Next: Personalization →