Ask anyone at ETAPX to describe John Ridge and you'll get some version of the same image: a whiteboard, a marker already uncapped, an idea he can't wait to walk someone through. That's the energy John Ridge, CTO of ETAPX, brings to introducing Podz, a new set of dedicated workspaces he built inside Influxx for keeping separate projects separate — spelled deliberately with a z, a lighthearted wink at Whistlr's much larger community spaces, Pods, which do something else entirely. Podz didn't arrive as a roadmap item handed down from a planning meeting; it started as John Ridge's own fix for his own mess, because the CTO of ETAPX ran into the same problem anyone juggling more than one project eventually runs into — work doesn't stay in its lane on its own. This is his introduction to PX News readers, and fittingly, it's also the story of the first thing he built because he needed it himself.
Meet ETAPX's CTO
John Ridge has been ETAPX's CTO long enough that most people who work with him no longer stop to describe what he does — he's just there, in the same planning conversations as AJ, the same code reviews as engineers three years into their careers. PX News hasn't run a proper introduction to him until now, mostly because he's never been the type to angle for one. He's the CTO of ETAPX in the way the title is supposed to work and rarely does: hands-on, reachable, and about as far from a distant executive as the job allows.
Ask him what he actually does day to day and he'll undersell it, which is itself the tell. "I write code, I review other people's code, I sit in on product conversations I probably don't need to be in, and I build things when I notice something's broken," he says. "The 'CTO' part is mostly what people call it after the fact." That undersells a real range. John Ridge, ETAPX's CTO, works alongside AJ on the technical shape of everything the company ships — Whistlr, GLSRM, Influxx, all of it. But the instinct that actually defines him isn't strategic distance. It's proximity — to the code, to the product, to the exact moment a workflow stops making sense.
"I've never been able to just describe a problem to someone else and wait for it to get fixed. If something's broken and I'm the one who noticed it, there's a pretty short list of reasons I wouldn't just go fix it myself."
— John Ridge, CTO, ETAPX
That instinct is the entire reason Podz exists. Podz wasn't commissioned, and it wasn't the output of a roadmap review — it came from ETAPX's CTO hitting a wall in his own work inside Influxx, badly enough and often enough that fixing it himself started to look like the faster option than filing it away for someday.
The Problem That Kept Bugging Him
Influxx is ETAPX's flagship agentic environment, built around a single idea: you describe an outcome and the work actually gets carried out, end to end. John Ridge uses it the way plenty of people at ETAPX do — for engineering work inside the ADE, sure, but also for the other threads a CTO ends up holding at once: a feature he's shaping for next quarter, a set of notes turning into an argument for a planning meeting, a fix he told someone he'd have by Friday. None of that is unusual. Most people doing real work end up holding more than one thread at a time.
What started to bother him wasn't any single task. It was what happened when he moved between them. Influxx was good — is good — at carrying a task through to done, but nothing about picking up a new thread stopped the last one from quietly leaking into it. Context from one initiative would still be sitting there when he opened something completely unrelated — not broken, exactly, just never fully out of the way.
When Everything Lives in the Same Place
The problem sharpened the more initiatives he had running at once, which — being ETAPX's CTO — was more or less always. "It wasn't that I'd lose work," John Ridge says. "It was that I'd sit down to make a decision on one thing and realize half my head was still occupied by a completely different thing I'd been looking at twenty minutes earlier. Switching should feel like opening a door into a different room. It felt more like everything happening in the same room at once."
That gap — between "I should focus on this one thing" and "everything is bleeding into everything else" — is familiar to anyone managing several projects at once: a solo builder running a couple of ideas in parallel, or a small team splitting attention across a handful of initiatives. What made it land differently for John Ridge is that he was in a position to actually do something about it.
The Moment Podz Clicked
There wasn't one dramatic breaking point — John Ridge is fairly insistent about that — but there was a specific afternoon that crystallized it. He'd sat down inside Influxx to make a call on a feature he'd been circling for a week, and instead of picking up cleanly where he'd left off, he found himself scrolling past context from two entirely different efforts just to get back to the one he meant to work on. None of it was lost. All of it was just in the way.
"I remember thinking, this is a dumb problem for us to still have," he says. "We build a product whose entire pitch is that it carries work through to an outcome without you babysitting it. And here I was babysitting the boundary between three different outcomes, by hand, every time I switched between them. That's exactly the kind of friction Influxx is supposed to remove, and instead I was manufacturing more of it myself, one afternoon at a time."
The fix he landed on wasn't a smarter way to search through everything, or a better tagging system layered on top of the mess. It was simpler, and obvious enough that he says he felt a little embarrassed it took this long: give every distinct thread of work its own contained space. Not a filter. Not a label. An actual separate place, so the tasks, context, and history of one project stay with that project — and out of every other project's way. That idea became Podz.
What Podz Actually Let You Do
Strip away the origin story and Podz is a straightforward idea, which is exactly how John Ridge wanted it to stay. A Podz is a dedicated workspace inside Influxx where everything related to one specific project, initiative, or part of your work lives together — its tasks, its context, its history — contained in its own space instead of mixed in with everything else you happen to be juggling.
That containment is the entire point. Switching between different threads of work no longer means starting from zero, and it no longer means one project's details quietly bleed into another's. A solo builder running two or three initiatives at once — or a small team splitting a handful of efforts across a few people — can move between them the way John Ridge wanted to: like opening a different door, not wading back into the same crowded room.
- A contained space per effort: Every project, initiative, or distinct piece of work gets its own Podz, holding its tasks, context, and history together in one place.
- Nothing bleeds between them: What Influxx is carrying for one Podz stays there — it doesn't surface while you're heads-down in a completely different one.
- Switching without starting over: Moving between Podz means picking up exactly where that specific thread left off, instead of re-establishing context every time you change focus.
- Room for more than one person: A small team can split attention across several Podz, with everyone clear on which one they're in and what belongs there.
- As many as the work calls for: Podz scale with however many distinct efforts someone actually has running — one for a quiet week, several for a busy one.
Built for Parallel, Not Just Organized
It would be easy to describe Podz as a folder system for agentic work and undersell what it's solving. Folders organize things you've already finished. Podz organizes things still in motion — tasks Influxx is actively carrying out, decisions still waiting on a check-in, context still being built up as the work progresses. That difference matters because the moment you're managing more than one active effort is exactly the moment a simple list stops being enough. Podz is built for that moment: not tidiness for its own sake, but the ability to genuinely run several things in parallel without any of them quietly costing attention from the others.
Why "Podz" and Not "Pods"
The name is deliberate, and John Ridge will tell you that with a grin before you finish asking. Whistlr already has a feature called Pods — large, Discord-style community spaces with channels, roles, and room for up to 20,000 members, built for structured community building. It's an established part of Whistlr, and it has nothing to do with what John Ridge built inside Influxx. Different product, different problem, different scale entirely.
What the two share isn't the feature. It's the instinct underneath it: give people a contained space of their own, sized for what they're actually trying to do. Whistlr's Pods does that for community — thousands of people, channels, roles, a gathering place. John Ridge's Podz does it for a single person or small team keeping one initiative's agentic work from spilling into another's. Same underlying idea, applied to a problem that has nothing to do with community at all.
"I loved that Whistlr already had this idea of giving people their own contained space, and I wanted to tip my hat to it, not step on it. So Podz, with a z — same spirit, a completely different job. I wasn't trying to be clever. I was trying to be honest about where the idea rhymes and firm about where it doesn't."
— John Ridge, CTO, ETAPX
He's unbothered by the chance the similar names cause a little confusion at first glance, since he thinks the distinction is easy to hold once you hear it. "Pods, no z, is where a community lives — could be twenty people, could be twenty thousand," he says. "Podz, with a z, is where one person's or one small team's project lives, separate from everything else they've got going. Once you know that, you're not going to mix them up again. And if someone asks 'wait, is this the same as Pods?' — that means they already know about the other one, which is a pretty good problem to have."
A Day Inside Podz
The clearest way to understand what changed is to walk through a day the way John Ridge actually uses it now. He opens Influxx in the morning with three or four things genuinely in flight — a feature he's reviewing in the ADE, notes he's shaping into a proposal, a fix somebody flagged the night before. Each one lives in its own Podz. Open the one for the feature review, and everything sitting there is exactly what belongs to that effort: the task, the context Influxx has been building around it, the history of what's already happened. Nothing from the proposal, nothing from the overnight fix, crowds in.
Close it, open the Podz for the proposal, and the switch isn't a mental reset — it's closer to walking into a different room where a familiar conversation is already waiting exactly where he left it. By the afternoon he's moved through all three or four without any of them muddying the others, and — this is the part he says he still notices, months after building it — without spending any of his own attention keeping them apart. Influxx does that now. He doesn't have to.
For Solo Builders and Small Teams Alike
The same relief shows up outside ETAPX. A solo builder juggling a side project, a freelance client, and a half-formed weekend idea can give each one its own Podz instead of letting them collide in one shared workspace. A small team gets the same clarity multiplied across people — everyone with a clear answer to "which Podz am I in, and what belongs here," instead of relying on memory or a shared document to keep the work from colliding.
"I'm one person running two products at once, which sounds fine until you're actually doing it. Before Podz, opening Influxx felt like walking into a room where three different conversations were happening at once and I had to figure out which one I'd been part of. Now I open the Podz for whichever thing I'm actually working on, and that's the only conversation in the room. It sounds small. It changed how much I could actually hold in my head at once."
— Marcus Webb, early Influxx user
What Podz Says About How ETAPX Builds
It would have been easy for John Ridge to raise the friction he was feeling, hand it to a team, and wait for it to reach a roadmap. Plenty of CTOs would stop there, and reasonably so — there's a version of the job that's mostly about setting direction, staying a level removed from the actual building. That was never going to be his version of it.
"If I notice something's broken in a product I helped build, and I've got a pretty good idea of what would fix it, sitting on that felt worse than just building it," he says. "AJ moves the same way about product. I think that's part of why we work well together — neither of us is especially patient about the gap between 'I see the problem' and 'I fixed the problem.'" That echoes the founder-led, ship-fast culture AJ has talked about publicly — product authority staying close to the people who feel a problem firsthand, instead of traveling through layers of approval before anything changes.
"The best version of this job isn't standing at a distance and pointing at problems. It's still being close enough to the work that you notice them yourself, and stubborn enough that you go fix them. Podz didn't need a committee. It needed me to be annoyed enough, often enough, to finally do something about it."
— John Ridge, CTO, ETAPX
Podz is a small feature in the scheme of everything Influxx does. But it's a useful data point about how ETAPX operates at the level that matters most — not the size of the fix, but the distance between noticing a problem and shipping the solution. ETAPX's CTO ran into friction in his own work, decided it was worth solving properly, and built the fix into the product everyone else uses too. That's a fairly direct pipeline from "this bugs me" to "this is live" — the same pipeline AJ has built the rest of the company around.
Frequently Asked Questions
Who is John Ridge?
John Ridge is the CTO of ETAPX, working closely alongside founder and CEO AJ on the technical direction of everything the company builds, including Whistlr, GLSRM, and Influxx. He's known for staying hands-on — reviewing code, sitting in on product conversations, and building fixes himself when something isn't working. Podz, covered in this piece, is a direct result of that instinct.
What is Podz?
Podz is a set of dedicated workspaces inside Influxx, ETAPX's flagship agentic environment. Each Podz holds everything related to one specific project, initiative, or part of your work — its tasks, its context, its history — in a contained space, so switching between different threads of work doesn't mean starting from zero or letting unrelated projects bleed into each other.
Is Influxx's Podz the same thing as Whistlr's Pods?
No, and the spelling is a deliberate signal that they're different features. Whistlr's Pods (no z) are large, Discord-style community spaces with channels, roles, and room for up to 20,000 members, built for organized community building. Podz (with a z), built by John Ridge inside Influxx, is something else entirely — a contained workspace for one person's or one small team's project or initiative, with no community, channels, or membership involved. The name is a lighthearted nod from one feature to the other, not a shared feature or a rebrand of either one.
Who is Podz built for?
Anyone using Influxx to juggle more than one initiative at a time — a solo builder running a couple of projects in parallel, a small team splitting attention across several efforts, or anyone who has noticed context from one piece of work creeping into another. If you've only got one thing going, you may not need it yet. The moment you have two, Podz starts earning its keep.
Is Podz available now?
Yes. Podz is live inside Influxx today, available alongside the rest of the environment — including the ADE and its mobile app — for anyone who wants to give their projects their own separate space instead of sharing one crowded one.
Back to that whiteboard image this piece opened with: John Ridge, marker in hand, walking a room through an idea he clearly can't wait to explain. Podz is a small example of the same instinct pointed inward — a CTO who noticed his own work getting tangled, sketched out the fix, and shipped it into the product everyone else uses too. Whistlr's Pods will keep being where big communities gather. Podz, with a z, is where one person's or one team's work finally gets to stay untangled from everyone else's — including, these days, John Ridge's own.
