XupaStack provides free self-hosted and managed gateway options to keep your Supabase-powered apps working when supabase.co is blocked by ISPs like Jio, Airtel, BSNL in India. It gives you a gateway URL with full support for REST, Auth, Storage, Functions, GraphQL, and Realtime (WebSockets). Choose your trust model: Self-hosted (recommended): deploy into your own Cloudflare account (privacy-first). Managed (fastest): instant gateway URL (different trust model; best for emergencies).

Anima - OnBrand Vibe Coding — Design-aware AI for modern product teams.

Design-aware AI for modern product teams.

Hey Product Hunt 👋 I’m the maker of **XupaStack**. #What it does: keeps Supabase apps working for users in India when `*.supabase.co` is unreliable on some ISPs. #How: it’s a Cloudflare Workers gateway — your browser hits the gateway, gateway proxies to Supabase. #Setup: swap `SUPABASE_URL` → add Auth callback URL → run diagnostics/doctor. **Two modes (your choice):** ✅ Self-hosted (recommended):** deploys into *your* Cloudflare account (privacy-first). ⚡ Managed (fastest):** instant URL (different trust model; capacity capped). It’s free + open-source. If it saves your production app, there’s an optional donate link. Ask me anything — I’d love feedback on edge cases (Auth redirects, WebSockets, CORS).

Supabase India outage (Jio / Airtel / ACT) update + what I built 🇮🇳

When Supabase started failing for some Indian networks, I panicked and built XupaStack — a one-line “insurance switch” to keep apps working if *.supabase.co becomes unreachable again.

And now the best update: Supabase says connectivity is restored (Monitoring).

Honestly… that’s the outcome I wanted most. Every builder shipping with Supabase deserves peace.

I was a bit late building this… but I still shipped what I wish existed during the incident:

I built XupaStack (https://xupastack.com)

A free, open-source reliability switch for Supabase in India.

If reachability ever breaks again, the fix is a one-liner:

✅ same anon key (unchanged)

✅ no code changes

✅ supports REST / Auth / Storage / Functions / Realtime (WebSockets)

✅ vibecoder + non-technical builder friendly (copy → paste → done)

Security & privacy (important):

You choose the trust model:

1) Self-hosted (recommended 🔐): deploys into your Cloudflare account with one command → you control the data plane. Includes step-by-step instructions + a mini dashboard to lock CORS / services / rate limits.

2) Managed (fastest ⚡): instant gateway URL for emergencies (different trust model).

Also: XupaStack never asks for your Supabase keys. It’s designed as a transparent proxy (no payload logging by default).

Why I’m keeping it live (even after the fix):

Because this incident proved a painful truth: reachability failures are silent. Your app can look perfect in your testing… and real users see blank screens. Having an “insurance switch” matters.

What’s next (bigger than Supabase):

I’m expanding XupaStack into a universal “Connectivity Failover Layer” for builders shipping in India:

One dashboard to test real-user reachability (Wi-Fi vs mobile networks)

One-click fallback domains for multiple backends (not just Supabase)

“Provider health” diagnostics + alerts so you catch outages before users do

Self-host first, privacy-first, open-source by default.

If you’re a founder/dev shipping Ideas and you’ve ever been burned by an ISP/DNS issue, I’d love your feedback on which providers should be supported next.