
A running log of the real decisions behind ZyVOP — hosting migrations, stack choices, costs, and the mistakes that came with them. No polish, just what happened and what it cost.

7 articles • curriculum order
Vercel was the obvious choice when I launched ZyVOP — until edge function timeouts started silently killing cross-posts. I moved the entire platform to a $8/month VPS using Docker and Cloudflare Tunnel in under 2 hours. Here's the exact setup, what broke, and the Cloudflare cache gotcha nobody warns you about.
I used to publish everything on Dev.to. It worked, but I eventually realized I was building my content on someone else's platform. So I built ZyVOP—a developer publishing platform where I can keep the original article, distribute it to other platforms, and build the analytics and tools around it myself.
Most "cost of running my SaaS" posts hide the free tiers and skip the disasters. Here's every line item behind ZyVOP — including the Vercel timeout that was one slow API response away from silently killing cross-posts.
Cross-posting sounds simple until you try to build it. Every platform has different APIs, different formats, different quirks, and different failure modes. Here's the complete technical breakdown of how ZyVOP's syndication engine works under the hood.
Most developer platforms treat content syndication as a two-way street. It isn't. Every piece of content you cross-post has a canonical URL, and that URL determines which domain gets the SEO credit. Here's the strategy behind ZyVOP's approach — and the bug that almost broke it.
Invalid emails can destroy your sender reputation. We built an 8-step NestJS verification pipeline with regex, MX checks, disposable/role filters, SMTP probing, greylisting retries, catch-all detection, and 24-hour caching with auto cleanup. Here’s the architecture and key lessons.
built a cross-posting engine that publishes to 5 platforms with a single click. This post covers the adapter pattern architecture, HTML-to-Markdown conversion quirks, platform API inconsistencies (GraphQL, REST, AT Protocol), JSONB error persistence, retry mechanisms, and canonical URL strategy for SEO.