Founder here. A few things worth surfacing up front since it's been ~10 minutes:
The pitch is small. It's a Rails activity log gem that joins HTTP + Sidekiq + ActiveRecord into one card per user action. Not metrics, not APM, doesn't replace Datadog. The audience for the card is the rest of your company, not engineers.
The post above is the boring lesson from week one of having real users — the install template had a placeholder URL on launch day, and that placeholder cost me my first conversion. 0.1.8 is on RubyGems with the fix (pre-filled SaaS URL, reads the API key from ENV, one env var to set).
Happy to answer specifics: how correlation works across `perform_later` job boundaries without thread-locals, why MCP is unlimited at every paid tier (data-only, the customer's own AI narrates), what "read-only by design" rules out and why.
The pitch is small. It's a Rails activity log gem that joins HTTP + Sidekiq + ActiveRecord into one card per user action. Not metrics, not APM, doesn't replace Datadog. The audience for the card is the rest of your company, not engineers.
The post above is the boring lesson from week one of having real users — the install template had a placeholder URL on launch day, and that placeholder cost me my first conversion. 0.1.8 is on RubyGems with the fix (pre-filled SaaS URL, reads the API key from ENV, one env var to set).
Happy to answer specifics: how correlation works across `perform_later` job boundaries without thread-locals, why MCP is unlimited at every paid tier (data-only, the customer's own AI narrates), what "read-only by design" rules out and why.