We Just Shipped TamperTrail v1.0.0 — Here's the Whole Story

If you're reading this, thanks for stopping by.

Whether you found this through a random search, someone shared it, or you stumbled in from somewhere — I appreciate it. This is my first blog post for TamperTrail and I want to use it to explain what this project actually is, why I built it, and be completely upfront about where it stands today.

What problem was I actually trying to solve?

It started with a pretty basic question I couldn't stop thinking about:

If your audit logs live in PostgreSQL, and someone with database access deletes or modifies them — how would you know?

You wouldn't. That's the uncomfortable answer.

Standard logs, whether they sit in a database, an S3 bucket, or a cloud logging SaaS, can be modified or deleted by anyone with the right credentials. There's no mathematical proof that the log you're reading today hasn't been touched since it was first written.

This matters a lot for teams building towards SOC 2, HIPAA, or any compliance framework that requires tamper-evident audit trails. Auditors don't just want logs — they want evidence. Those are two very different things.

At the same time, sending all your audit data to a third-party cloud logging service meant your most sensitive operational data — who accessed what, when, from where — was sitting in someone else's infrastructure. For a lot of teams, that's a hard no.

So: self-hosted + cryptographically tamper-proof. That's the foundation TamperTrail is built on.

What is TamperTrail exactly?

TamperTrail is a self-hosted audit logging infrastructure. You deploy it on your own servers, inside your own environment. Your data never leaves. No third-party sees it. You own everything.

Every log entry gets SHA-256 hashed and chained to the previous one — like a blockchain, but without the nonsense. If anyone modifies or deletes a log entry, the chain breaks. It's instantly, mathematically detectable.

It also ships with:

Write-Ahead Log (WAL) — logs are crash-safe and your app never blocks waiting for the audit system. POST /v1/log responds in under 10ms.
AES-128-CBC encrypted metadata vault — sensitive fields are encrypted server-side before they touch the database. Never stored in plaintext.
Built-in dashboard — search, filter, verify integrity, export compliance reports.

You can go deep on the internals in the CTO Architecture Whitepaper if you want the full technical picture.

Who is this for?

Backend engineers, DevOps teams, and founders building products where compliance is part of the roadmap — fintech, healthtech, SaaS, or anything that handles sensitive user data. If you need to answer "show me every action this user took" or "prove this log wasn't modified", TamperTrail is built for exactly that. Self-hosted, tamper-evident, and free to start.

The thing I genuinely like about it: you get a fast, developer-friendly audit logger from day one. And when compliance requirements show up — SOC 2, HIPAA, whatever — your logs are already verifiable. No retrofitting. No scrambling. Just integrity built in from the start.

How do you get started?

Pretty straightforward. It's a Docker Compose stack — you clone it, set a few environment variables, and run it on your own infrastructure.

Head to the Installation guide — it walks you through every step
Then check the Integration Guide to add the Python SDK to your existing app
The API Reference covers the full POST /v1/log spec if you're integrating from another language

Self-hosting means you're in full control of where it runs, how it scales, and who has access to it. No vendor dependency, no data leaving your servers.

Pricing — what's free, what's not?

Right now, the core infrastructure is free. The full stack — ingestion, dashboard, SDK, encryption, hash chaining — all of it is included in the Developer tier at $0.

A Startup tier is in development for teams that need unlimited log retention, multi-project support, webhooks, and high-availability mode. Pricing isn't set yet — if you're interested, you can join the early access waitlist and you'll be the first to know.

Full breakdown on the Pricing page.

What's the current state honestly?

v1.0.0. It works, it's been tested, but it's early. I'm one person building this. I'll be straight with you:

Hash chain verification is solid
The WAL and encryption are production-grade
The dashboard is functional, not particularly polished yet
There's currently one native SDK (Python) with HTTP/curl docs for other languages — more SDKs are coming

If you run into something, there's a contact form on the pricing page or you can reach out directly. If you want to give general feedback, same place.

That's it for now

More posts coming. I plan to write about the cryptography implementation in detail, how the WAL works under the hood, and real integration patterns for different stacks.

If TamperTrail looks useful to you — start with the Installation guide and get it running. If you have questions or hit a wall anywhere, reach out through the contact form.

Thanks for reading. Talk soon.

— Shubham