Persistent identifiers
Every registered file has a unique fabric URI. Renaming folders or changing application views does not change that identity.
CrownThrive / Your fabric
PENTAFABRIC WORKSPACE
Your work. Your fabric.
Organize, connect and carry your work across the ecosystem.
Connecting to your fabric…
BUILT AROUND YOUR WORK
One workspace.
Not another silo.
Keep persistent file identities, organize your work, export your metadata, and decide which people and apps can see it.
Opening a workspace does not start a subscription. Storage, file delivery and external processing are separately qualified.
| File | Size | Status | Folder / tags | Actions |
|---|
A home for what comes next.
No files match this view. Create folders now; uploads require a verified storage allocation.
File identities and checksums are independent of folder names. Organizing a file never deletes or rewrites its original bytes.
Choose how your fabric should work.
Save a cloud, decentralized or hybrid preference. A preference is not a migration or a promise that an unqualified backend is active.
Provider mesh
| Provider | Role | Qualification | Resale eligible |
|---|
Available storage is not automatically sellable storage. Provider contracts, verified budgets, retained bytes, existing reservations and recovery headroom govern allocation.
Links that respect permission.
Give a verified recipient an expiring metadata link and QR code. A link does not make a bucket public. Revocation takes effect at the next access check.
Current service details
This release supports authenticated file identity and metadata sharing. Shared binary downloads are not enabled; delivery acceptance is still outstanding.
Your recipient links
Open a shared link
YOUR DATA PASSPORT
Your identity stays.
Your work can move.
Stable workspace and file identifiers let authorized tools refer to the same work without depending on a particular folder or storage vendor.
Exports contain metadata and your declarations, not file bytes or automatic rights clearance.
Verifiable metadata
The manifest carries file names, sizes, SHA-256 fingerprints, folder assignments and tags.
Controlled portability
Export metadata without provider credentials. Binary exports, automatic migration, and universal cross-brand single sign-on are not included in this release.
Use it across CrownThrive
Connect your own authorized application through the scoped API or MCP bridge. Virality Music, Melanated Vault/Stock, Go Flipbooks, Locticians and CrownThrive IO can adopt the same file identities; each application still needs its own tested adapter and user permission.
Your apps. Your permission.
Review native service bindings and record or revoke consent. Consent alone never triggers a file transfer, image optimization or charge.
Current service details
ThriveTools OPT and SEO are registered services. Per-customer transfer and transformation adapters remain acceptance-gated. Provider account secrets stay server-side.
Put your fabric in your workflow.
Create a scoped, expiring read-only key for your own app or agent. Keys cannot upload, purchase capacity, create public shares, or delete data.
Keys and access
REST API
GET /api/fabric?resource=files
Authorization: Bearer <your scoped key>Resources: files, passport, integrations. Cursor pagination and filename search are supported.
OpenAPI specification ↗Model Context Protocol
https://crownthrive-storage-fabric.vercel.app/api/mcpRead-only tools for files, manifests and integration states. Manual Bearer-key clients or the bundled stdio bridge are supported. OAuth discovery is not implemented.
Download stdio bridge ↓Capacity you can account for.
Allocation is reserved before checkout. Existing storage, replica obligations and hosting restrictions are not sold twice.
Subscription
No automatic provider upgrades, no silent overages and no subscription from merely creating a workspace.
Service limits
Current upload ceiling: 512 MiB per file. Hot/warm/cold remain logical policies on online Wasabi storage. Storj has a verified canary, not general production replication. No physical local storage node has been attested.
Your workspace activity.
Recent folder, preference, sharing, integration-consent and API-key actions. This view is not a claim of complete access-log or regulatory certification.
Useful tools. Right where you work.
Process a copy on this device. Source files are never overwritten. Nothing is sent to another service.
Text, JSON & CSV
Image resize & compression
JPEG, PNG or WebP · up to 20 MiB and 40 megapixels. A new image is created without copying source metadata.
File integrity
Calculate a local SHA-256 checksum and compare it with an expected value. Up to 512 MiB; this does not upload the file.
Keep a processing record
Save the source/output checksums, operation and file sizes to your workspace after processing. The output stays on your device until you choose to upload it.
What a record proves
This is a client-reported processing receipt, not a provider-verified upload or a rights approval. Linking to a stored file requires its source checksum to match.
Recent processing records
Context stays attached to the work.
Record the source, rights basis, intended use, credit and permissions. Keep an auditable revision history without changing the file.
Rights & cultural context
File details also provide direct access to this record. Your declaration is evidence supplied by you, not an automatic legal or cultural clearance.
CHLOM + Cultural Imprint Engine
1
Record context
Rights basis, audience, credit and permission choices.
2
Submit a review request
An exact revision and digest enter the existing governed review route.
3
Keep the decision separate
Only an authorized review can establish clearance. Submitting a request does not authorize publication or licensing.
Review and integration status
Checking the current review contract…