This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
EZLogs
Know what your app and its AI agents did, in plain English
EZLogs turns what your Rails or Next.js app does into an activity log anyone on the team can read. Requests, background jobs and database changes become one sentence per action, with every step behind it. New: alerts. Ask "tell me when a refund fails" and hear back as it happens, in the app, by email or in Slack. AI agents show up next to your people, and your own AI can ask what happened over MCP. Read-only by design. Free in beta.
at three jobs in a row the same message kept landing in the engineering channel: "can someone check what this user did yesterday?" someone opens the logs, greps an email, scrolls past the SQL noise, follows the request into the background jobs, and writes back a sentence support can read. i got tired of being the translator, so i wrote the thing that translates.
how it works: one gem for Rails, one npm package for Next.js. it captures requests, background jobs and database changes, groups them into actions, and shows each one as a sentence. AI agents show up as actors next to your people. "Refund RF-3JRW failed: card expired, by Rebooking assistant." click it and you see every step behind it.
what's new since the last launch here: - alerts. write "tell me when a refund fails" and hear back as it happens (checked every 5 minutes), in the app, by email or in Slack - your own AI can ask it what happened over MCP (Claude, ChatGPT, Cursor, Codex). it's in the Claude connector directory now - Pulse, rebuilt: where every person, AI agent and record stands right now - a live demo with no signup, and it's free while in beta
things i was strict about: - read-only. it never writes back into your app, no write credentials anywhere - sensitive fields are masked inside your app before anything is sent - every count and every alert is computed from the real events, so you can click through to the actions behind it
the demo is a small ferry company on a stormy night: an AI rebooking assistant handles 48 disrupted bookings, two rebookings get rejected, three refunds fail. app.ezlogs.io/demo
one thing i'd really like to hear: what's the "what happened?" question people in your company keep asking engineers? that's exactly what i want EZLogs to answer.
About EZLogs on Product Hunt
“Know what your app and its AI agents did, in plain English”
EZLogs was submitted on Product Hunt and earned 2 upvotes and 7 comments, placing #146 on the daily leaderboard. EZLogs turns what your Rails or Next.js app does into an activity log anyone on the team can read. Requests, background jobs and database changes become one sentence per action, with every step behind it. New: alerts. Ask "tell me when a refund fails" and hear back as it happens, in the app, by email or in Slack. AI agents show up next to your people, and your own AI can ask what happened over MCP. Read-only by design. Free in beta.
On the analytics side, EZLogs competes within SaaS, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how EZLogs performed against the three products that launched closest to it on the same day.
Who hunted EZLogs?
EZLogs was hunted by Razvan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of EZLogs including community comment highlights and product details, visit the product overview.
hey PH, razvan here. i built EZLogs.
at three jobs in a row the same message kept landing in the engineering channel: "can someone check what this user did yesterday?" someone opens the logs, greps an email, scrolls past the SQL noise, follows the request into the background jobs, and writes back a sentence support can read. i got tired of being the translator, so i wrote the thing that translates.
how it works: one gem for Rails, one npm package for Next.js. it captures requests, background jobs and database changes, groups them into actions, and shows each one as a sentence. AI agents show up as actors next to your people. "Refund RF-3JRW failed: card expired, by Rebooking assistant." click it and you see every step behind it.
what's new since the last launch here:
- alerts. write "tell me when a refund fails" and hear back as it happens (checked every 5 minutes), in the app, by email or in Slack
- your own AI can ask it what happened over MCP (Claude, ChatGPT, Cursor, Codex). it's in the Claude connector directory now
- Pulse, rebuilt: where every person, AI agent and record stands right now
- a live demo with no signup, and it's free while in beta
things i was strict about:
- read-only. it never writes back into your app, no write credentials anywhere
- sensitive fields are masked inside your app before anything is sent
- every count and every alert is computed from the real events, so you can click through to the actions behind it
the demo is a small ferry company on a stormy night: an AI rebooking assistant handles 48 disrupted bookings, two rebookings get rejected, three refunds fail. app.ezlogs.io/demo
one thing i'd really like to hear: what's the "what happened?" question people in your company keep asking engineers? that's exactly what i want EZLogs to answer.