Boringstack achieves $5.96/month production cost for two apps

This review examines boringstack's ultra-lean architecture, leveraging systemd, SQLite, and Caddy on Hetzner to run two production applications for minimal monthly cost.

The Answer Up Front

For indie founders and bootstrapped projects where extreme cost efficiency and operational control are paramount, the boringstack approach offers a compelling blueprint. This architecture, detailed by boringstack, demonstrates how to run two production applications for under $6 per month using a minimalist, self-hosted setup. Developers needing enterprise-grade scalability, fully managed services, or extensive built-in observability should look elsewhere. The core takeaway is that significant cost savings are achievable by deliberately choosing simple, robust components over complex, platform-as-a-service offerings.

Methodology

This v0 review draws on the founder's published claims and architectural details provided in a Reddit post and a linked blog article. The source signal, authored by boringstack, details the actual monthly cost of running two production applications: borela.dev (a babysitter service for SQLite-on-VPS apps) and api.boringstack.org (a newsletter backend). This review covers the specific tool choices, their reported costs, and the architectural philosophy underpinning the cost efficiency. Independent benchmarks for performance, long-term workflow implications, or edge case handling are not covered in this initial assessment. Update cadence: re-tested when claims diverge from observed behavior.

• Tool name + version + date observed: boringstack architecture (Hetzner CX22, Cloudflare R2, systemd, SQLite, Caddy), as detailed on 2026-05-30.
• Source signal URL: https://www.reddit.com/r/selfhosted/comments/1tsfuy5/our_twoapp_production_stack_runs_on_596month/
• What's covered in this review: The founder's claims regarding monthly costs, the specific cloud and software components used, and the architectural principles enabling co-tenancy and cost reduction. The review incorporates details from the linked full writeup at https://boringstack.org/issues/2026-05-30-the-cloud-bill-is-an-architecture-review.html.
• What's NOT covered: Independent performance benchmarks under load, the operational overhead of manual backup and deployment scripts, long-term maintenance costs, or detailed security audits.

What It Does

The boringstack architecture is a highly optimized, self-hosted production environment designed for minimal operational expenditure. It leverages a combination of infrastructure-as-a-service and open-source software to achieve its cost targets.

Core Infrastructure Choices

At its foundation, the stack utilizes a Hetzner CX22 virtual private server (VPS) as the primary compute resource, costing $4.59 per month. For object storage, Cloudflare R2 is employed at a reported cost of $0.12 per month. Domain Name System (DNS) services for boringstack.org add $1.25 to the monthly bill. Email delivery is handled by Resend's free tier, incurring no additional cost. This selection prioritizes providers known for competitive pricing and reliable basic services.

Process-Oriented Application Hosting

Central to the boringstack philosophy is the principle of running applications as processes rather than relying on managed platforms. Both borela.dev and api.boringstack.org operate as systemd units, each configured with different users, dedicated SQLite files for data persistence, and distinct network ports. This approach enables efficient co-tenancy on the single Hetzner VPS, allowing the second application to be added with zero additional infrastructure cost. Caddy serves as the front-end web server and reverse proxy, managing virtual hosts and automatic TLS for both applications.

Deliberate Omission of Managed Services

The architecture explicitly avoids common cloud-native services that typically add significant cost and complexity. The founder reports that components like Redis, dedicated message queues, and advanced observability platforms are not on the bill. Similarly, continuous integration (CI) is handled outside of paid services. This lean approach reduces both direct monetary costs and the cognitive load associated with managing a distributed, service-heavy environment.

What's Interesting / What's Not

The most interesting aspect of the boringstack is its explicit, verifiable demonstration of extreme cost efficiency. Running two production applications for $5.96/month is a direct challenge to the prevailing narrative of escalating cloud bills. The founder's detailed breakdown of the bill, line by line, provides transparency often missing in discussions about cloud economics. The

The investor read

The boringstack approach signals a growing segment of the developer market that is highly sensitive to cloud costs and willing to trade managed services for direct control and lower expenditure. This challenges the 'everything-as-a-service' model, suggesting that for many small-to-medium scale applications, the value proposition of hyper-scale cloud providers is diminishing relative to simpler, self-hosted alternatives. While boringstack itself is an architectural philosophy rather than a product, it highlights a potential market for specialized tooling or consulting services that enable similar cost-efficient, 'boring tech' stacks. Companies offering robust, single-binary tools, or highly efficient infrastructure components that integrate well with systemd and Caddy, could find a receptive audience. This is likely a deliberate small/bootstrapped play, demonstrating a viable path for indie developers to achieve profitability without venture-scale cloud spend.