▎ I'm building a tool that generates tamper-evident receipts for AI coding sessions. I just shipped the site, designed with backend and frontend with I would say good security for apis and those types of things.

AI writes half my code now, and when something goes wrong I have basically no record of what actually happened, what the agent did, in what order, what it touched. "The AI broke it" isn't something you can show anyone.

So I've been building Axyvera: a local-first evidence layer for AI-assisted development. It records sessions as hash-chained streams (each event sealed against the last, so edits are detectable), exports them as signed .axy evidence bundles, and there's a free verifier so anyone can check a bundle's integrity without a license — verification shouldn't be paywalled if the point is trust.

Everything is redacted before it's persisted. Raw prompts and credentials never touch disk. The evidence is about what happened, not what you typed.

Just shipped the website: https://axyvera.com

One design decision I'm weirdly proud of: since the whole product is basically "signed documents," I styled the site like security printing, engraved-plate dark green instead of the usual near-black, a Clarendon slab serif like you'd find on a banknote, verdicts that land as rubber stamps, real SHA-256 digests as section serial numbers, and a verified seal whose ring draws itself closed as the hero chain finishes verifying. I wanted it to feel like a notarized record, not another dark-mode SaaS template.

Stack: Next.js 16 + Tailwind on Vercel, Redis for the license store, Ed25519 for signing. License documents are returned exactly once at issuance and never stored server-side — the server keeps metadata only.

Would love feedback on both the concept (would you actually want receipts for your AI sessions?) and the site itself. I need like brutal honesty btw.