Why Your Website Bill Should Not Depend on How Often It Is Used. How Usage-Billed Cloud Platforms Compare to Flat-Rate Application Hosting—And Why Your Business Deserves One Predictable Monthly Number.

2. Inside the Four Meters: Deploys, Database Hours, Bandwidth, and Per-Project Fees

To see why a typical small business application can generate variable bills on metered platforms, you do not need to guess—leading cloud providers publish their exact credit and hourly rates clearly in their documentation. Consider what happens to a standard business website across four common meters:

• 1. Production Deploys: On credit-based platforms like Netlify, every production deploy consumes 15 credits (Netlify Docs — How Credits Work), and extra credit packs on the Pro plan cost $10 per 1,500 credits (Netlify Docs — Buy Credit Packs). While local testing catches most issues before launch, the final checks that confirm a site works properly—forms saving to the live database, page redirects, caching headers, and checking a layout on a real phone—only happen in production. On a metered plan, every live verification pass ticks the deploy counter.

• 2. Database Compute Hours (Sleeping vs. Non-Pausing Clocks): Modern cloud databases generally bill in one of two ways. On a serverless credit meter like Netlify’s built-in database, compute is billed at 10 credits per GB-hour (Netlify Docs). Serverless databases are designed to sleep when nobody visits, but a live business website with contact forms, regular visitors, and automated uptime checks rarely stays asleep for long. Conversely, on a dedicated per-project database platform like Supabase Pro, databases never pause (Supabase Pricing)—each project runs its own database server billed for every hour it exists, with any partial hour counting as a full hour (Supabase Docs — Manage Compute Usage). Their smallest Micro instance is $0.01344 per hour (about $10/month per project), and while the $25 Pro base plan includes $10 in compute credit—enough to cover one Micro database—each additional project adds another hourly clock (Supabase Docs — Billing FAQ).

• 3. Bandwidth, Requests, and Rate Adjustments: Metered platforms also count database bandwidth (20 credits per GB on Netlify) and web bandwidth (20 credits per GB), plus serverless function compute (Netlify Docs). In addition, platforms periodically adjust credit multipliers over time—for example, Netlify updated its compute and bandwidth credit rates on April 14, 2026 (AgentDeals — Netlify Pricing Update)—meaning the cost math you calculate in January can shift later in the year.

4. What Runs Behind Our Flat-Rate Cloud— And the Engineering Work We Handle for You

Moving off a usage meter does not mean cutting corners on infrastructure—it means our team takes direct responsibility for the server operations so you get a fixed monthly cost. In plain terms, here is what sits behind your site when you host with GreenTree:

• 1. Standard Open-Source Platform, Kept Current: We run our own private deployment and container platform built on standard open-source deployment software on dedicated Linux hardware rather than a modified custom fork. Staying on the official upstream release matters because when upstream security updates ship, we apply them promptly—typically the same day—while keeping administrative control panels locked behind restricted access.

• 2. Automated Backups and Outside Monitoring: Every client database is backed up automatically every day, and our external monitoring tools (LogBot.app and DNSBot.app) check your website and form endpoints from outside the server every 60 seconds under our 99.982% uptime service standard (as defined in our Master Terms of Service).

• 3. Second Server Redundancy Planned on Our Roadmap: We also believe in being straightforward about what is live today versus what is next. While large managed clouds spread workloads across multiple machines automatically, a single dedicated server requires disciplined backups and a tested rebuild plan. Adding a second server as a high-availability pair—two machines that can cover for each other automatically—is planned next on our infrastructure roadmap as we continue expanding our fleet. (Curious whether you should build and run a stack like this yourself? Read our companion guide: Should You Run Your Own Server Stack? What Self-Hosting Actually Asks of You.)

5. A Respectful Note for Long-Time Hosting Customers Deciding When to Modernize

GreenTree hosts more than 250 websites, and many of our customers have been with us for ten, fifteen, or twenty+ years—some dating all the way back to hosting companies we helped lead before launching GreenTree in 2007. A share of those long-time customers are still on legacy shared hosting plans paying a fraction of what a modern application plan costs.

To a software company, $99 a month sounds small. To a small business owner or an individual who has kept a website online for fifteen years, stepping up from a legacy hosting bill is a real financial decision. We respect that completely, and we never pressure a long-time customer to upgrade before their business needs it.

When you are ready to replace an aging website with a fast, modern platform that reflects what your business does today—beginning with our Small Business Website Modernization ($999 for a 5–6 page done-for-you build)—the least we owe you is a monthly number that will not change on you. You will never get a surprise invoice because we pushed extra updates to get your contact form right or because your database stayed awake all month.

To see how we price project builds and ongoing care in plain terms, read Why We Charge $350/hr — And Why We Bill Projects as a Flat Fee and explore our Ongoing Engineering & Content Retainers. (And if you enjoy behind-the-scenes founder essays, you can also read Gene’s personal perspective on Substack: The Drip Economy & Cognitive Rent.)