What does EZLogs actually do?
It records every request, background job, and database change in your app, links them by user action, and turns each chain into one plain-English card — so anyone on your team can read what happened, not just the engineers.
Can I ask it questions, and will it tell me when something changes?
Yes. Ask in plain English and you get a cited answer — every number clicks back to the events behind it. You can also pin a question (“tell me when a trial account goes quiet for 3 days”) and EZLogs watches it for you, notifying you in-app, by email, or in Slack the moment the answer changes. It only ever notifies — it never writes anything back into your app.
Will it slow down my app?
No. The agent runs out-of-band: events are buffered in memory and shipped to EZLogs over a separate connection. If our service is down, the agent fails open and your app keeps running. Average overhead in benchmarks: under 1 ms per request.
What happens if EZLogs is down?
Your app keeps serving traffic. The agent buffers up to 10,000 events in memory and retries with exponential backoff. If the buffer overflows, it drops the oldest events — never the customer's request.
How is this different from Datadog, New Relic, or Honeycomb?
Those tools are for engineers, and they answer "is the system healthy?" EZLogs is for everyone, and it answers "what happened to my customer?" We don't compete with metrics. We're the layer above them.
Do you store my customer data?
We store the events your app sends us — request paths and parsed params, job names, table names, and the before/after values of the columns that changed. We never store raw request bodies or response bodies. Field-level redaction is on by default for any field matching password, token, secret, api_key, credit_card, and more — the value is masked before it ever leaves your app.
What languages and frameworks are supported today?
Ruby on Rails (Sidekiq, ActiveJob, ActiveRecord) and Next.js (App Router, Pages Router, Server Actions, Prisma, Drizzle, supabase-js, BullMQ, Inngest, Trigger.dev, Upstash, Supabase Queues).
Can I self-host?
Not yet. Self-host is on the post-launch roadmap. If self-hosting is a hard requirement for you, email us — we want to talk.
Is the AI explanation accurate?
The cards, titles, and timeline are built without AI. AI is optional and only writes the extra explanation, using the structured events your app actually sent. It never invents data. If it doesn't know, it says so. Every generated explanation is cached and reproducible — re-running the same action produces the same words.
Can I export my data?
Yes. /settings/data-export gives you a full JSON archive of every action, event, actor, and entity we have on file. Available to every account — GDPR Article 20 compliant.
Is EZLogs free?
Yes. EZLogs is free while it's in beta, with generous usage limits. We will never charge you without you explicitly choosing a paid plan, and we'll announce any pricing well in advance.