One-man SaaS, 9 Years In

On-call, downtime, and vacations

• Many note that incidents mostly happen during deployments or config changes; if nothing is changing, solo operators can usually relax.
• Several solo founders accept being effectively on call 24/7 with a laptop and connectivity, and avoid truly off-grid trips.
• Others argue occasional downtime is acceptable for non-critical services; third‑party outages can’t be fixed anyway.
• Some deliberately keep infrastructure simple and stable (few changes, no complex failover) to minimize incident frequency.
• A minority is uneasy about relying on a single hosting provider or being unreachable in low‑coverage situations.

Simplicity of one‑person SaaS

• Multiple commenters echo that “one‑man apps” are easier to maintain: single mental model, fewer misunderstandings, fewer bugs.
• Simple stacks (shared hosting, PHP/jQuery, bare metal with systemd/nginx, no containers/serverless) are seen as robust and low‑stress.
• Machines are treated more as “pets” than “cattle”; failover is often manual, but uptime in practice is high.

Pricing, enterprise customers, and moats

• Debate around enterprise pricing: some suggest raising prices aggressively and indexing to inflation; others say this conflicts with a “budget alternative” positioning.
• Comparison is made to larger monitoring tools; question whether capping top tier pricing leaves money on the table.
• Several argue a solo SaaS doesn’t need a strong moat or market dominance; a small, profitable slice is enough.
• Others counter that without a moat, competitors or larger players could eat into the business.

Self-hosted email

• Linked post on running a self-hosted transactional email stack prompts debate.
• Some insist email is complex and fragile; others say modern tools (e.g. integrated mail servers) plus proper IP reputation and DNS setup make it manageable.

Marketing, acquisition, and growth

• Customer acquisition comes largely from search, word of mouth, Reddit communities, and Hacker News; paid ads without analytics are described as “shooting in the dark.”
• Advice to aspiring founders: clear landing pages, free tiers, public docs, visible company info, and long‑term persistence through slow early MRR growth.

Lifestyle, burnout, and “hobbit software”

• Many find the “small, calm, content” SaaS ideal highly aspirational.
• Discussion around burnout: some see it as tied more to lack of agency and hated work than to total hours.
• Several solo founders emphasize boundaries, email‑only support, self‑service features, and accepting “enough” rather than chasing endless growth.