Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prudra.dev/llms.txt

Use this file to discover all available pages before exploring further.

Storage overview

Prudra Storage gives each paid request its own isolated vault: a container for documents, files, and real-time events. Vaults are created automatically by vaultMiddleware when a payment is verified, and sealed by your handler when the work is done.

What storage provides

FeatureDescription
VaultsIsolated containers created per payment. Hold documents, files, and events. Auto-expire after TTL.
EventsReal-time SSE stream per vault. Emit progress events while work runs.
FilesBinary file storage via GCS. CDN-delivered at assets.prudra.dev.

Vault lifecycle

Every vault moves through a defined set of states:
created → active → sealed → persisted (optional)
                          ↘ expired (if not persisted)
  • Active: Your handler can write documents, files, and events
  • Sealed: Work complete. No further writes. Caller can still read.
  • Expired: TTL elapsed. Vault and all contents deleted.
  • Persisted: Manually extended — survives past its TTL.

Plan limits

LimitHobbyProEnterprise
Active vaults350Unlimited
Persisted vaults120Unlimited
Vault TTL24 hours7 daysUnlimited
Documents per vault50UnlimitedUnlimited
Files per vault5100Unlimited
Max file size10 MB100 MB1 GB
Total storage500 MB10 GBUnlimited

Sub-pages

Vaults

Create, seal, persist, query, and delete vaults.

Events

Real-time SSE event streams per vault for progress reporting.

Files

Upload, download, and delete binary files from vault storage.
  • Accept a payment — vaultMiddleware wires vault creation into your handler
  • Webhooksvault.sealed and vault.expiring events