Superlog (YC P26)

@arseniycodes and it’s just the beginning!

today Nico and I are watching superlog.sh. best teams love to build and ship. but now they're drowning in bugs and alerts. our mission is to help them get rid of toil, and go back to doing what they love: making things people want.

@arseniycodes love it!

there's no better feeling in the world than to see something you've built being useful for somebody. just watched a new signup from our launch today use superlog.sh for 2 hours. he's using our tools in more creative and efficient ways I could have imagined.

making the world bug-free

@nicolomagnante @arseniycodes here we are!

proud of the new dashboards we just shipped to superlog.sh

@nicolomagnante @Totzenberger @vikramvadrevu @aresta_katz 👀

yc dinner pt.5: butter chicken, observability and early-career mistakes @Totzenberger @vikramvadrevu @aresta_katz

@arseniycodes love it 🤖

we're in the middle of @ycombinator. we had revenue. and we decided to pivot. here's why: in our previous startup, working w/ huge enterprises and high volumes, keeping critical services stable and online 24/7 was by far our top priority. luckily @arseniycodes spent years inside Datadog, building exactly the kind of observability infrastructure most teams pay millions for. so when we got to the batch, we kept getting the same question from other founders: "how did you set up observability and auto-debugging internally? can we use it?" every startup is living the same broken loop: - Sentry/Datadog/Grafana fires a thousand alerts, half are duplicates - until something serious breaks - panic, logging was not done properly - someone copy-pastes a stack trace into Claude at 11pm - finally, the bug gets fixed - until the next one we think this is not the way things should be done in 2026, so we pivoted. today we're building @superlogYC a wizard installs OpenTelemetry across your repo in one click, then runs every single day to add the logs, alerts, and dashboards your team forgot. when something breaks, an agent groups the noise into one incident, investigates with full context (logs, traces, metrics, recent deploys), and either ships a clean PR or pulls in the engineers who can solve it. one mergeable PR per incident. posted in Slack. merge it, ignore it, or open it in Claude Code and tweak. if your team is drowning in alerts, paying too much for telemetry that never actually solves anything, or running integrations that quietly break in the background, sign up in the first comment and let the agent do the work.

@nicolomagnante @arseniycodes let’s puuuuush

me: we need a fix for the demo in 15 min, but we gotta hop in the waymo rn 🤨 @arseniycodes : / 💻 \ /\

@pulsentyc @arseniycodes @vikchuppala @sixtensor @ClodoAI @imagineagi @neo_lky @skygodkingdom @jpmorgan @Google luma.com/gtjdjfex