JioBase is a transparent reverse proxy project for Supabase, originally built to address DNS blocking of *.supabase.co by multiple ISPs in India. Instead of having an application access its Supabase project domain directly, it connects to a JioBase/Cloudflare proxy domain, which then forwards requests to Supabase. One important caveat: the captured text clearly states that the JioBase managed service has stopped. The hosted service is no longer available, and the official recommendation is to migrate back to the original Supabase URL or deploy your own proxy.
Functionally, JioBase covers the main Supabase API surfaces: REST/PostgREST, Authentication, Storage, Realtime WebSockets, Edge Functions, and GraphQL endpoints. Integration is lightweight: the core change is replacing the Supabase client URL, while business logic, anon keys, and RLS policies can remain unchanged. Its infrastructure is built entirely on Cloudflare, including Workers, D1, KV, and Pages, and it uses Hono, Drizzle ORM, SvelteKit, and Tailwind CSS v4.
On the open-source side, JioBase is licensed under AGPLv3. The project states that the full code is available on GitHub, allowing users to audit the proxy logic, API, and dashboard. Self-hosting is now the primary path: run npx create-jiobase to deploy your own Supabase reverse proxy to Cloudflare Workers, then change the client URL to the new Workers address.
The managed service was previously offered for free, with the author personally covering Cloudflare costs. The terms mentioned a free tier of 1 app and 50,000 requests per month. Since the hosted service has now been discontinued, the practical pricing model should be understood as free open-source self-hosting, with optional donations via Buy me a coffee. In terms of data handling, JioBase states that it does not read, parse, modify, cache, or log Supabase application traffic. However, Cloudflare terminates TLS at the edge, which is an important trust boundary to understand when using this type of proxy.
Its main strength is that it solves a very specific problem: when Supabase is unreachable on certain networks, it offers a low-change, auditable, self-hostable recovery path. Cloudflareβs edge network also helps make deployment convenient. The downsides are equally clear: the managed service has been shut down, so it should not be relied on as a long-term third-party service; availability depends on both Supabase and Cloudflare; and there is no clear SLA.
JioBase is best suited for developers affected by Supabase access blocking who are also capable of maintaining Cloudflare Workers. The source text does not provide information about accessibility from China, so this cannot be determined. If using it in mainland China, you should independently test connectivity to Cloudflare Workers, Supabase, and the related domains. Alternatives include returning directly to the official Supabase URL, building another reverse proxy, or evaluating backend-as-a-service/database options that are accessible domestically.
β This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on jiobase.com official site.
jiobase.com is an India Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of Workable. Click "Visit Official Site" to reach jiobase.com directly.