Developer Infrastructure.
Rent Nothing.

The clearest escape route from Firebase lock-in. You get a real Postgres database instead of a proprietary NoSQL store, plus auth, storage, and edge functions in one stack. Self-hosting is genuinely possible but not trivial — the compose file is heavy and you'll want a proper VPS. For most people the managed free tier is the better starting point.

Replaces UptimeRobot cleanly. Set up monitors for HTTP endpoints, TCP ports, or ping, and get alerts via nearly any channel you can think of. The dashboard is pleasant and the public status pages are genuinely nice. Runs fine on a small VPS, and it's worth having it somewhere other than your main server so it can alert you when the main server goes down.

The Git forge for people who don't want GitLab's resource footprint. Runs in a few hundred megabytes, the UI is fast, and everything you'd expect from a modern forge is there. The tradeoff is a smaller ecosystem of third-party integrations and slightly less polished enterprise features than GitLab.

Zapier and Make charge per task, which gets expensive fast once you have real workflows running. n8n self-hosted has no task limits. The node-based editor is powerful but has a real learning curve — expect to spend a weekend with it before it clicks. The library of pre-built nodes is huge and growing.

If you're doing any serious monitoring, you're probably using Grafana. The plugin ecosystem covers Prometheus, Loki, InfluxDB, and dozens of other data sources out of the box. Alerting is flexible and works well. Setup takes some planning if you're not already familiar with the metrics stack it usually runs alongside.

Where Baserow wants to be your database, NocoDB connects to the one you already have. Useful if you've got a legacy database and want to give non-technical people a way to view and edit records. The interface is polished and views are flexible. Best when you already have data — less compelling as a starting point.

Lots of self-hosted apps expect an S3-compatible backend for storing files, and MinIO is the standard answer. Setup is straightforward and the S3 API is well-implemented. The tradeoff is that serious deployments need proper erasure-coded disk layouts to be durable — treat it like real infrastructure, not a casual storage layer.

The idea is that someone on your team can ask questions of the company database without writing SQL. It works for that — dashboards are quick to build and the visual query editor handles most common cases. Self-hosting is easy and the free tier is generous. Setup on a real dataset requires some patience with permissions.

The open-source Calendly. Booking pages are customizable, the API is well-documented, and you can embed the booking widget anywhere. Self-hosting requires a Postgres database and some configuration, but the managed cloud free tier is generous enough to try it first.

Like Plausible but with a slightly different design philosophy — simpler, more minimal, easier to read at a glance. Self-hosting is a single Node process with a Postgres database. You get the numbers that matter (visits, referrers, top pages) without the complexity of full web analytics.

Not essential if you're comfortable with the docker CLI, but genuinely nice once your stack grows past a few containers. The UI shows logs, environment variables, and volume mounts in a way that beats scrolling through docker inspect output. Free tier is fine for personal use.

The point of Directus is that it doesn't impose a schema on you — point it at your existing database and it generates a full admin UI and API. Great for teams who want to skip building a CMS from scratch. The tradeoff is that some features are locked behind a paid license for commercial use.

Pulls conversations from your website chat widget, email, WhatsApp, and social media into a single inbox. Intercom and Zendesk charge serious money for this — Chatwoot self-hosted charges nothing. Setup is heavier (Ruby on Rails app with background workers) but the result is a professional support stack.

Keycloak is what enterprises use when they need real identity management. More capable than Authelia but correspondingly more complex — the admin UI is dense and the concepts take time to learn. For a homelab it's usually overkill. For anything with multiple user types and permissions, it's the right tool.

Does one thing well: tells you which pages people visit, where they came from, and what device they used. No cookies, no cross-site tracking, no consent banner needed in most jurisdictions. The tradeoff is you give up the deep user-journey analytics Google Analytics provides — if you need funnels, look elsewhere.

Node-RED predates most of the no-code automation tools and is more flexible than any of them. Popular in home automation circles — if you use Home Assistant or have ESP32 sensors, Node-RED is often the glue. The flow metaphor works well for event-driven tasks and less well for anything requiring complex state.

Mailchimp and ConvertKit charge by subscriber count, which adds up fast. Listmonk has no such limits — it's just a Go binary with a Postgres database. Campaign editing is straightforward and analytics are adequate. You need to bring your own SMTP provider, which is where the actual cost lives.

Forgejo exists because the Gitea project was commercialized. Functionally it's near-identical to Gitea today, so the choice is mostly philosophical. If you care about project governance and federation is on the roadmap, Forgejo is the safer long-term bet. Migration between the two is straightforward.