Evidence requests eat engineering time
Every auditor sample and every customer security review becomes a bespoke SQL favor. It should be an export endpoint.
Use case
Auditors ask four questions about your logging: is it complete, is it tamper-proof, how long do you keep it, and can you produce it. Softechlog is a yes to all four.
The problem
Every auditor sample and every customer security review becomes a bespoke SQL favor. It should be an export endpoint.
If your team can UPDATE the audit table, your logs aren’t evidence. Append-only needs to be structural, not policy.
A retention policy that a human executes quarterly is not a control. It has to run on a schedule, uniformly, and be observable.
How it works
Logins, role changes, key lifecycle, exports, billing — roughly eight track() calls at your backend choke points.
Append-only storage, actor snapshots, and hourly plan-based retention (30/90/365 days) happen without ongoing work.
Filtered CSV/JSON export for auditor samples and customer reviews — one authenticated GET, on every plan.
# Auditor wants Q1 role changes? One command: curl -H "Authorization: Bearer $SOFTECHLOG_SECRET_KEY" \ "https://api.softechlog.com/v1/events/export?format=csv&action=member.role.changed&from=2026-01-01T00:00:00Z" \ -o role-changes-q1.csv
FAQ
No vendor can claim that — SOC 2 covers your whole organization. Softechlog gives you the logging controls auditors look for: completeness, immutability, enforced retention, and exportable evidence. Your auditor has the final word.
30 days on Free, 90 on Growth, 365 on Scale — enforced automatically every hour. For longer horizons, export on a schedule to your own warehouse.
Events are stored in our managed PostgreSQL infrastructure, isolated per project, encrypted in transit. See the security page for the full model.
Keep reading
Ready to try it? Beta partners get hands-on onboarding and a schema review.
Request Beta Access