PX Campus is growing again. Not in the loud, ribbon-cutting way that usually comes with a company announcement, but in the quieter way that anyone who spends a week in the building would notice without being told: more faces at the kitchen table, more whiteboards covered before lunch, more teams that used to be two people and are now a real pod with its own rhythm. ETAPX has been through stages like this before, and every one of them has changed what the company is capable of building. This one is no different. Here's an honest look at what this new stage of growth on PX Campus actually means — for the people who work here, for the products they build, and for the community that uses Whistlr, GLSRM, Ocsidian, Influxx, and in.between every day.
PX Campus Growth: What's Actually Changing
PX Campus has always meant two things at once. It's the literal place where the ETAPX team works — a Bay Area headquarters that AJ, our founder and CEO, chose on purpose over a remote-first default. And it's shorthand for a culture: the open, argumentative, show-your-work way the company builds. When we say PX Campus is going through another stage of growth, we mean both halves of that definition are stretching at the same time.
The physical half is the easiest to see. There are more people on the floor than there were a few seasons ago, and more of them are working on problems that didn't exist as full-time jobs until recently. The product lineup has widened — in.between and Nalani joined Whistlr, GLSRM, Ocsidian, and Influxx as a genuinely new kind of product for the company — and each product has deepened enough that the teams behind them have needed to grow alongside it. Creator Studio living at its own home, Flow live streaming, Minis and WTC Gems, Storefronts and Live Shopping, Podz inside Influxx, GLSRM's mobile presence: none of those run themselves, and all of them have more surface area than they did a year ago.
The cultural half is harder to photograph, but it matters more. Growth is the moment a company either protects the habits that made it good or quietly trades them away for process. This stage of growth is really a test of whether the collisions, the directness, and the "say it out loud before you write it in a doc" instinct that define PX Campus can survive a bigger room. That's the part we've been thinking about hardest, and it's the part most of this piece is about.
It's worth being clear about what this isn't. This isn't a funding announcement, a headcount milestone, or a new office reveal with a date attached. We're deliberately not publishing numbers here, partly because numbers about team size tend to become the story instead of the work, and partly because the honest version of this stage is still unfolding. What we can describe is the shape of the change and the choices we're making to keep it healthy.
Why ETAPX Is Growing Right Now
Growth at ETAPX has never been a goal on its own. The team doesn't hire so the company looks bigger; it grows when the products outgrow the people available to take care of them properly. That's exactly what's happened over the last stretch, and a few forces have been pulling at once.
- A wider product lineup: in.between and Nalani introduced an entirely new discipline to the company — building an AI companion designed to listen more than it talks — alongside the four products that were already here. A new category of product brings new kinds of work with it.
- Deeper products, not just more of them: Whistlr in particular has grown from a social feed into a full platform with Circuits and SubCircuits, Waves, Minis, Creator Studio, Flow, Storefronts, Live Shopping, Halo, Profile Skins, and relationship status. Each of those is its own ongoing responsibility, not a one-time launch.
- A bigger, more international community: Whistlr's international expansion and a steadily growing userbase raise the bar on safety, support, reliability, and polish. A bigger community deserves a team sized to take care of it.
- A commitment to hiring ahead of need: The company would rather invest in capacity before it becomes an emergency than scramble after something breaks. That philosophy means some of this growth is intentionally early.
That last point is the one people outside the company tend to miss. It's tempting for a startup to wait until a team is visibly drowning before adding anyone to it, because waiting feels frugal. In practice, it usually means the people who were already stretched thin spend months onboarding newcomers while also keeping everything afloat, and quality quietly slips in the gap. AJ has pushed hard in the other direction: grow before the pressure peaks, so the people who join have room to actually learn the product before they're asked to carry it.
"I don't want to grow the company because a chart told me to. I want to grow it because the things we've built have gotten big enough that they deserve more people who care about them. Every product we ship is a promise to someone — a creator, a reader, someone journaling at midnight. Growing PX Campus is how we keep those promises without burning out the people making them."
— AJ, Founder & CEO, ETAPX
A Brief History of How PX Campus Has Grown Before
This is not the first time the campus has changed shape, and understanding the earlier stages helps explain why this one feels the way it does.
The single-product stage
In the earliest days, ETAPX was effectively one team working on one idea. Everyone knew everything. A design decision on Monday was common knowledge by Monday afternoon, not because anyone announced it, but because there was only one table and everyone sat at it. That stage produced a lot of the instincts that still define the company: directness, speed, and a low tolerance for decisions made behind closed doors.
The multi-product stage
The second stage arrived as Whistlr was joined by GLSRM, then Ocsidian and Influxx. Suddenly PX Campus wasn't one product team pretending to be a company — it was four genuinely different products sharing one floor, one kitchen, and one increasingly well-worn set of inside jokes. That stage introduced the thing people on the team now call "collisions": the unscheduled hallway conversations where an Influxx engineer overhears a Whistlr bug and realizes it's the same one they fixed in Podz last week. Those collisions became one of the company's biggest structural advantages.
The stage we're entering now
The current stage is defined less by a new product than by maturity across all of them. Each product now has enough users, enough features, and enough history that it needs specialists — people who go deep on one surface rather than spreading across five. That's a healthy sign. It's also exactly the moment when a company's culture is most at risk of fragmenting into separate silos that happen to share a lobby. Everything we're doing to manage this stage is aimed at getting the benefits of specialization without losing the collisions.
How We're Keeping the Culture Intact as the Team Grows
Every growing company says it wants to keep its culture. Fewer can explain what they're actually doing about it. Here are the specific habits PX Campus is leaning on during this stage, and why each one matters.
- Shared spaces stay shared: The kitchen, the common areas, and the long tables are deliberately not carved up by product. A GLSRM editor and an Ocsidian engineer should keep bumping into each other, because that's where some of the best cross-product ideas have always started.
- Newcomers see the whole company, not just their team: People joining during this stage get a real tour of all the products, not just the one they were hired for. You can't have a useful hallway opinion about Whistlr's Storefronts if you've never opened them.
- Decisions stay visible: The "show your work" norm matters more as the room gets bigger. Design reviews, tradeoffs, and the reasoning behind a call get written down where anyone on campus can read them, so nobody has to be in the right meeting to understand why something shipped the way it did.
- Directness scales with kindness: A small team can get away with blunt feedback because everyone already trusts each other. A bigger team has to earn that trust faster, so the norm is still candid, but it's candid with context — say what's wrong, say why, and assume the other person wants the product to be good as much as you do.
- Small pods over big departments: Where possible, teams grow as small, focused pods that own a specific surface end to end rather than as large departments that hand work back and forth. Small groups argue faster, ship faster, and stay closer to the people using what they build.
None of these are revolutionary on their own, and that's kind of the point. Culture isn't protected by a single grand initiative. It's protected by dozens of small, boring defaults that nobody gets to quietly remove because they've become inconvenient.
"The engineering challenge with growth isn't really headcount — it's communication paths. Every new person adds new connections that either carry context or lose it. Our job is to make sure the context keeps flowing: that the person fixing a caching issue in GLSRM knows the Whistlr team solved something similar, and that nobody on campus has to rediscover a lesson the building already learned once."
— John Ridge, CTO, ETAPX
What Onboarding Looks Like on PX Campus Today
One of the clearest signs of a company's growth stage is how it treats people on their first week. At ETAPX, onboarding during this stage is built around a simple idea: new people should understand why things are the way they are before they're asked to change them. That doesn't mean waiting around. It means getting context fast.
Step 1: Use everything
New team members start by actually using the products — posting on Whistlr, joining a few SubCircuits, reading GLSRM the way a regular reader would, trying an Ocsidian project, opening Influxx and Podz, and spending a few nights with in.between and Nalani. The goal is to feel the products as a user before seeing them as a codebase or a design file.
Step 2: Read the history
PX News exists partly for this reason. Much of the reasoning behind major decisions — why Creator Studio moved to its own home, why certain Whistlr development focuses on the latest iOS, why in.between shipped deliberately narrow — is written down in public. New people read it the same way our community can, which keeps the internal story and the public story aligned.
Step 3: Sit in on the collisions
Newcomers are encouraged to spend time around teams they won't be working on directly. Watching how GLSRM makes editorial calls or how the Whistlr team debates a feed change teaches more about the company's values than any slide deck could.
Step 4: Ship something small, early
The fastest way to belong on PX Campus is to ship. New team members are pointed toward a real, small, useful change early — a polish fix, a copy improvement, a performance tweak — so they experience the full loop of building, reviewing, and releasing before they take on anything larger.
"The thing that surprised me most in my first month was how much context I got without asking for it. I'd sit down for lunch and leave knowing why a feature I'd never touched was built the way it was. You don't feel like the new person for long here — mostly because everybody assumes you want to know how the whole thing works, not just your corner of it."
— Jordan, recent PX Campus team member
How Campus Growth Shows Up in the Products You Use
It's fair to ask why any of this should matter to someone who just wants their Whistlr feed to load fast or their in.between journal to remember what they said last week. The answer is that growth on PX Campus is directly tied to the quality of the things we ship. When teams are sized properly, a few things get noticeably better.
- Polish gets its own time: A team stretched thin ships features and moves on. A team with room can come back to the rough edges — the transition that stutters, the setting that's hard to find, the notification that fires one time too many. More people means more of those small fixes actually get prioritized.
- Safety and support keep pace: As the Whistlr community grows, the work of keeping content safe and enjoyable grows with it. Investing in the people behind trust and safety, moderation, and support is non-negotiable during any growth stage.
- Reliability improves: Security and infrastructure are round-the-clock responsibilities. A larger team makes it possible to maintain that focus without leaning on the same few people every time something needs attention late at night.
- Feedback gets answered faster: More people close to the community — in Campus, our Discord server, and inside the apps themselves — means the loop between "someone noticed a problem" and "someone on the team is working on it" keeps getting shorter.
- Cross-product ideas land more often: The more specialists sitting near each other, the more often a solution in one product turns out to be useful in another. That's how shared tools and consistent design language keep emerging across the lineup.
In other words, this stage of growth isn't about ETAPX getting bigger for its own sake. It's about the products getting the care they've earned from the people who use them.
Growth Without Losing Focus: What We're Saying No To
Every growth stage comes with temptations, and it's worth naming the ones we're actively resisting. A bigger team can easily become an excuse to do more things instead of doing the important things better. PX Campus is growing to deepen what already exists, not to scatter energy across a dozen new bets.
That means a few deliberate "no's" during this stage:
- No growth for appearances: We aren't adding roles to make the company look larger or to match what other startups are doing. Every addition should map to a real need in a real product.
- No layers for the sake of layers: Process should exist to remove friction, not to create it. When a new review step or approval gate is proposed, the first question is whether it actually protects quality or just slows people down.
- No quiet trading of culture for speed: If growing faster would mean abandoning the habits that make the company good — visible decisions, shared spaces, candid feedback — we'd rather grow a little slower.
- No overpromising in public: PX News will keep covering what actually happened, including the parts that take longer than planned. Growth is not a reason to start writing press releases instead of honest updates.
"Growth is the easiest time to get lazy about culture, because you're busy and everything feels urgent. That's exactly why we're paying so much attention to it right now. The version of ETAPX that people trust was built by a small team that argued in the open and finished what it started. A bigger PX Campus has to keep doing both, or it isn't really growth — it's just more people."
— Derek Amadi, Head of People at ETAPX
The Bay Area Roots Behind This Stage of Growth
ETAPX's decision to keep a real, physical headquarters in the Bay Area is a big part of why this growth stage looks the way it does. A remote-first company grows by adding more video calls. PX Campus grows by adding more people to the room where the collisions happen, and that changes the character of the growth entirely.
There's also a longer-term vision attached to the physical campus. AJ has been open that the headquarters shouldn't stay a private space that only employees ever walk into forever. The small meetups with members of Campus, our Discord community, are an early, deliberate step toward a headquarters that eventually hosts events and welcomes creators and community members in. Growth on PX Campus is part of what makes that possible: a bigger, more established team can eventually open its doors in a way a tiny, stretched team never could.
What This Means for the Community
If you use any ETAPX product, this stage of growth reaches you in ways that are easy to miss but meaningful over time. Here's what to expect as PX Campus continues to grow:
- More visible team members: As the team grows, more of the people building the products will show up in public — on the YouTube channel, in Campus on Discord, and in PX News coverage — so you'll see more of the faces behind the features.
- Steady, focused improvements: Expect a lot of refinement across existing products rather than a flood of unrelated launches. That's by design.
- Faster responses in Campus: The Discord community's feedback, beta, and early access channels become more useful the more people on the team are actively reading them.
- More behind-the-scenes content: A growing campus has more stories worth telling, and the team plans to keep sharing them through PX News and video.
Looking Ahead: The Next Chapter of PX Campus
Nobody on the team would describe this stage as finished. Growth at ETAPX has always been iterative: the company expands, figures out which habits survived the expansion and which ones need reinforcing, and adjusts before the next stage arrives. That pattern will continue. Some things that work today will need to change as more people join, and the team fully expects to learn a few lessons the hard way.
What won't change is the underlying standard. PX Campus is at its best when people are close to each other, close to the products, and close to the community using them. Every choice being made during this stage — how space is shared, how new people are welcomed, how decisions are documented, how teams are shaped — is aimed at keeping those three kinds of closeness intact while the campus gets bigger.
Frequently Asked Questions
What is PX Campus?
PX Campus is both ETAPX's physical headquarters in the Bay Area, where the team building Whistlr, GLSRM, Ocsidian, Influxx, and in.between works, and the company's shorthand for its culture — an open, direct, show-your-work way of building products. It's separate from Campus, ETAPX's official Discord server, though both share the same community-first spirit.
Why is PX Campus growing right now?
PX Campus is growing because ETAPX's products have grown. A wider lineup that now includes in.between and Nalani, a deeper Whistlr platform, and a larger, more international community all need more people to take proper care of them. ETAPX also prefers hiring ahead of need so teams aren't stretched thin before help arrives.
Is ETAPX announcing a specific headcount or new office?
No. This is a look at the company's current stage of growth and how it's being managed, not a headcount milestone or office announcement. ETAPX deliberately avoids publishing numbers about team size, preferring to focus on how growth shows up in the quality of its products.
How does ETAPX keep its culture as the team gets bigger?
By protecting small, specific habits: keeping shared spaces shared across products, giving new team members a view of the whole company, documenting decisions where anyone can read them, organizing teams into small focused pods, and keeping feedback candid but kind. The goal is to gain specialization without losing the unscheduled "collisions" that drive cross-product ideas.
How does PX Campus growth affect Whistlr and other ETAPX products?
A properly sized team means more time for polish, stronger safety and support, better reliability, and faster responses to community feedback. Users should expect steady, focused improvements across existing products rather than a rush of unrelated new launches.
How can I follow along with what's happening on PX Campus?
Join Campus, ETAPX's official Discord server, at discord.gg/etapx, subscribe to the ETAPX YouTube channel at youtube.com/@etapx-inc, and read PX News. Those are the places where the team shares behind-the-scenes updates, answers questions directly, and shows the people behind the products.
PX Campus has grown before, and each time it came out the other side able to build something it couldn't have built at its previous size. This stage is the same kind of moment — more people, more depth, and more responsibility — handled with the same stubborn attention to the habits that made the company worth growing in the first place. We're glad to be building it in the open, and we're glad you're here to watch it happen.
