Get the weekly radar
One short email with the freshest products, every week.
Midway drops real-time member chat into a Memberstack Webflow site with one iframe embed.
Grounded in available product and source data
No backend, no database, no separate login system — that's the pitch behind Midway as real-time chat for Memberstack Webflow sites, built to drop straight into a site that already runs on Memberstack for membership and Webflow for the front end.
Messages, read state, and typing indicators update live without a page refresh, and voice notes record directly in the browser and attach to a conversation the same way a text message would. Beyond group chat, direct messaging lets members message each other one-to-one, gated by a request flow that requires approval before a new conversation starts — a deliberate friction point against unwanted messages. Threading, reactions, member blocking, and soft message deletion round out the feature set, with soft deletion specifically designed so a removed message doesn't break the reply chains or reactions still attached to it.
Authentication is where Midway's Memberstack-specific design shows most clearly: the site states it reads a site's member list and honours every member-level access object already configured, so there's no second login system for members to deal with — they chat with the account they already have. Getting it running is a single iframe embed pasted into Webflow or any HTML-accepting page, with members able to start chatting the moment the page loads and no backend deployment required on the site owner's end.
Two tiers separate by project count and storage: Free covers one project with 5 GB of storage, while Studio supports multiple projects at 50 GB each. One practical detail worth knowing upfront — voice notes and uploaded files auto-delete after 90 days, though the text message history around them stays intact, so anyone needing longer-term file retention should plan around that window rather than assume uploads persist indefinitely.
No — Midway reads a site's existing Memberstack member list and access permissions directly, so members chat using the account they already have rather than creating a new login.
Very little, by design — it's meant to be a copy-paste job rather than a development project, since the whole setup is one embed rather than a server to provision or a database schema to design.
Not without approval — direct messaging includes a request flow, so a new one-to-one conversation only starts once the recipient accepts it, rather than opening automatically.
They auto-delete after 90 days, per the site, though the surrounding text message history stays intact — worth planning around if a community needs longer-term access to shared files.
Only Memberstack-powered Webflow sites — the authentication model depends specifically on Memberstack's member list and access objects, so it isn't a general-purpose chat widget for any site.
These 1 comments were collected from the discovery source. ProductVisit does not host replies in Release A.
Hey Product Hunt 👋 I built Midway because Memberstack + Webflow gives you a beautiful members area, and then the second you want your members to talk to each other inside it, you fall off a cliff. The usual answers are an external Slack or Discord (community lives somewhere else, branding gone), Circle (another login), or wiring up a chat API like TalkJS. Midway is one iframe embed. Paste it into Webflow, point it at your Memberstack project, and your members get DMs with voice notes, replies, reactions, typing indicators, read receipts, online presence, and chat-request gating so nobody gets spammed. There are other ways to put chat on a site (TalkJS, Stream, Memberchat in the Memberstack ecosystem). Midway's tradeoff is being built specifically around Memberstack auth and Webflow embedding, so the setup is minutes instead of days, and your site stays the home of the community instead of pointing people to a third-party app. Free plan to try, paid plans when you scale past a couple hundred MAU.