u/Worried_View6544

Five years ago, most AI discussions were about models.

Today, the bottleneck is starting to look very different.

Data centers are consuming enormous amounts of electricity. Utilities are struggling to keep up, and governments are starting to treat AI infrastructure as industrial policy rather than just a tech issue.

It raises an interesting question:

Will the countries that lead AI be the ones with the best models, or the ones that can build power generation, data centers, semiconductor capacity, and grid infrastructure fast enough to support them?

It feels like AI is becoming as much an infrastructure race as a software race.

Curious how others here see it.

https://preview.redd.it/qfe6nclxpjbh1.png?width=1536&format=png&auto=webp&s=fed40a744f5e3b9ad8d6886e3a3cd9b6505121d8

https://reddit.com/link/1umwedb/video/xesou87bc4bh1/player

It's not about replacing developers. It's just satisfying when you come back and the code is clean, readable, and does exactly what you asked. 😄

I've seen a lot of people lately saying that AI coding tools have made n8n obsolete.

Instead of taking that at face value, I spent a few days digging into the numbers.

Here's what stood out:

• n8n's valuation reportedly grew from $2.5B to $5.2B in about 7 months.
• NVIDIA invested.
• SAP invested and is integrating n8n into its products.
• 150k+ GitHub stars.
• 100M+ Docker pulls.
• Reported ARR of over $40M with strong growth.

That doesn't really look like a product that's dying.

I think a lot of people are comparing tools that solve different problems.

Coding agents like Claude Code generate code.

n8n orchestrates workflows, connects services, and serves as infrastructure for automation and AI agents.

From what I've seen, the strongest AI workflows usually combine both rather than choosing one over the other.

Am I missing something? If you think n8n is actually losing relevance, I'd genuinely like to hear why.

I've been building an AI voice agent platform for months now. It's called X1-AI it handles calls, books appointments, talks to customers like a human. Multi-tenant, fully dynamic, built from scratch.

It's not finished.

Not because I lost interest. Not because the idea is bad. But because rent doesn't wait for your product to be ready.

So I stopped. Picked up freelance work to keep the lights on. And every day I open the codebase, look at what I built, and close the laptop to go work on someone else's dream instead.

People talk about SaaS like it's just execution. It's not. It's choosing between your vision and your survival, sometimes every single week.

X1-AI is my first SaaS ever. I built something I'm genuinely proud of voice agents that actually sound human, latency optimizations that took weeks to figure out, architecture I designed from zero.

It feels like having a kid you can't afford to raise yet.

I'm not posting this for sympathy. I'm posting because I know some of you are in the exact same place. Building something real, on borrowed time.

I'll finish it. Just not today.

Spent the last few weeks deep in LiveKit + voice pipeline debugging, and hit a bug that I think a lot of people building voice agents will eventually run into: calling session.say() inside a tool call context can cause 20-30 second hangs. Took me way too long to track down.

The bigger lesson wasn't the bug itself — it was realizing that latency in voice AI isn't one number, it's death by a thousand cuts:

• Intent classification running synchronously? +1 second.
• Tool call blocking the response? Dead air while the user wonders if it's still listening.
• LLM "thinking" before answering a simple FAQ? Feels broken even at 2-3 seconds.

What actually moved the needle for me:

• Converting routing/classification to fully async — cut one bottleneck from ~1.2s to ~2ms
• Running filler audio + tool calls in parallel instead of sequentially
• Bypassing the LLM entirely for structured data collection (bookings, forms) — just extract + respond directly

Curious what's been the trickiest latency issue for others building voice agents — LiveKit, Pipecat, or otherwise? Always good to compare notes on what's actually a known issue vs.