Stacks / Email
Flagship
Mailflare + Cal.com + synct + genoffice
The office stack: Cloudflare Workers email, open-source booking, calendar sync, and an AI office.
The problem
Google Workspace or Microsoft 365 plus Calendly is a seat tax for mail, calendar, and "pick a time." Dave is retiring M365 on c17.io and moving apex mail to Mailflare.
Replaces
Google Workspace / M365 + Calendly
Estimated SaaS saved
$1,800
per year, small team, before lock-in
Deploy on RailwayFlagship. Mailflare lives on Cloudflare Workers; Cal.com + synct are the Railway pieces. DNS cutover is a separate checklist.
The stack
Cost table
| You stop paying | Typical / year | Self-host instead |
|---|---|---|
| Google Workspace Business Starter (5) | $432 | Mailflare on Workers + your domain |
| Microsoft 365 Business | $720 | Same Mailflare cutover |
| Calendly Teams | $1,200 | Cal.com + synct |
Agent setup prompt
Build the flagship office stack that replaces Google Workspace / M365 + Calendly. Pieces: - Mailflare (https://github.com/hieunc229/mailflare) on Cloudflare Workers for apex email. Check whether Mailflare requires Cloudflare nameservers. - Cal.com for public booking. - synct (https://synct.utility.cx/honeststok/david) for calendar sync. - genoffice (https://github.com/genspark-ai/genoffice) for the AI office layer. DNS for c17.io (do not apply yet, document only): - Remove M365 MX / SPF / autodiscover / lync / sip / msoid / tenant TXT. - Add Mailflare MX / SPF / DKIM / DMARC. - Put Resend DKIM on send.c17.io. Write AGENT_PROMPT.md, a cost table, and a rollback plan if mail breaks.
Also as markdown: /stacks/mailflare-office.md
FAQ
- Is M365 still on c17.io?
- Yes, until DNS changes. Decision is made: Mailflare takes apex email. Nothing has been flipped yet.
- Will Resend collide with Mailflare?
- Not if Resend stays on send.c17.io. Don't put two MX stories on the apex.