All Case Studies
Case Study

SupaStack: Free Cloudflare Proxy for Supabase Access

A free Cloudflare-powered proxy that makes Supabase work in India and anywhere it is restricted. One URL change in the developer's project, zero configuration, zero cost.

Client: SupaStack (xupastack.com)

Visit live site
Timeline
1 week
Investment
$3,999
Key Result
1,000+ developers using the proxy

SupaStack landing page showing the one-line URL change that fixes Supabase access in restricted regions.

The Challenge

Supabase, one of the most popular open-source backend platforms, is blocked or severely throttled in India and several other regions. Developers building production applications on Supabase suddenly find their apps broken for a large portion of their user base. The existing workarounds (VPNs, self-hosted instances) are either unreliable, expensive, or too complex for indie developers to maintain.

Our Approach

We built a Cloudflare Worker that acts as a transparent proxy between the developer's application and Supabase's API endpoints. The developer changes one URL in their Supabase client configuration and everything works. No SDK changes, no server-side modifications, no complex networking setup. The proxy handles authentication passthrough, request routing, and edge caching for static assets. Deployed globally on Cloudflare's edge network for minimal latency.

What We Built

Cloudflare Worker proxy that transparently routes all Supabase API requests
Authentication passthrough that preserves Supabase auth tokens and RLS policies
Edge caching layer for static assets and frequently accessed data
Landing page with one-click setup instructions and real-time status monitoring
Custom domain routing so developers get a clean proxy URL

Delivery Timeline

Day 1-2: Proxy Core

Built the Cloudflare Worker with request routing, auth passthrough, and error handling.

Day 3-4: Edge Optimization

Added caching layer, latency monitoring, and global deployment testing across 10 regions.

Day 5-7: Landing + Launch

Built the landing page, setup instructions, and deployed. Shared in developer communities.

Tech Stack

Cloudflare Workers
Edge Runtime
TypeScript
Language
React + Tailwind
Landing Page
Cloudflare DNS
Routing

Architecture

proxy

Cloudflare Worker with TypeScript, handling request/response transformation and routing

edge

Deployed across 300+ Cloudflare edge locations for global low-latency access

caching

Intelligent cache headers for static assets, pass-through for dynamic API calls

Security

auth

Full authentication passthrough, no credentials stored or logged by the proxy

encryption

End-to-end TLS between client, proxy, and Supabase. No plaintext data in transit

isolation

Each request is isolated in its own Cloudflare Worker execution context

The Results

Developer adoption
01,000+ developers
Setup complexity
VPN or self-hostOne URL change
Cost to developer
$20-50/month (VPN)Free

Key Takeaways

The simplest possible developer experience wins adoption. One URL change beats any amount of documentation or configuration guides.

Cloudflare Workers gave us global edge deployment with zero cold starts. The proxy adds less than 10ms of latency in most regions.

Building a free tool that solves a real pain point for developers creates organic distribution. The tool spread through dev communities without any marketing spend.

Deliverables

Cloudflare Worker source codeLanding page with setup instructionsStatus monitoringDocumentation

FAQ

Frequently Asked Questions

Related Case Studies

Want similar results?

Book a free 15-min scope review. Your vision, engineered for production in 14 days. Fixed price.

Book Scope Review