Company · September 22, 2026 · 17 min read

PX Team: Building in Public, Daily Streams Coming Soon

The PX team is building in public with daily streams coming soon. See what we'll stream, where to watch on YouTube, Whistlr, and Campus, and what always stays off camera.

PX Team: Building in Public, Daily Streams Coming Soon
PX Team: Building in Public, Daily Streams Coming Soon
The PX team is building in public with daily streams coming soon. See what we'll stream, where to watch on YouTube, Whistlr, and Campus, and what always stays off camera.

The PX team is about to start building in public in the most literal way we know how: daily streams, coming soon, showing the actual work of making Whistlr, GLSRM, Ocsidian, Influxx, and in.between as it happens. Not a polished highlight reel, not a launch-day keynote, but the real, sometimes messy middle — engineers working through a bug, designers debating a layout, the team talking through a decision before it's final. ETAPX has spent a long time arguing that visibility is worth more than polish. Daily streaming is the next step in actually living that out. Here's what building in public means to us, what the streams will look like, where you'll be able to watch, and how you can be part of it.

What Building in Public Means for the PX Team

"Building in public" gets used a lot in the startup world, often to mean little more than posting a revenue screenshot or a teaser of a feature that's almost done. For the PX team, it means something more specific and more demanding: letting people see how the work actually happens, not just what comes out the other end. That includes the reasoning behind decisions, the tradeoffs we weigh, the ideas that don't survive, and the ordinary, unglamorous hours of making software good.

ETAPX didn't arrive at this idea suddenly. It's the natural continuation of choices the company has already made. We run our own newsroom in PX News. We post product walkthroughs and founder updates on YouTube. We answer questions directly in Campus, our official Discord server, instead of routing everything through a ticket queue. AJ, ETAPX's founder and CEO, has written openly about why he believes a company that shows its actual thinking will out-earn one that only ever shows a highlight reel. Daily streams take that same bet and extend it into real time.

The difference is the format. An article describes a decision after it's been made. A video walkthrough shows a feature once it's finished. A live stream lets you watch the decision being made, and sometimes lets you weigh in before it's final. That's a much closer relationship between the people building a product and the people using it, and it's exactly the kind of relationship ETAPX has been trying to build from the beginning.

"We've been saying for a long time that we'd rather be findable than filtered. Streaming the work is the most honest version of that. If people trust what we make, they should get to see how it gets made — the arguments, the dead ends, the late-night fixes — not just the version we cleaned up for an announcement. I'd rather someone watch us figure something out than read a press release that pretends we never had to."

— AJ, Founder & CEO, ETAPX

Why Daily Streaming, and Why Now

There are a few reasons the timing feels right, and they all come back to where the company is today.

  • The team is growing: PX Campus is going through another stage of growth, which means more people, more specialists, and more work happening across more products at once. That's more worth showing, and it's also a moment where making our process visible keeps us honest with ourselves.
  • The products have gotten deeper: Whistlr now spans Circuits and SubCircuits, Waves, Minis, WTC Gems, Creator Studio, Flow live streaming, Storefronts, Live Shopping, Halo, and more. Influxx has native apps, ADE, and Podz. in.between and Nalani introduced a new kind of AI companion. The more a product can do, the more valuable it is to see how the people behind it think.
  • Video has proven itself: The ETAPX YouTube channel moved past its trial stage because walkthroughs and behind-the-scenes explanations genuinely helped people understand what we build. Live streaming is the next logical format.
  • The community asked for more access: People in Campus regularly ask how a feature was built, why a design changed, or what the team is working on right now. Streams answer those questions directly, at the source.

Why daily rather than occasional? Because building in public only works if it's consistent. A stream once a quarter is an event. A daily presence is a relationship. We want people to be able to drop in on an ordinary Tuesday and see what an ordinary Tuesday at ETAPX looks like, not just the big moments we'd naturally be tempted to schedule around.

What You'll See on the PX Team Streams

The streams are designed to show the real range of work that goes into the products, not just the parts that look impressive on camera. Here's the kind of content the team is planning as daily streaming rolls out:

  • Live build sessions: Engineers working through real features, fixes, and performance improvements, explaining their thinking as they go — the kind of problem-solving that usually happens silently behind a closed laptop.
  • Design reviews and critiques: Designers walking through layouts, interactions, and visual decisions, including the options that don't make the cut and why.
  • Product decision walkthroughs: Product leads explaining how the team weighs tradeoffs — what feedback came in, what the underlying need seems to be, and how a feature might be shaped to meet it.
  • Bug triage and polish passes: The unglamorous but essential work of finding rough edges and smoothing them out. Some of the most useful streams may be the ones where nothing new launches at all.
  • Community Q&A: Segments where the team answers questions from viewers and from Campus, our Discord community, in real time.
  • Cross-product conversations: Moments where people from different teams — Whistlr, GLSRM, Ocsidian, Influxx, in.between — compare notes, the same kind of hallway collisions that make PX Campus work, just with a camera on.

Not every stream will cover all of these, and not every day will look the same. Some sessions will be long, focused working blocks. Others will be shorter conversations. The goal is variety that reflects the real shape of the work rather than a rigid show format.

Where to Watch the Daily Streams

The streams will live on the channels ETAPX already uses to talk with the community, so you won't need to learn a new destination to follow along.

YouTube

The ETAPX YouTube channel at youtube.com/@etapx-inc is the natural home for long-form video from the team. Subscribing there is the easiest way to catch streams and, where it makes sense, watch highlights or recordings afterward.

Whistlr

Whistlr is where so much of the ETAPX community already spends its time, and Flow is Whistlr's own live streaming experience. It makes sense for the team to show up where creators and users are already going live every day. Following ETAPX on Whistlr keeps the streams close to the product they're about.

Campus on Discord

Campus, ETAPX's official Discord server at discord.gg/etapx, is where the conversation around the streams will happen. It's the best place to ask follow-up questions, share feedback on what you saw, and get notified when the team goes live. Campus already has dedicated channels for feedback and for beta and early access, which makes it a natural companion to watching the work happen.

Exact schedules and the specific mix of platforms will be shared as the streams roll out. We'd rather announce details once they're real than promise a timetable before the first stream airs, so keep an eye on Campus, PX News, and the YouTube channel for updates.

How to Follow Along: A Step-by-Step Guide

If you want to be ready when the daily streams start, here's the simplest way to set yourself up.

Step 1: Subscribe on YouTube

Head to youtube.com/@etapx-inc and subscribe. Turning on notifications means you'll know when the team goes live rather than finding out after the fact.

Step 2: Follow ETAPX on Whistlr

If you're already on Whistlr, make sure you're following the official ETAPX presence so streams and updates show up alongside the rest of what you watch.

Step 3: Join Campus

Join Campus at discord.gg/etapx. That's where stream announcements, discussion threads, and follow-up questions will live, and it's where the team is most reachable in real time.

Step 4: Bring your questions

The streams are more useful when viewers participate. If there's a feature you want explained, a decision you want the reasoning behind, or a bug you've been hitting, bring it. Some of the best segments will come from questions the team didn't anticipate.

Step 5: Keep reading PX News

Streams show the work in motion. PX News captures the decisions and outcomes in a permanent written record you can link to and reread. The two are designed to complement each other.

What a Typical Stream Might Look Like

It helps to picture an ordinary session. Imagine the Whistlr team has been hearing in Campus that a particular screen feels cluttered. A stream might open with a designer pulling up that feedback, explaining what people have said, and sketching the underlying problem out loud — not "move this button," but "people can't find what they need quickly enough." From there, the designer might walk through two or three alternative layouts, talk through the tradeoffs of each, and invite viewers to say which one matches how they actually use the app.

Later in the week, a different stream might pick up the same thread from the engineering side: an engineer implementing the chosen direction, running into an edge case on a smaller screen, and working through it live. Viewers see the decision go from a complaint in Discord to a design sketch to working code. When the change eventually ships, the PX News write-up and any YouTube walkthrough will feel familiar, because a lot of people will have watched it being made.

Not every stream will follow a tidy arc like that. Some days will be an hour of focused debugging with occasional commentary. Some will be a relaxed conversation about why a product is shaped the way it is. That's fine. The value isn't in every stream being a finished story; it's in the steady, honest view of how the work really moves.

What We Won't Stream, and Why

Building in public doesn't mean streaming everything, and it's important to be upfront about where the lines are. Being open about our process only works if it never comes at the expense of the people using our products.

  • User data and private content: Nothing that exposes a user's private information, messages, journal entries, or account details will ever be shown. in.between entries are private by default, and that doesn't change because a camera is rolling. The same goes for private content on Whistlr.
  • Security-sensitive work: Security at scale is a round-the-clock responsibility at ETAPX. Some infrastructure and security work simply can't be shown publicly without creating risk, so it stays off stream.
  • Trust and safety specifics: Moderation cases and the details of how specific reports are handled involve real people and real situations. The team can talk about principles and approach, but not individual cases.
  • Partners' confidential information: When ETAPX works with creators, artists, and businesses, their plans are theirs to share. We won't reveal a partner's work before they're ready.
  • Team members who'd rather not be on camera: Streaming is an invitation, not a requirement. Plenty of great work at ETAPX happens off camera, and nobody's contribution is measured by how often they appear on stream.

These boundaries aren't a contradiction of building in public. They're what make it sustainable. Visibility that puts users or team members at risk isn't transparency; it's carelessness. The PX team wants to be as open as possible about process while staying protective of people.

"There's a real engineering discipline to streaming your work responsibly. You have to know which screens are safe to share, which environments hold nothing sensitive, and where the line is between explaining how a system works and exposing something that should stay protected. We're setting that up carefully before we go live daily, because the whole point of building in public is trust — and trust is the one thing you can't afford to leak."

— John Ridge, CTO, ETAPX

Why Building in Public Makes the Products Better

It would be easy to treat daily streaming as a marketing exercise. That's not how the team thinks about it. Building in public has direct, practical benefits for the quality of what ETAPX ships.

Faster feedback loops

When people can watch a feature take shape, they can say "that's not how I'd use it" before the feature ships instead of after. That's the same principle behind Campus's feedback and beta channels, compressed even further. Catching a misunderstanding during a design review is much cheaper than fixing it in an update.

Better explanations

Explaining your reasoning out loud to an audience forces clarity. If a decision is hard to justify on stream, that's often a sign it deserves another look. Building in public makes the team better at articulating why things are the way they are, which makes the products themselves more coherent.

Real accountability

A company that shows its work is easier to hold to its word. If the team says a polish pass is happening, you'll be able to see it happen. That kind of visible follow-through is how trust compounds over time.

Shared understanding across the lineup

Streams aren't just for the community. They also let people inside ETAPX see what other teams are working on. An Ocsidian engineer watching a Whistlr stream might spot a solution to their own problem, extending the cross-product collisions that make PX Campus work beyond the walls of the building.

"I've been in Campus for a while and the best part has always been that you can actually talk to the people making the app. Being able to watch them work on something live is the next level. I want to see the stuff that doesn't make the changelog — the 'why' behind the changes, the bits they tried and threw away. That's what makes me trust a product."

— Marcus, longtime Whistlr creator and Campus member

Building in Public for Creators, Developers, and Founders

The daily streams are for everyone who uses ETAPX products, but a few groups in particular may find them especially useful.

  • Whistlr creators: Creators rely on tools like Creator Studio, Flow, Minis, Storefronts, and Live Shopping to build audiences and income. Watching how those tools are designed and improved can help creators understand what's coming and give feedback that directly shapes it.
  • Developers and builders: People interested in agentic tools like Influxx, ADE, and Ocsidian's approach to game creation can see how the team thinks about building with AI, and how ETAPX encourages working alongside AI rather than treating it as a replacement for skill.
  • Startup founders: AJ has openly encouraged other startups to choose visibility too. The streams are a working example of what that looks like in practice — the benefits, the boundaries, and the day-to-day reality.
  • Students and people curious about tech careers: Seeing how a product team actually works — how engineers debug, how designers critique, how decisions get made — is some of the most useful context someone can get when figuring out where they want to go.
  • Everyday users: If you've ever wondered why an app you use changed, the streams are a chance to hear the answer from the people who made the call.

How Streams Fit With PX News, YouTube, and Campus

ETAPX now has several ways to share what it's building, and each one does a different job. Understanding how they fit together makes it easier to know where to look for what you want.

  • PX News: The written record. Deep explanations, announcements, and honest updates — including the parts that took longer than planned — that you can quote, link, and reread.
  • YouTube: Finished video. Product walkthroughs, founder updates, and behind-the-scenes explanations that are easier to show than to write.
  • Daily streams: Work in motion. The live, unedited process of building, with room for viewers to participate as it happens.
  • Campus on Discord: The conversation. Real-time discussion, direct questions, feedback, and beta access, connecting everything else together.

None of these replace each other. A decision you watch take shape on a stream might later be explained in a PX News article and demonstrated in a YouTube walkthrough, with the discussion happening in Campus the whole way through. That's what a genuinely open company looks like when all its channels work together.

"The streams are going to make Campus even more valuable. When someone watches the team work through a problem and then jumps into Discord to ask about it, the distance between having a thought and being heard by the person who can act on it gets really, really small. That's what we built Campus for in the first place."

— Priya Okonkwo-Hale, Head of Community at ETAPX

What Comes Next

Daily streaming is coming soon, and the team is preparing for it the same way it prepares for any launch: carefully, with attention to the details that make it work well over the long run. That means setting up safe streaming environments, figuring out a rhythm that the team can genuinely sustain, and making sure the content stays useful rather than repetitive.

We expect the format to evolve. The first streams will teach us what people find most valuable, what they skip, and what they want more of. Some segments will become regular fixtures. Others will fade. That iteration is part of building in public too — the streams themselves will be built with the community watching and weighing in.

What won't change is the underlying commitment. ETAPX believes the companies that earn lasting trust are the ones willing to show their actual thinking. Streaming the work every day is a very direct way of putting that belief on the line.

Frequently Asked Questions

What does "building in public" mean at ETAPX?

Building in public at ETAPX means showing how the PX team actually builds its products — the reasoning, tradeoffs, design debates, and everyday work — not just the finished features. It continues what ETAPX already does through PX News, its YouTube channel, and Campus, its Discord server, and extends it into daily live streams.

When will the PX team's daily streams start?

Daily streams are coming soon. ETAPX is setting up safe streaming environments and a sustainable schedule before going live, and will share specific timing through Campus on Discord, the ETAPX YouTube channel, and PX News once the details are final.

Where can I watch the ETAPX daily streams?

The streams will live on channels ETAPX already uses, including the YouTube channel at youtube.com/@etapx-inc and ETAPX's presence on Whistlr, with discussion and announcements in Campus at discord.gg/etapx. Exact platform details will be confirmed as streaming rolls out.

What will the PX team stream?

Expect live build sessions, design reviews, product decision walkthroughs, bug triage and polish passes, community Q&A, and cross-product conversations between teams working on Whistlr, GLSRM, Ocsidian, Influxx, and in.between.

Will my data or private content ever appear on stream?

No. ETAPX will never stream user data, private messages, in.between journal entries, account details, security-sensitive systems, individual moderation cases, or partners' confidential plans. Building in public is about sharing process, never about exposing people.

Can I ask questions or give feedback during the streams?

Yes. Community participation is a core part of the plan. Bring your questions to the live Q&A segments and to Campus on Discord, where the team will follow up on what viewers ask and share feedback channels for features shown on stream.

The PX team has always believed that the best way to earn trust is to let people see the work. Daily streams are coming soon, and when they arrive, you'll be able to watch Whistlr, GLSRM, Ocsidian, Influxx, and in.between get built one ordinary day at a time. Subscribe, join Campus, bring your questions — and come build with us.