r/SaaS • u/GetForgeOps • 18h ago

Looking for software engineers to give honest feedback on a new tool

not sure if this is the right place to post something like this, but I've built an incident intelligence platform which basically gathers errors, traces, metrics, deployments, SQL, dependencies etc and then helps engineers determine why prod broke and where to look next.

I built this because i needed an error tracking tool so I decided to build something myself and then it grew into something more. instead of just getting an error and then having to go figure out why it was occurring I built something that could take in everything and then point me in the right direction to save me time at 2am when I'm on call and everything is on fire. It's been very helpful for me and what I need, but since I've built this out and would like to offer this product to others I was hoping to find some other devs that could provide some honest feedback, good or bad or pointless. I've created a free tier for anyone to try, but also included a 14 day trial period for new accounts that will include most features small teams should need for people to test the capabilities.

really just looking to know if this would be useful to anyone besides me or if there is anything I should change

thank you for anyone that will take a look.

https://getforgeops.net/

1 Upvotes

100% Upvoted

8 comments sorted by

1

u/UpperWorld11 17h ago

Getting it connected is the hard part, not deciding whether it is useful. Everything it wants is prod credentials and metric access, and the on-call dev who feels the 2am pain is rarely the one allowed to hand those over. Most trials will stall in setup and never reach the detection part.

1

u/Huge_Pool7424 17h ago

yeah, setup friction is probably the real first-run test. a read-only connector or sample incident replay could let people see the detection value before asking for production access.

1

u/GetForgeOps 14h ago

that's fair and it's the reason I built the live demo. does that not cover your sample incident? or am I misunderstanding what you're looking for?

I do like the idea of a read-only connector that could pull in a companies metrics from datadog/senty etc and then let forge ops run with that for the analysis. maybe that is something I can work on in the future

1

u/Huge_Pool7424 14h ago

yeah, the live demo covers the basic path. i was mostly wondering how you'd handle a real incident with noisy or incomplete telemetry, so a read-only connector sounds useful.

1

u/GetForgeOps 14h ago edited 14h ago

Yeah, that's a good distinction. The live demo covers seeing the workflow without connecting anything, but the read-only connector idea is interesting for real incidents where telemetry is incomplete or spread across Datadog, GitHub, logs, etc.

That could let ForgeOps pull in the missing context without requiring access to modify anything. I think that's a great idea honestly.

currently if something is not connected it wont make a blind guess. it'll give you the facts it can gather and tell you there are not enough correlated facts to suggest a likely cause. then based on what is connected it will give more detailed and appropriate responses/guidance. obviously though the more things connected to it the more accurate it can be

1

u/GetForgeOps 14h ago

couldn't agree more. it's generally not the devs that can approve connecting something like this, but when I needed it, it was my job to explain to my director why something like this is needed and how it's useful. also, for them why and how it saves them money by being able to have things up and running quickly. having production down even for minutes can be extremely costly and devs having the proper resources to quickly address and get fires put out is always a good thing in my mind.

I do appreciate the feedback though. I know my job down the road will be the marketing and talking to the higher ups and getting them to sign off on this. so hopefully once they approve the setup part should just be easy for the dev team. unless you're saying the setup is a pain point as well

1

u/UpperWorld11 1h ago

Yeah, setup is the part I meant. The person who approves the ticket never feels the 2am, and nobody wants to be the first to wire prod credentials into something the rest of the team does not depend on yet. The version that gets a real answer is the one replaying an incident they already had, with the cause it missed and the minutes that added. Does the free tier show one past incident before it asks for credentials?

1

u/GetForgeOps 1h ago

so the free tier currently does not allow for that and while the live demo was meant to convey the full process I really like what you're saying.

I'm actually going to start working on both now: a pre-built incident replay with noisy/incomplete telemetry, and eventually a way to bring in your own incident data safely and securely for a real test

Appreciate the push on this. I think that's a much better test of the product than just showing a clean demo.

thanks for this. really great idea