Supabase-compatible backend · inside the Kingdom
Your data docks
inside the Kingdom.
Postgres, auth, file storage and realtime, with the Supabase APIs your team already knows, on a cloud inside Saudi Arabia. Sign-up codes go out through a Saudi SMS provider, and you're billed in SAR.
Early access is open · we're choosing the first projects now
import { createClient } from '@supabase/supabase-js'
- createClient(SUPABASE_URL, ANON_KEY)+ createClient(MURSA_URL, MURSA_ANON_KEY)
Same supabase-js library. Change only the URL and the key.
The problem
Government work is hosted inside the Kingdom, and hosting it abroad needs a justification. SAMA-regulated firms need approval before hosting offshore. And Supabase has no Middle East region. The problem doesn't stop at the database: the sign-up code usually leaves the country through a foreign SMS provider.
Where does your data go?
Usually: copies of your data live outside the Kingdom.With Mursa: every copy inside the Kingdom, and a report that proves it.
0 of 6 copies inside the Kingdom
An example of what the residency report shows for each project. The first cell is planned in Dammam, and where the SMS and email providers process messages is something we verify before launch. The platform has a test that fails if any configured endpoint is outside the Kingdom.
Who it's for
For teams whose data has to stay here.
You sell to government or regulated buyers.
Your client requires its data to be hosted in the Kingdom. Move your backend as it is, and hand them a report showing where every copy lives.
- A dedicated server per customer
- A residency report to attach to your bid
- A SAR invoice per project
You build on Supabase and need to stay in the Kingdom.
Your users' data and their sign-up codes stay in the Kingdom, without rewriting your app or running servers yourself.
- The same libraries and APIs
- Your project moved over from Supabase
- Sign-up codes through a Saudi provider
How it works
From your current project to a backend inside the Kingdom.
01We set up your project
A dedicated server on an in-Kingdom cloud, running the open-source Supabase components unchanged.
02We move your data
From Supabase: schema, data, auth users and files.
03You change two lines
Your app stays as it is. Change the URL and the key, and it runs.
04You get the residency report
Where every copy of your data lives, to hand to your client or your counsel.
New project
Cell: Dammam
Import from Supabase
Example
app.js
import { createClient } from '@supabase/supabase-js'
- createClient(SUPABASE_URL, ANON_KEY)+ createClient(MURSA_URL, MURSA_ANON_KEY)
Residency report
Illustrative example
What you get
A whole backend, not just a database.
Postgres 17
The official Supabase image, on a dedicated server per customer.
Auth and sign-up codes
Sign-up codes sent through Unifonic or Taqnyat instead of foreign providers.
PostgREST · Realtime · Storage
Files on in-Kingdom storage, behind the same Supabase APIs.
Backups that get tested
Continuous WAL-G backups and an automatic restore test every week.
Residency report
Every copy, with its location: database, WAL, files, backups, SMS and email.
Billing in SAR
Payment through Moyasar and a ZATCA e-invoice.
Supabase Studio dashboard
The same open-source dashboard your team already knows.
Oracle in Riyadh and Jeddah
More in-Kingdom cells after the Dammam cell.
AWS Riyadh
Once the region opens, announced for December 2026.
Where we are now
The platform is built and covered by automated tests; the next step is running it on the first cell in Dammam. No customers yet, which is why we're looking for the first projects to launch with.
Pricing
A monthly subscription per project in SAR, with an e-invoice. We'll publish prices at launch, and the early-access list hears them first.
FAQ
Before you ask.
Is Mursa Supabase?
No. Mursa runs the open-source Supabase components unchanged, on a server dedicated to you inside the Kingdom, so your app keeps using the Supabase libraries. Mursa is not affiliated with Supabase.
Which cloud?
The first cell is planned on Google Cloud in Dammam, then Oracle in Riyadh and Jeddah, then AWS Riyadh once it opens.
Does this make me PDPL-compliant?
We don't claim that. We give you the residency report as evidence of where every copy of your data lives; compliance is your call with your counsel. The proposed PDPL amendment to keep a copy of personal data in the Kingdom (Article 23(2)) is still a draft and has not been issued.
Do sign-up SMS codes stay in the Kingdom?
We connect auth to Saudi SMS providers (Unifonic or Taqnyat) instead of the usual foreign ones. We verify where they process messages before launch, and it shows in the report.
How do you handle backups?
Continuous WAL-G backups to in-Kingdom storage, and an automatic restore test every week. A backup we haven't restored doesn't count as a backup.
When do you launch?
The platform is built, and the next step is running it on the first cell. The early-access list tries it first, and we talk to each of them directly.
Early access
Be one of the first projects on Mursa.
Leave your details and what you're building, and we'll get in touch to understand your hosting requirements.
- A short call to understand your clients' requirements
- Priority access when the first cell goes live
- Prices before the public announcement