If you want to understand what ESTAGE actually is and why I run my whole business on it, that post is worth reading first. But if you're already building on the platform and you've been heads-down in client work like I have, this one is for you. The stretch from July 15 through August 14, 2026 was not a normal week of small fixes. It was a genuinely large batch of real platform changes, and I don't want to just dump a changelog at you. What I'm going to do instead is walk through the highlights that actually matter if you're running a hub-centric business, then close with a tighter list of the smaller stuff that still deserves a mention.
Web Apps: ESTAGE Can Now Build Real Applications
This is the headliner, shipped August 14. Genesis can now build full web applications, not just landing sites. A Web app project gets its own dedicated dev server with server-side rendering, real npm packages, and API routes. That is a meaningful step up from a marketing page.
The way it handles compute is worth understanding. The dev machine sleeps when you're not actively working (you buy a package of hours rather than paying for always-on), and when you publish, the live site runs on its own dedicated machine you choose at publish time. Your traffic never shares compute with anyone else's project. Server size is set in Settings, then Server. One more practical detail: publishing doesn't block your work. The build runs in the background and you can keep editing.
Community Toolkit: Bring Your Existing Community Into a Genesis-Built Site
Also shipped August 14, and this one is directly relevant to anyone running a coaching or membership hub. You can now bring an existing Estage community into a site Genesis builds for you. That means the full stack: feed and posts, member profiles, courses with lessons and resources, challenges, a video library, live broadcasts with chat, stories, moderation queues, badges, and gamification. All of it.
The security piece is handled cleanly. Members sign in through a secure Estage login and their credentials never touch the site's own code. The AI restyles every community screen to match the brand, so you're not stuck with a generic look bolted onto a custom site. This is available on Web app projects.
The Community Toolkit requires a Web app project. It is not available on standard Website projects.
Go Live by Link: Join a Stage Without an Account
Shipped August 14. A visitor can now join a live stage straight from the site with just their name. No Estage account, no signup flow. For anyone running live workshops or Q&A sessions directly on their site, this removes the friction that used to make guests hesitate.
The host keeps full control: the lobby, mute, and remove functions all work exactly as before. Stage rooms hold up to 12 people on screen, which covers most small-group use cases. For larger audiences, the live-stream element is still the right tool.
Several Apps Inside One Project
Shipped August 1. This one changes how I think about project structure. A project is no longer just one site. You can keep a Website, a Web app, and a Mobile app side by side under the same project, switching between them from a switcher in the builder.
Each app is genuinely its own build: own chat history, own files, own live preview, own pages list, own server, own publishing. Changing one never bleeds into the others. What they share is the important part: the project's CRM connection, team members, domain, and cloud database. So you can build the marketing site, a customer portal, and a phone app once, on one set of data, without wiring three separate projects together by hand. This is available to accounts with mobile-builder access.
ESTAGE Genesis for Mac: The AI Reaches Your Desktop
Rolling out from August 12. This is a native desktop app for Mac that lets the AI reach your own computer, with your permission, only where you let it. The practical unlocks are: using photos straight from a Desktop folder or Photos library without manual uploading, exporting reports or generated files to a location you choose, having the AI capture your screen when something is broken instead of you screenshotting it yourself, and getting a notification when a long build or publish finishes.
The safety design matters here. Reading and writing are treated separately. Project files still go through Genesis and every validation check. Credential folders like ~/.ssh are refused outright. The app is signed and notarized by Apple, so there's no security warning on macOS. Signing in is one step, and if you're already signed into Genesis in the browser, it connects through that. It's currently rolling out to internal accounts, with wider availability coming shortly.
AI Chat Widget in One Toggle
Shipped July 24. Adding a floating AI chat to a site is now a single switch in Settings, then AI Assistant. You define what it's allowed to do in plain language. No code, no API keys, and visitors never see a configuration screen. For a hub site where I want to answer common questions without building a full support workflow, this is exactly the right level of simplicity.
A Third AI Engine and a Stronger Genius Tier
Shipped July 25. The Kimi engine is now open to every user as a third choice of builder brain, alongside the existing options. More choices at the base level is a welcome change for experimenting with different build styles.
The Genius tier now runs on Claude Opus 5, described as the strongest model available for the hardest builds. If you've been using Genius for complex multi-section builds, that's a direct upgrade without any action on your end.
Real Capabilities From the First Prompt
Also shipped July 25. When you describe a site, Genesis now recognizes what it should actually do and offers to provision those as real working modules before the first build. Accounts, a blog, an in-site AI assistant, lead capture. Instead of shipping placeholder buttons that look right but don't work, it asks upfront and wires the real thing in from the start. That is a different kind of build experience.
Frequently Asked Questions
Do I need a Web app project to use the Community Toolkit?
Yes. The Community Toolkit (feed, courses, challenges, live broadcasts, badges, and all the rest) is available on Web app projects only. It is not available on standard Website projects.
Is ESTAGE Genesis for Mac available to everyone yet?
Not yet. As of the August 12 rollout date, Genesis for Mac is going to internal accounts first. Wider availability is coming shortly, but no specific date has been given beyond that.
Does switching AI engines cost extra?
The Kimi engine is open to every user as a third choice at no extra tier requirement. The Genius tier, which now runs on Claude Opus 5, is a separate tier. Pricing details for tiers are in your account settings, not something I'm covering here.
What happens to my existing single-app project?
Existing projects continue as they are. The multi-app capability means you can now add a Web app or Mobile app alongside your existing Website inside the same project, if your account has the right access. Nothing about your current project changes unless you choose to add another app to it.
Can a visitor join my live stage without creating an Estage account?
Yes, that is exactly what the Go Live by Link update enables. They enter their name and join straight from the site. No account, no signup. The host still controls the lobby, muting, and removing participants. The room holds up to 12 people on screen.
Does the desktop Mac app have access to everything on my computer?
No. Access is granted by you, and only where you allow it. Reading and writing are treated as separate permissions. Credential folders like ~/.ssh are refused outright regardless of what you tell it. Project files still go through Genesis and every validation check, same as in the browser.
Also Shipped
These are the smaller changes from the same period. Each one is real and worth knowing about.
- Marketplace search: now searches inside descriptions, supports filtering by multiple categories at once, and sorting is back.
- Smarter error fixing in previews: known error patterns are fixed instantly before any AI turn is spent. When AI does step in, 'fixed' means the page actually renders, not just that the code compiled. Failures the AI can't fix (like a cold server) now say what's actually happening instead of offering an AI fix.
- Form redirects: can now open in a new tab while the current page stays put and still shows the confirmation message. Saving a form also updates its live wiring immediately.
- Dashboard project cards: now show the actual address a project lives at, an honest live/unpublished state, and publish dates from the actual publish (not the last edit). You can search by name, domain, or ID.
- Nine new connectors: Slack, Discord, Shopify, Airtable, Google Reviews, Spotify, YouTube, Cal.com, and Trustpilot (Trustpilot ships as a widget since the provider walls off direct access). Each is wired correctly for its own API, with official brand logos.
- Media library: now accepts files up to 12 MB, shows the size limit for every file type up front, and gives a plain message instead of raw error text when something is too big.
- Account settings: now open in a panel over whatever you're doing, same as project settings. Billing, allocation, and credits live together in one Allocation & Credits tab.
- Module subdomains: modules can now live on their own subdomain (like app.yourdomain.com or store.yourdomain.com), each with its own home page, and the AI keeps its edits scoped to the right module.
- Cross-project style matching: the AI can now read another project on the same account and match its style. Saying 'use the same style as my main site' now works without exporting anything.
- Projects dashboard redesign: full redesign, and creating a project now starts from a 'What are you building?' chooser (Website or Mobile app).
- Mobile projects: can now use the device camera, the photo picker, video playback, SVG graphics, and embedded web views.
- SEO and crawlability: published sites now serve a crawlable favicon, search engines get fully pre-rendered pages on the custom domain, and the genesis.estage.com mirror no longer competes with the custom domain in search results.
- Legacy project re-binding: if a legacy project was imported with the wrong Estage project ID, it can now be re-bound to the correct one without a full rebuild. Files, chat history, settings, theme, and hardcoded ID references all move. A few things (configured payment elements and connected domains) need re-attaching after.
This post is part of the same update series as last week's post on the new reCAPTCHA protection, and there are more posts coming in this initial catch-up run. What I keep coming back to is this: when you build a business on top of a platform, the platform's investment pace matters as much as the features you're using today. A steady drumbeat of real, substantive changes (not just UI polish) tells you something about where the platform is headed. The July-August batch covered here is the kind of update that changes what's actually possible, not just what's slightly easier. That's worth paying attention to.