Everscribe is live. It is the easiest way to add an audit trail to your app.
Why not build it yourself?
Rolling your own audit logging is not one project. It's six:
- Instrumentation that keeps up as your team ships new endpoints every week.
- Retention that satisfies compliance, which wants years, and privacy law, which wants deletion on request.
- A view for your customers, with a UI and a permission model, the day one of them asks to see their own activity.
- Search that turns a stressful question into an answer fast.
- Storage for what quickly becomes your largest table, without it competing with your application traffic.
- Delivery into your customers' Splunk, Datadog, or Sentinel, with retries and proof nothing was lost.
Each one looks small on the day it lands. Together they are a year you meant to spend on your product. An audit log is not just a feature. It is evidence. When an auditor asks about last March, whatever you had built by then is the only answer you get.
With Everscribe, retention is a policy on your account, enforced on a schedule. Forwarding to your SIEM is a setting, not a sprint. The storage is ours to run.
Up and running in minutes
Here is everything it takes.
1. Create an account. Sign up with email or Google and verify your email.
2. Create a project. One project per app, per environment is the typical layout. E.g. acme-prod, acme-staging.
3. Create an API key. Open the project's API keys tab and create one. You see the secret once, so put it in your environment or secrets manager.
4. Wire up the SDK. Pick whichever path fits how you work.
Coding with Claude? Install our setup skill with the es CLI and run it in your repo locally via /everscribe-setup in Claude Code( you might have to restart claude for it to get picked up). It detects your HTTP handlers, proposes the audit events worth recording, and wires the SDK in for you. It asks before it commits anything, and it runs against your own Anthropic key, so your source code never leaves your machine. Full walkthrough: Claude setup skill.
Prefer to wire it yourself? Install the SDK for your stack. We ship SDKs for Go, Node, Python, and Rust.
Each SDK also ships HTTP middleware for the popular frameworks, so most handlers only have to name the event. Full walkthrough: Recording Events.
That's it. Open your project's Events page and your events are there, searchable and filterable. Ask a question in plain English and our AI turns it into a query for you.
Built for multi-tenant apps
If your customers have customers, Everscribe already speaks their language.
Tag any event with a TenantID for your end-customer's workspace and you can query, filter, and export per tenant. Single-tenant apps leave it blank and nothing changes.
Your customers can see their own trail too. Drop our embeddable <audit-trail> component into your app, mint a tenant-scoped token from your backend, and each customer sees only their own activity. Our server enforces that scope on every read. The component comes with the same search you get in the Everscribe dashboard, including plain-English questions, and every color and spacing value is a CSS variable you can match to your brand.
Open source, top to bottom
Everything you integrate with is open source.
- SDKs for Go, Node, Python, and Rust, with middleware for the major frameworks.
- The
esCLI to manage projects and API keys, and tail and inspect events from your terminal. - Web components for React, Svelte, and plain HTML, plus a core data layer if you want to build your own UI.
- The Claude setup skill, plain markdown you can read before you run it.
- Full-stack examples covering twelve frontend and backend combinations, each in single-tenant and multi-tenant variants.
What's next
We are just getting started. See what we are building next on our roadmap.