Replacing High-Cost SaaS with Owned Services
Replace bounded recurring services while retaining infrastructure with heavy operating burden
Definition
A service-replacement audit compares recurring vendor spend with the engineering and operating burden of owning a smaller substitute before choosing whether to build or keep buying each service.
Perspectives
@levelsio (2026-09-09, X)
@levelsio reports replacing fourteen paid services or labor categories with small owned services for approximately $25,000 per month in claimed savings. Examples include Sharp plus Redis for image resizing, NudeNET for NSFW detection, Nginx on a VPS for video streaming, OpenFreeMaps for maps, Kuma for uptime checks, Patchright for scraping, a Telegram bot instead of IFTTT and an AI support bot alongside Featurebase.
The largest claimed substitutions were human moderation with xAI at $10,000 per month, customer support with Featurebase plus an AI bot at $5,000, NSFW detection at $2,500 and image resizing at $1,500. Keep buying domain registration, email sending, object storage, backups, hosted servers and LLM access rather than becoming a registrar, operating email, maintaining home storage and servers or running a local GPU rig.
How to apply
- Fits a revenue-producing product with material recurring bills, stable requirements and enough operating capacity to own incidents and maintenance.
- Do not start with low-cost conveniences or infrastructure whose failure carries regulatory, deliverability, data-loss or hardware risk.
- Evaluate one bounded service at a time and include engineering time, monitoring, abuse handling, redundancy and migration risk in the break-even point.
- Use Deciding When to Leave Supabase for the capability gate and Staging a Supabase Database Migration when a replacement crosses data and attached-service boundaries.
- Move repetitive parts into code only after the behavior is stable, following Promoting Agent Workflows into Automation.
Limits
All savings are a founder's rounded self-report without invoices, engineering-time accounting, reliability data or a common comparison period. Several replacements are described as $0/mo despite requiring a VPS, existing infrastructure or maintenance. Product versions, licenses, traffic volumes, service quality and the exact boundary between custom code and third-party components were not provided.