Self-hosted party invitation & RSVP tool with per-guest links
Problem
Someone hosting a birthday party wants to self-host their invitations instead of using ad-driven services like Evite, but no simple self-hosted option exists: they need dedicated per-guest links, RSVP tracking, and something guests can open without accounts or friction.
Opportunity
A lightweight, privacy-friendly self-hosted invitations app (Docker-deployable) generating unique per-guest links, collecting RSVPs plus dietary notes, and giving the host a live dashboard — filling a real gap in the self-hosted ecosystem between heavy event platforms and DIY forms.
Market analysis
The gap is narrower than it looks: gath.io already offers an open-source, self-hostable event planner with simple RSVP (deployable via Docker/Cloudron), and Hi.Events covers the heavier self-hosted ticketing end, while free hosted tools (Partiful, Luma, Invyt) absorb everyone who doesn't actually care about self-hosting. What remains unclaimed is the specific per-guest-link + dietary-notes party flow — a nice OSS project, but monetization is structurally near zero because the audience is exactly the people who self-host to avoid paying.
Market · Self-hosting enthusiasts in the r/selfhosted community; enthusiastic but tiny, and culturally opposed to SaaS fees.
Pricing · Expectation is FOSS/free (gath.io is free open source; hosted RSVP tools are free at casual scale); realistic revenue is optional donations or a hosted tier at a few dollars per event.
Pros
- + Clear, frequently recurring request pattern in the r/selfhosted community.
- + Small, well-scoped scope (links, RSVP, notes, dashboard) — a clean weekend-scale OSS build.
- + Per-guest unique links with dietary capture is genuinely missing from gath.io's simple RSVP flow.
Cons
- − gath.io already covers open-source self-hosted event RSVP.
- − Audience by definition avoids paying for software.
- − Free hosted tools (Partiful, Luma, Invyt) are good enough for most hosts.
Existing / similar tools
- → gath.io ↗
- → Hi.Events ↗
- → Partiful ↗
- → Invyt ↗
Source
r/selfhosted (Reddit)
Worth being honest about what this is: a portfolio project, not a business. The build itself is well-bounded — unique tokens per guest, a no-login RSVP page, a CSV export — and it would earn real goodwill (and GitHub stars) in the self-hosting community, which does have value as reputation. If revenue matters at all, the only viable shape is a hosted one-click version where the self-hosted option stays free: some fraction of party hosts want per-guest links without running Docker, and that fraction is larger than the r/selfhosted thread itself. Design for that from day one (multi-tenant from the start) or the hosted tier becomes a rewrite.