M
Infrastructure Report March 2026 · India Edition

Your backend, finally on Indian ground.

PostgreSQL infrastructure hosted in Mumbai, governed by Indian law, billed in rupees. Fully compatible with the Supabase JS SDK — migrate in one line of code.

Works on · Jio Airtel ACT BSNL Vi · All Indian ISPs
Live Infrastructure Status
953
Free slots remaining of 1,000 total — closing soon
API Latency · Mumbai
<10ms
AWS ap-south-1 · Chennai edge node
Uptime SLA
99.9%
Guaranteed. Not marketing.
Data stays in India
100%
Zero cross-border data routing
Recent signups
Arjun K. Chennai · Developer
Priya M. Bengaluru · Free
Rahul S. Hyderabad · Student
Kavya R. Coimbatore · Free
PostgreSQL 16 · Mumbai
DPDP Compliant
Real-time Subscriptions
INR Billing · UPI
Row Level Security
WhatsApp Notifications
Zero Foreign Dependency
Edge Functions · Deno
Supabase SDK Compatible
PostgreSQL 16 · Mumbai
DPDP Compliant
Real-time Subscriptions
INR Billing · UPI
Row Level Security
WhatsApp Notifications
Zero Foreign Dependency
Edge Functions · Deno
Supabase SDK Compatible
99.9%
Uptime SLA
<10ms
Mumbai Latency
100%
Data in India
20+
Years Saravonix Heritage
1 line
Migration from any SDK
The Problem, Explained

What actually happens when
foreign infrastructure fails you

Most developers see an error screen. Here is the three-layer failure underneath — and why each "fix" leaves you exposed.

Infrastructure Incident Report
February 24, 2026
365,000 Developers Affected · No ETA Given
What Happened
ISPs received orders to poison DNS resolution for foreign backend domains. Any lookup returned a government sinkhole IP instead of the real server address.
⚠ DNS POISONED
Why Proxies Fail Next
Proxies bypass DNS but cannot hide the Server Name Indication (SNI) header in TLS connections. Deep Packet Inspection reads this and blocks at the packet level.
⚠ DPI ESCALATION LIKELY
The Only Real Fix
Eliminate the foreign infrastructure dependency entirely. Indian servers have Indian IPs. Indian DNS resolves correctly. There is nothing in the chain to block.
✓ MAYONDB SOLUTION
🔒 mayondb.in/explainer

Layer 1 — DNS Poisoning: The request never reaches the server

Your app calls a foreign backend URL. Before the packet can travel, your ISP's DNS server intercepts the lookup and returns a fake IP address it controls — a "sinkhole." Your app connects to a wall.

DNS query → ← fake IP returned 💻 Your App 🏢 ISP DNS intercepts here 🚫 Sinkhole IP 49.44.79.236 INTERCEPTED
● TERMINAL OUTPUT — nslookup result
$ nslookup xyz.foreign-backend.com
Server: Jio-Internal-DNS-01
Address: 2405:200:d001:e8f1::1

Name: xyz.foreign-backend.com
Address: 49.44.79.236 ← ISP sinkhole, NOT the real server

ERR_CONNECTION_TIMED_OUT
Your app never reached the actual server.

Layer 2 — Deep Packet Inspection: Why proxies are temporary

A proxy bypasses DNS by routing through an unblocked domain. But DPI reads the SNI (Server Name Indication) header inside your TLS packet — which contains the real destination — and blocks at the network packet level. Proxies cannot hide the SNI header.

bypasses DNS ✓ reaches DPI → SNI blocked ✗ 💻 Your App 🔄 Proxy 🔍 DPI Scanner reads SNI header 🚫 Blocked Again
Proxy approach

Routes via an unblocked domain, so DNS works. But your TLS handshake still announces the real destination in the SNI field. DPI reads this and applies the block at packet level. Every proxy breaks when DPI is deployed.

MayonDB approach

Your SNI header says db.mayondb.in — an Indian server. DNS resolves to an Indian IP. DPI sees Indian-to-Indian traffic. There is nothing to flag. Nothing to block.

MayonDB — Zero dependency chain, Indian servers

MayonDB runs on independent infrastructure in Mumbai. Your DNS lookup returns a real Indian IP. Your data never crosses a border. There is no foreign server in the request chain — which means there is nothing for any authority to block.

Indian DNS resolves DPI: Indian-to-Indian ✓ 💻 Your App 🇮🇳 MayonDB Mumbai · India
● TERMINAL OUTPUT — clean connection
$ nslookup db.mayondb.in
Server: Indian-Resolver
Name: db.mayondb.in
Address: 13.235.x.x ← AWS Mumbai, Indian data centre

HTTP/2 200 OK · 8ms
Connected. No blocks. No proxies. No workarounds.
One Line Migration

Your existing code.
Indian servers.

MayonDB is fully API-compatible with the Supabase JS SDK. Every query, every auth call, every storage upload works identically. Change one environment variable.

  • supabase-js v2 fully supported
  • Same REST, GraphQL, and Realtime endpoints
  • Row Level Security policies migrate directly
  • Database dump → import supported
  • Auth users export and import
  • All SDK methods identical — no code changes
src/lib/client.js
// Before — foreign-hosted backend import { createClient } from '@supabase/supabase-js' const client = createClient(   'https://xyz.foreign-backend.com',   process.env.API_KEY )
// After MayonDB — Indian infrastructure ✓ import { createClient } from '@supabase/supabase-js' const client = createClient(   'https://db.mayondb.in'// ← that's it   process.env.MAYONDB_KEY )
// Same SDK. Same API. Same RLS policies. // Your data. Your country. Your servers.
What's Included

Everything your app needs.
Nothing based abroad.

01
🗄️
PostgreSQL Database

Full PG 16 with Studio UI, Row Level Security, and real-time WAL streaming. Your schema, your rules, your data.

SDK Compatible
02
🔐
Authentication

OTP via Indian SMS gateways. Google OAuth. Email magic links. Aadhaar-ready for institutional verification.

India First
03
Real-time

WebSocket-based live data subscriptions with sub-10ms latency to Indian users. Build collaborative apps that actually feel fast.

Free on All Plans
04
📱
WhatsApp Notifications

Trigger WhatsApp messages directly from database events. Reach Indian users where they actually communicate.

Exclusive Feature
05
📋
DPDP Compliance

India's Digital Personal Data Protection Act compliance built in — not bolted on. Data residency guaranteed. Audit-ready from day one.

Compliance Ready
06
☁️
File Storage

S3-compatible object storage with CDN delivery from Indian edge nodes. Images, documents, and media — all hosted in India.

CDN Included
Pricing

Indian prices.
World-class infrastructure.

INR billing. Pay via UPI, debit card, or net banking. No USD. No hidden fees.

🎁 Free Forever
₹0
no time limit
  • 100 MB PostgreSQL
  • 500 MB Storage
  • 10K API calls/month
  • Auth up to 100 users
  • Community support only
🎓 Student
₹10
per month
  • 500 MB PostgreSQL
  • 2 GB Storage
  • 50K API calls/month
  • Auth up to 500 users
  • Community support
🏢 Enterprise
Custom
contact us
  • Unlimited everything
  • DPDP Compliance Cert
  • On-premise option
  • Dedicated SLA
  • Unlimited WhatsApp
  • 24×7 dedicated support
Limited Availability

Secure your
free slot now.

The first 1,000 developers get permanent free access. No payment. No time limit. Your data in India, always.

953
Free slots remaining out of 1,000 total — closing soon
  • No payment collected during waitlist
  • You choose your plan — we confirm availability
  • Data never leaves India — guaranteed
  • Built by Saravonix — 20 years enterprise infrastructure
  • IST support. Indian team. Indian prices.
Reserve Your Slot
Choose a plan — no payment taken today
🔒 No payment now 🇮🇳 Data stays in India ✓ Cancel anytime
🎉
You're on the list!
We'll email you when your MayonDB account is ready.
Your slot is confirmed.