ELU is a product intelligence system aimed at engineering, product, and UX teams shipping with AI assistance. It watches how real users move through software, surfaces bugs and UX friction, and gives product teams a path to the fix , with the goal of catching the problems that pile up when features ship faster than teams can analyze them. The launch frames a specific pain point: AI coding tools have compressed release cycles, but understanding what breaks for users in production has not kept up.
Under the hood, ELU learns where real users struggle, generates fixes, tests them with synthetic users in a simulated environment, and auto-merges validated fixes into production . It is designed to detect customer-facing issues, trace them back to the code, and ship fixes end to end , going beyond click heatmaps to flag confusing flows, latency, silent failures, feature problems, and behavioral issues that traditional analytics miss . It plugs into the stack most product teams already run, including GitHub, Linear, Jira, PostHog, Amplitude, Mixpanel, Slack, Supabase, Claude, and Codex, with an on-premise option for customers that need stricter data handling.
The company is based in San Francisco and was co-founded by Amir Sorhan Karimloo (CEO) and Ali Ajam (CTO) , who are building ELU through a16z Speedrun as part of the SR007 cohort. This launch coincides with the team preparing to show the product publicly at Speedrun Demo Day, positioning ELU as a continuous feedback loop between production usage and the codebase rather than another dashboard for teams to monitor.
Comments (10)
Sign in to join the discussion.
N
Nadia Oyelaran12d ago
Self-healing software is a bold phrase to put on a landing page before anyone has seen it heal anything. Prove it on a gnarly race condition and I'll believe.
T
Tove Lindqvist12d ago
Every "self-healing" demo I've seen is a scripted bug with a scripted fix. Show me ELU catching something you didn't plant.
K
Kiril Stoykov12d ago
The jump cut from the terminal to the dashboard around 0:18 is clean, but the voiceover is doing that LinkedIn-podcast cadence. Trust the product, drop the gravitas.
R
Raj Pillai12d ago
Cool, now the real questions: webhook payload shape, retry policy, and do you rate-limit per repo or per org? Docs link or it didn't launch.
M
mimi12d ago
How many people built this? I need to know if I should feel inspired or deeply inadequate before my 3pm standup.
Y
Yusra Benali12d ago
Who owns the fix when ELU pushes a patch at 2am and it breaks staging? The ops org chart implications here are spicier than the tagline suggests.
H
Hiroaki M.12d ago
Noob question but if ELU rewrites my code to fix a user friction, does it also update the PRD? Asking because my PM brain just short-circuited.
P
Parker Odegaard12d ago
Reminds me of what Sentry wanted to be before it became a logging product. If ELU actually closes the loop, that's a different animal.
Z
Zara H.12d ago
Building in roughly this space and genuinely rooting for you, though I'd argue "understanding UX" and "patching bugs" are two very different companies. Which one is ELU in 18 months?
D
Dmitri Varga12d ago
Clicked the site on mobile and the hero text wraps weird on my phone. First impression for a product called self-healing is a little ironic.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
ELU
Make your software improve itself
Make your software improve itself
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
ELU is a product intelligence system aimed at engineering, product, and UX teams shipping with AI assistance. It watches how real users move through software, surfaces bugs and UX friction, and gives product teams a path to the fix , with the goal of catching the problems that pile up when features ship faster than teams can analyze them. The launch frames a specific pain point: AI coding tools have compressed release cycles, but understanding what breaks for users in production has not kept up. Under the hood, ELU learns where real users struggle, generates fixes, tests them with synthetic users in a simulated environment, and auto-merges validated fixes into production . It is designed to detect customer-facing issues, trace them back to the code, and ship fixes end to end , going beyond click heatmaps to flag confusing flows, latency, silent failures, feature problems, and behavioral issues that traditional analytics miss . It plugs into the stack most product teams already run, including GitHub, Linear, Jira, PostHog, Amplitude, Mixpanel, Slack, Supabase, Claude, and Codex, with an on-premise option for customers that need stricter data handling. The company is based in San Francisco and was co-founded by Amir Sorhan Karimloo (CEO) and Ali Ajam (CTO) , who are building ELU through a16z Speedrun as part of the SR007 cohort. This launch coincides with the team preparing to show the product publicly at Speedrun Demo Day, positioning ELU as a continuous feedback loop between production usage and the codebase rather than another dashboard for teams to monitor.
Comments (10)
Self-healing software is a bold phrase to put on a landing page before anyone has seen it heal anything. Prove it on a gnarly race condition and I'll believe.
Every "self-healing" demo I've seen is a scripted bug with a scripted fix. Show me ELU catching something you didn't plant.
The jump cut from the terminal to the dashboard around 0:18 is clean, but the voiceover is doing that LinkedIn-podcast cadence. Trust the product, drop the gravitas.
Cool, now the real questions: webhook payload shape, retry policy, and do you rate-limit per repo or per org? Docs link or it didn't launch.
How many people built this? I need to know if I should feel inspired or deeply inadequate before my 3pm standup.
Who owns the fix when ELU pushes a patch at 2am and it breaks staging? The ops org chart implications here are spicier than the tagline suggests.
Noob question but if ELU rewrites my code to fix a user friction, does it also update the PRD? Asking because my PM brain just short-circuited.
Reminds me of what Sentry wanted to be before it became a logging product. If ELU actually closes the loop, that's a different animal.
Building in roughly this space and genuinely rooting for you, though I'd argue "understanding UX" and "patching bugs" are two very different companies. Which one is ELU in 18 months?
Clicked the site on mobile and the hero text wraps weird on my phone. First impression for a product called self-healing is a little ironic.