How I built a highly profitable web platform, but wrote zero backend code to keep my server costs at $0.
Every developer has a folder on their computer filled with abandoned side projects. You know the one—it's where ambitious ideas go to gather dust after the weekend is over. Four years ago, BeGoodTool was just another one of those folders. It didn’t start with a venture capital pitch, a business plan, or a dream to disrupt an industry. It started because I was incredibly frustrated. I was doing…
In the early 2021, a developer named [Name] found themselves overwhelmed by a folder on their computer filled with half-finished side projects. Inspired by a personal frustration with the modern web's reliance on forced sign-ups, hidden features, and sensitive data uploads, [Name] decided to build a platform that would run entirely in the browser, eliminating the need for backend processing.
The initial project, named BeGoodTool, started as a simple utility that performed JSON formatting and image conversion tasks. As colleagues requested additional features, the platform evolved into a collection of 70 diverse tools, supporting 18 languages. Despite the complexity, [Name] aimed to scale the platform without incurring significant server costs.
To achieve this, [Name] adopted an unconventional architectural philosophy called "Bring Your Own Compute." This meant that every tool on the platform would execute entirely within the user's browser using their local CPU and RAM. By doing so, [Name] eliminated concerns about server vulnerabilities, traffic-related database crashes, and hefty AWS compute bills.
To support this approach, [Name] leveraged free enterprise tiers from Azure Static Web Apps and Cloudflare. The core compiled files were hosted on Azure Static Web Apps, which offered a generous free tier for static assets. However, Azure Static Web Apps alone did not provide global distribution or bandwidth capabilities. To address this, [Name] used Cloudflare's Free Tier as a global edge CDN.
Cloudflare cached all static HTML, JS, and CSS assets across its worldwide network, handling DDoS protection, SSL, and absorbing a significant portion of the bandwidth.
The SEO challenge posed a unique obstacle, as pure Single Page Applications (SPAs) often struggled with search engine crawlers. To solve this, [Name] employed Static Site Generation (SSG) using Vite-SSG. During the build process, a headless browser environment was spun up to crawl the Vue Router configuration and generate pre-rendered HTML files for every page.
This approach allowed Cloudflare to serve pre-rendered HTML files directly from local edge nodes, depending on the user's location, greatly reducing Time-to-First-Byte (TTFB).
The implementation of SSG presented the "Hydration Nightmare." Browser-native APIs like window, document, and HTMLCanvasElement were not available during the build process. To overcome this, [Name] globally stubbed dangerous components during SSG and dynamically imported them only when the code reached the browser. This separation of "Build-time code" from "Browser-time code" ensured a smooth user experience while adhering to the zero backend processing rule.
By combining these architectural decisions and clever design patterns, [Name] managed to host a massively diverse platform with over 70 tools, supporting 18 languages, and generating a substantial passive income stream—all while keeping server costs at a minimal $0 monthly fee.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written; read the original for the full account.
