Build this with alleex
Ship a B2B SaaS where every action is auditable and explainable
Enterprise buyers demand audit trails. alleex composes a hash-chained, exportable audit log into your SaaS from day one — so compliance is a feature, not a backlog item.
Link
Hash-chained from day one
Every state-changing action writes an append-only row whose hash chains to the previous row via a server-side Postgres trigger. Retroactive alteration is detectable without access to your database.
Download
Exportable for enterprise buyers
Audit log is exportable as CSV or JSON from the control panel — no engineering ticket required. Sigstore Rekor chain heads are included so your enterprise buyer's auditor can verify independently.
Users
Multi-tenant, role-isolated
Each tenant sees only their own audit events. Role-based access control determines who can view, export, or redact audit records within a tenant workspace.
How it works
Compose these modules
Tenant audit log
Every action within a tenant workspace is recorded: who did what, when, from which IP, with before/after state for data changes. Exportable on demand by the tenant admin.
audit-log module
Multi-tenant isolation
Each customer tenant has a isolated data partition with row-level security applied by default. Tenant A cannot read Tenant B's data — enforced at the database level, not just the application layer.
multi-tenancy scaffold + Better Auth with RBAC
Role-based access control
Define roles (admin, member, viewer, auditor), assign least-privilege, and every permission change is itself audit-logged. Enterprise procurement teams check for this before signing.
Better Auth with RBAC
Signed deploys and SBOM
Every build produces a Software Bill of Materials (SBOM) signed with Cosign. Enterprise security teams can verify what went into the binary — a growing requirement in regulated procurement.
Syft + Cosign (built into the alleex build pipeline)
Customer stories
Real customer stories — none yet.
We are in private beta. The first case studies will feature named customers who share real results. We do not publish testimonials we have not earned.
Become a design partner →FAQ
Common questions
Is the audit log tamper-proof?
The hash-chain makes retroactive alteration detectable — each row's hash includes the previous row's hash. Chain heads are periodically submitted to Sigstore Rekor, a public transparency log. A third party can verify chain integrity without access to your database. We say 'tamper-evident,' not 'tamper-proof' — honest about what the architecture provides.
Can enterprise buyers access the audit log directly?
Yes. Tenant admins and users with the 'auditor' role can export the audit log from the control panel. You can also expose a read-only audit endpoint via the generated MCP server — DPoP-bound, RFC 9449.
Does the audit log survive database migrations?
Yes. The audit log is an append-only table with a server-side trigger — it does not depend on the application layer. Drizzle migrations preserve the table and trigger. Hash chains are not broken by schema changes to other tables.
What events are logged by default?
All INSERT, UPDATE, and DELETE operations on tables that opt into audit logging. Auth events (sign-in, sign-out, failed attempts, role changes) are always logged. You can extend logging to custom events via the audit-log module API.
Compliance is a feature. Ship it from day one.
Compose the audit-log module with multi-tenancy and RBAC. Your enterprise buyers get the audit trail they need before the procurement conversation starts.
Free €0 · Pro €29/mo · Business €59/mo · Enterprise custom. See full pricing. Prices may change before general availability.