Use self-hosted Loki when you need to own the log store and its operating model; otherwise, reach for a hosted app log search API when a small business needs incident evidence without becoming a storage-and-indexing operator. For app logging, the useful comparison is not "which service has the lowest sticker price," but which system can preserve enough evidence to explain a bad payment, a duplicate callback, or a reconciliation mismatch after the fact.
I build ledger services, so a log line is rarely decoration to me. It is an audit fragment: request identity, actor, state transition, and enough surrounding context to prove why a write was accepted or refused.
What should a small business choose for self-hosted Loki, Elastic Cloud, and a hosted app log search API?
A small business choosing between self-hosted Loki, Elastic Cloud, and a hosted app log search API should start with the operational boundary. Loki is the right alternative when someone can own object storage, retention, upgrades, access control, and the query path; Grafana then gives that team a familiar exploration surface. Elastic Cloud is a strong choice when schema-rich search, governance, and a wider Elastic workflow justify a managed service. Both can be sensible, but neither makes the operational questions disappear.
