CovertGift
Group gift planner. The person getting the gift can’t see a thing, and the server enforces it: every route answers them 403.
- Role
- Solo, from design to deployment
- Period
- Oct 2026 → ongoing
- Stack
- Go 1.27 · Gin · GORM · PostgreSQL 17 · React 19 · TypeScript · TanStack Query · Tailwind 4 · SSE · Gemini · Docker · nginx · Azure Container Apps

Problem
Group gifts get planned in WhatsApp groups. Links get lost, the budget stays vague, and worst of all, the surprise is easy to spoil.
Approach
01Anti-Spoiler lives on the server
The recipient gets a 403 on every route that touches the group and its ideas, invite link included. Integration tests against the real router and PostgreSQL guard the rules.
02Link previews for stubborn links
Trendyol's short link stopped on an Adjust tracking page instead of the product. I decode the redirect parameter and make a second request to the real page, with a JSON-LD fallback for the price. The server fetches URLs users hand it, so it has SSRF guards: a domain allowlist, private IP blocking, size and redirect limits.
03Live updates that don't leak
An SSE event carries no data, it only says “changed”. The client refetches from the routes that are already protected, so being live never bends the access rules.
04Cost-aware hosting
Azure Container Apps. I shut the environment down when it's idle and added a “server is waking up” screen for cold starts.


Outcome
Live · 123 commits · 40 Go test files · TR/EN · light and dark themes · mobile.