Archibal. Every AI generation, remembered.
Connect Claude, ComfyUI, or your generation tools once. From then on, every render is saved with its prompt, model, seed, and workflow - the moment you generate. Your work becomes a searchable library, and every delivery ships with proof of how it was made.
- Free - no card required
- Renders captured automatically
- Prompts & workflows saved
- Searchable production library
- Deliver with verification
How it works
From generation to delivery, nothing gets lost.
Your best work should not disappear into a downloads folder with no prompt, no settings, and no way to reproduce it. Archibal keeps the record for you.
Connect
Claude, ComfyUI, fal, ElevenLabs, Runway, Higgsfield - or a plain webhook. One-time setup; no change to how you work.
02Capture
Every generation lands automatically with its prompt, model, seed, and workflow - into a searchable library where each file keeps its recipe.
03Deliver
Ship the final with a signed provenance certificate. The record freezes at delivery - later edits create new deliveries, never rewrite old ones.
04Verify
Anyone with the link can check the record - what was made, with which models, and how each claim was evidenced.
One platform, two sides
Whether you make AI content or receive it.
Every delivery connects a creator workspace to a client workspace - the provenance travels with the work.
For creators & agencies
Produce AI work with proof
Upload work - or push it straight from ComfyUI - and Archibal records the models, prompts, and references behind it. Deliver with a signed C2PA manifest and a public provenance record your client can verify - and their procurement team can file.
- - Multi-layer AI detection on every upload
- - Clearance checks for protected characters, brands, and logos
- - Signed provenance records with public verification pages
For brands & clients
Receive AI content with proof
Receive certified deliverables into your own inbox and verify any file's content credentials before it goes live. Track the audience-facing disclosures you must add as the deployer, and keep a durable provenance archive across every agency.
- - Inbox of verified deliveries from every agency
- - Disclosure tracker for the channels you publish on
- - Independent file verification, even after metadata stripping
New here? Read the documentation or try the risk preview - no account needed.
The trust layer
How we know what we know.
Every claim in an Archibal record carries its evidence grade - how the information reached us, stated plainly. A record never pretends to more certainty than its capture channel earned.
The file arrived with verifiable capture evidence - an embedded workflow graph or a signed manifest.
A generation tool reported the details itself, over a trusted automatic channel.
An orchestration log from your studio pipeline recorded the job.
A person stated how the file was made. Recorded as a declaration - never upgraded to more.
Deliveries also carry signed C2PA Content Credentials, so the provenance survives inside the file itself - and anyone can check the record on its public verification page.
Honesty policy
What Archibal does not claim.
- 01
We are not a lawyer, and our checks are advisory. Governance findings inform your decision - they never gate your delivery. Whether an asset is cleared for a given use is a call for you and your legal counsel.
- 02
We show what we know and how we know it - never manufactured certainty. An unknown stays labeled unknown. A declaration stays a declaration. Usage terms we have sourced but not reviewed say exactly that, on the record.
- 03
A record is evidence, not a compliance certificate. AI-labeling laws mostly bind model providers and the organizations that publish content. An Archibal record is the provenance evidence those duties increasingly ask for - it does not discharge them by itself.
Why Archibal.?
AI production moves fast and leaves nothing behind: prompts vanish into chat histories, workflows live on one machine, and when a client asks how something was made, there is no good answer.
Archibal keeps the record at the source - every generation captured with its recipe, every file traceable through the stages that made it, every delivery backed by a provenance record you can stand behind.
Latest Intelligence
Analysis on AI production, provenance, and the rules arriving around them - how creators work, what the record proves, and what changes next.
- 1 Does the EU AI Act apply to agencies outside the EU?
- 2 How to label AI-generated content for the EU AI Act
- 3 How to verify AI-generated content you receive from an agency
Questions, answered
What does Archibal actually capture?
Every generation that flows through a connected tool: the file itself plus its prompt, model, seed, settings, and - where the tool provides one - the full workflow graph. Uploads are scanned for embedded recipes and Content Credentials too, so even work made elsewhere keeps its story.
Do I have to change how I work?
No. You connect a tool once - Claude, ComfyUI, fal, ElevenLabs, Runway, Higgsfield, or a plain webhook - and capture happens as a side effect of generating. There is no manual logging, no forms, no extra step in your creative loop.
What do my clients see when I deliver?
A delivery certificate, signed C2PA Content Credentials on the file, and a public verification page showing what was made and with which models. You choose the disclosure level: clients see business context and models, never your prompts or workflow - those stay yours.
What does Archibal actually produce?
A signed C2PA manifest, a perceptual fingerprint, and a frozen, verifiable provenance record on every delivery. The record is created automatically from what was captured - and it never changes after delivery; corrections create new deliveries.
What about AI disclosure laws?
AI-labeling rules mostly bind model providers and the organizations that publish content - and they push everyone in between to demand provenance. An Archibal record is that provenance, ready when someone asks. The specifics live at our compliance hub.
Regulation-specific questions live at the compliance hub.
And when regulation asks
The record already exists.
AI-content disclosure rules are landing across the EU and the US. They bind the model providers and platforms - and push everyone downstream to demand provenance. If your work is captured in Archibal, you are not scrambling for paperwork when they do.
EU AI Act · Article 50
AI media reaching EU audiences has to carry machine-readable disclosure.
Synthetic image, audio, video, and text needs an embedded, verifiable marking that a platform or regulator can check.
All EU-facing agencies, brands, and platforms
Your library, working for you
Search everything you have ever generated by prompt, model, or project. Re-run any step from its saved workflow. Trace any final back through every stage - and every take - that made it.
Create a free account