The Cloud evidence surface is in development
This surface is wired behind FILEONCHAIN_CLOUD_EVIDENCE_ENABLED. The backend, schema, and pages ship in this build; the route and UI are not reachable for users until the flag is flipped on.
Cloud
FileOnChain Cloud — the convenient way to run it
Managed anchoring, dashboard, and billing for teams that want evidence without operating wallets, RPC endpoints, and signers themselves. The hosted product removes the operational work — honestly labeled by what's live today.
Available today
What you can use right now without any feature flag.
Hosted anchoring with credits
AvailablePOST an artifact hash to the hosted API with a fok_ key; a funded worker settles it on the network you chose and returns the receipts.
MCP server for AI agents
Availablestdio Model Context Protocol server: read-only network-registry tools plus API-backed anchoring tools, so agents produce evidence without holding private keys.
Dashboard, API keys & activity history
AvailableScoped API keys, job polling for anchor requests, activity logs, and a dashboard of everything your keys have sealed.
Credit billing in USD/USDC
AvailableCredit ledger denominated in micro-USDC; deposits in USDC, hosted anchoring debits credits per job (refunded on send failure).
Wired behind FILEONCHAIN_CLOUD_EVIDENCE_ENABLED
The backend, schema, and pages ship in this build. The routes and UI are not reachable for users until the flag is flipped on. Listed here so they are not mistaken for current ones.
Evidence ingestion
PlannedPOST a sealed envelope to /api/v1/evidence; Cloud stores it under your org, recomputes the envelope digest, and stamps the retention policy.
Agent-run sealing
PlannedPOST an Agent Evidence Profile envelope to /api/v1/agent-runs; Cloud records runId + agentId for run-centric reads via /api/v1/agent-runs/:runId.
Server-side signer (server_sign)
PlannedGenerate a per-org ed25519 key and pass ?server_sign=1; Cloud adds an envelope signature — a service identity attesting it assembled the envelope. Never an artifact signature, so it makes no claim about who authored the subject. Verifiers resolve the public key status URL independently.
Retention & search
PlannedPer-org retention window editor; new envelopes are stamped with an expiry and a daily Vercel Cron sweep deletes expired rows. Full-text + claim-level search across the org's envelopes, indexed by a Postgres tsvector, with a multi-org scope picker.
Hosted verification pages
PlannedShareable per-envelope verification pages for counterparties who won't run a CLI. The local verifier remains the ground truth — hosted pages are a convenience, never a requirement.
Server-side verify
PlannedPOST an envelopeId or envelope to /api/v1/verify; Cloud runs the open verifier and returns the same VerificationReport shape as @fileonchain/verify.
Projects, quotas, per-project signers
PlannedSub-org tenancy with monthly caps on envelopes + anchors + bytes anchored, and an optional per-project service signer for project-attributed envelope sealing.
Webhooks
PlannedSubscribe URLs to envelope and anchor events. HMAC-SHA-256 signed delivery with exponential backoff and a per-minute drain so retries happen within minutes, not hours.
Bulk `.evidence.json` exports
PlannedStream every envelope (or a filtered subset) into a TAR archive of canonical `.evidence.json` files. Token-bound download links expire 24 hours after the build.
Compliance reports & SLAs
PlannedMonthly signed summaries plus tier-based uptime and settlement-latency promises, ready to share with auditors or partners.
Portable export, independent verification
Every Cloud-produced envelope is a standard protocol document; the reference verifier (fileonchain verify) checks it deterministically and locally with no FileOnChain service in the loop. The hosted pages run the same code — paste one into the in-browser verifier and the report matches. If FileOnChain disappeared tomorrow, existing envelopes and their receipts would lose nothing.