Who you are, what does your project do, and why did you build it?
I'm Magnaem Ambata and Midway is real-time member-to-member chat for Memberstack sites. Site owners paste one embed onto their site, and their members can message each other right there, as the Memberstack account they already have.
Members get direct messages, chat requests, replies, reactions, typing indicators, read receipts and online presence.
Site owners can add:
- voice notes and file sharing
- email alerts for unread messages
- chat that opens straight from a profile or listing page
- Confirm a deal, which keeps phone numbers and emails hidden until both members agree
- translations, so the inbox speaks the same language as the site
It works on Webflow and on any other site running Memberstack.
I'd used the chat tools that already exist, and I kept running into the same two problems. Some were missing features I needed, and others were priced for bigger teams, not for a solo founder or a bootstrapped business.
So I built the inbox I actually wanted on my own Webflow sites. That meant voice notes, reactions, a way for two members to confirm a deal before sharing contact details, and translations. Pricing starts with a free plan, because I built Midway for people like me.
What I love about Memberstack
Members already exist.The hardest part of embedding chat is knowing who is typing. Every site owner already has members in Memberstack, so Midway verifies the member's Memberstack session on the server and they chat as themselves. There's no second account, no profile to fill in twice, and nothing for the site owner to sync by hand.
The Admin API. Midway uses it to verify members, keep each project's member list in sync, and read custom fields. Those fields power names and avatars in the inbox, and they're how Confirm a deal shares a member's phone number or email once both people agree.
It works on any site. Memberstack isn't tied to one builder, so Midway isn't either. I built it with Webflow in mind, but anyone with Memberstack on their site can add Midway with the same embed.
It runs my own accounts too. Midway's dashboard uses Memberstack for signup, login, email verification, password reset and profile photos. I never had to build authentication for my own product.
The problem Memberstack solved
Midway needed authentication twice: once for site owners using the Midway dashboard, and once for every member chatting on those owners' sites.
For the dashboard, Memberstack gave me signup, login, email verification, password resets and account deletion out of the box. Without it, I would have had to build and secure all of that before writing a single line of chat.
For the product itself, Memberstack is the identity layer. Without it, every site owner would have to copy their members into a separate chat system and keep the two in sync, and every member would need a second login just to send a message. Instead, Midway checks the member's existing Memberstack session and knows exactly who they are. That's what makes it possible to install Midway with one embed instead of an engineering project.
