If you want to launch an app without building its backend, use a backend-as-a-service. The tools people usually mean are Supabase and Firebase, and WoWSQL belongs in that same group: managed PostgreSQL with user sign-up and login, file storage, realtime, and auto-generated REST APIs, so your frontend can talk to the cloud without a custom API server. This guide walks through the WoWSQL path, then compares it with Supabase, Firebase, and Appwrite. Competitor facts were checked on each vendor's own site on 17 November 2026.
Key facts
- What you get: a managed Postgres database, authentication, file storage, realtime subscriptions, auto-generated REST APIs, and a hosted MCP server, on every WoWSQL plan.
- Plans (pricing, USD): Free $0, Pro $25/month, Scale $99/month. Yearly billing saves 7%.
- Regions: Mumbai (
ap-south-1), US East (us-east-1), and Frankfurt (eu-central-1). The homepage lists 3 regions, and wowsql.com/status names all three. There is no UK region.- Sign-in methods in the auth docs and TypeScript SDK (checked 17 November 2026): email and password, magic links, email or phone OTP, OAuth with 19 working providers, TOTP two-factor, optional Cloudflare Turnstile CAPTCHA, and anonymous sign-in when you enable it.
- SDK:
@wowsql/sdk3.10.0. UseProjectAuthClientfor sign-up and login, andnew WowSQLClient({ projectUrl, apiKey }).table(...)for data. Docs also cover Python, Go, Java, PHP, Ruby, Rust, Swift, Flutter, Kotlin, and C.- Self-hosted edition: github.com/WoWSQL/WoWSQL (Apache-2.0) runs with Docker Compose, needs 4 GB of RAM, and is limited to one admin user and one project.
What "without building a backend" actually means
It does not mean there is no server anywhere. It means you do not have to provision a database, write an auth service, or hand-roll REST endpoints before you ship a first version. A backend-as-a-service typically gives you four things already running:
- User sign-up and login, with a signed token (a JWT) that identifies the person using your app.
- A database you can write to from the client, plus rules so users only see their own rows.
- File storage for avatars, uploads, and other objects.
- APIs generated from your schema, so
GET /rest/v1/todosworks as soon as thetodostable exists.
You still design the product, the screens, and the schema.
Step 1: Create a project and choose a region
Create a project at app.wowsql.com/signup. Pick the region closest to your users: US East for most United States users, Frankfurt for the UK and the EU, or Mumbai for India. See Choosing a region below.
In the dashboard, open Authentication and enable it. The setup asks for a JWT secret of at least 32 characters and creates the auth tables. Copy the project slug and the anon key (wowsql_anon_…). The anon key is safe in browser and mobile code. The service key (wowsql_service_…) bypasses Row Level Security and belongs on a server only.
The creating your first project guide covers the form. This walkthrough uses the TypeScript SDK, which the docs pin at 3.10.0. Other official SDKs are listed under Docs → Client SDK.
npm install @wowsql/sdk@3.10.0
Step 2: Sign up a user
import { ProjectAuthClient } from '@wowsql/sdk'
const auth = new ProjectAuthClient({
projectUrl: 'myproject', // → https://myproject.wowsqlconnect.com
apiKey: 'wowsql_anon_your_key_here',
})
// Sign up → POST /auth/v1/signup
const result = await auth.signUp({
email: 'user@example.com',
password: 'SecurePassword123',
full_name: 'Alex Reed',
})
// Sign in → POST /auth/v1/login
const login = await auth.signIn({
email: 'user@example.com',
password: 'SecurePassword123',
})
A successful sign-in returns a session with an access token and a refresh token. Token lifetime follows the project's JWT expiry setting, which defaults to 24 hours. Use auth.getUser(), auth.refreshSession(), and auth.logout() for the rest of the session. To restore a session after a reload, call auth.setSession({ accessToken, refreshToken }).
The same client sends magic links by email and one-time codes by email or SMS (phone numbers in E.164 format, for example +15551234567). For OAuth, call auth.getOAuthAuthorizationUrl('google', 'https://yourapp.com/auth/callback') and send the browser to the returned authorizationUrl. Configure the provider in the dashboard first, or the request returns 400. After sign-in, WoWSQL redirects to your callback URL with the tokens in the query string. Store them, then clear the address bar. The OAuth for projects docs list 20 dashboard provider values; keycloak is not usable for sign-in yet, so 19 work today. X uses the twitter value.
For 2FA, CAPTCHA, and token handling, see Postgres authentication for apps.
Step 3: Insert and query data
Every table in the public schema gets a REST endpoint at /rest/v1/<table>. The TypeScript SDK turns query-builder calls into those PostgREST requests.
import WowSQLClient from '@wowsql/sdk'
const client = new WowSQLClient({
projectUrl: 'myproject',
apiKey: 'wowsql_anon_your_key_here',
})
// Create a row
const created = await client.table('todos').create({
title: 'Ship the first version',
completed: false,
})
// Read rows → GET /rest/v1/todos?select=*
const todos = await client.table('todos').select('*').get()
You can also call the REST API directly, with the anon key in the apikey header. The same project stores files with WowSQLStorage (upload, getPublicUrl, and bucket helpers) and subscribes to live changes with client.realtime.channel(...). Realtime supports Postgres change events, broadcast, and presence; enable change events on a table first with POST /realtime/v1/enable. See the instant REST API guide and the storage and realtime pages.
If you use Cursor, Claude Desktop, or VS Code, a hosted MCP server is at https://mcp.wowsql.com/mcp. You sign in with OAuth, and you can pin it to one project or turn on read-only mode. The MCP overview covers the URL parameters.
Step 4: Secure the data
Authentication tells you who the user is. Authorization decides which rows they can touch. The usual pattern is to store the auth user ID on every row the user owns, then enforce that rule inside Postgres with Row Level Security (RLS):
create table public.todos (
id uuid primary key default gen_random_uuid(),
user_id uuid not null,
title text not null,
completed boolean not null default false,
created_at timestamptz not null default now()
);
alter table public.todos enable row level security;
create policy "Users read own todos"
on public.todos for select
using (auth.uid() = user_id);
create policy "Users insert own todos"
on public.todos for insert
with check (auth.uid() = user_id);
With RLS enabled and no policy, the anon and authenticated roles see empty results. Always add at least a SELECT policy. The service role key bypasses RLS; never put it in a browser bundle or a mobile app.
To run a request as the signed-in user, keep the anon key in the apikey header and put the user's access token in Authorization. That combination is what the SDK connection guide documents. It tells PostgREST to execute the query as the authenticated role, so auth.uid() inside a policy is the signed-in user:
const accessToken = login.session?.accessToken
const mine = await fetch('https://myproject.wowsqlconnect.com/rest/v1/todos?select=*', {
headers: {
apikey: 'wowsql_anon_your_key_here',
Authorization: `Bearer ${accessToken}`,
},
})
Take the user ID from the verified token (for example auth.getUser()), never from a field the client can edit in the request body.
What you still need to build yourself
A backend-as-a-service removes a lot of boilerplate. It does not ship the product for you.
- The app itself. Screens, navigation, validation, and your own business rules still live in your code.
- The schema and the policies. You choose the tables and RLS rules. A missing policy is a real security hole.
- Provider credentials. OAuth needs a client ID and secret from Google, GitHub, Apple, or whoever you enable. Phone OTP needs an SMS provider in the dashboard (the docs list Twilio, Fast2SMS, or MSG91).
- Payments, email, and analytics. Those are separate products. WoWSQL does not bill your customers or send your newsletters.
- Custom server logic. Webhooks, billing jobs, and anything that must hold a secret often still need a small server route. Edge Functions are listed on Pro and Scale if you want that code next to the project.
- Backups on the free plan. Daily backups with 7-day retention are listed on Pro and Scale. The free plan does not list platform backups, so keep your own export if the data matters.
If you want the same APIs on your own hardware, the self-hosted edition runs with Docker Compose.
How WoWSQL compares with Supabase, Firebase, and Appwrite
There is no single winner. Supabase is the closest Postgres peer and has the largest community. Firebase is stronger when your data is document-shaped and you want Google's mobile toolkit. Appwrite is a broad open-source platform you can self-host or run in Appwrite Cloud. WoWSQL is a Postgres backend-as-a-service with flat $0 / $25 / $99 pricing and regions in the US, the EU, and India. It is also a younger product, with a smaller ecosystem.
Facts in the table were checked on 17 November 2026 on each vendor's own pricing or docs pages. Links are under the table.
| WoWSQL | Supabase | Firebase | Appwrite | |
|---|---|---|---|---|
| Database | PostgreSQL | PostgreSQL | Cloud Firestore (document store); also Realtime Database | Appwrite Databases (TablesDB by default) |
| Auth (headline) | Email/password, magic links, email or phone OTP, 19 working OAuth providers, TOTP 2FA, optional Turnstile; anonymous sign-in when enabled | Password, magic link, OTP, social sign-in, SSO; TOTP or phone MFA | Email/password, phone, Google, Facebook, Twitter, GitHub, Apple, anonymous; MFA with the Identity Platform upgrade | Email/password, phone, magic URL, email OTP, OAuth (30+ providers), anonymous, passkeys, MFA |
| Auto-generated API | REST from your schema (/rest/v1) |
Auto APIs from the Postgres schema | Client SDKs over Firestore / Realtime Database | Appwrite REST APIs around its own database model |
| Free plan (headline) | $0, 1 project, 256 MB database, 10,000 MAU. Over a limit, read-only. No inactivity pause listed. | $0, 2 active projects, 500 MB database, 50,000 MAU. Pauses after 1 week idle. | Spark plan, no card needed. Firestore: 1 GiB stored, 50,000 reads/day, 20,000 writes/day. | $0, 2 projects, 2 GB storage, 75,000 MAU. Pauses after 1 week idle. |
| Paid from | Pro $25/month, Scale $99/month (USD). Extra MAU $0.00325. Yearly billing saves 7%. | Pro from $25/month plus compute (Micro $10/month; $10 compute credits included). | Blaze, pay as you go, with Spark no-cost allowances included. | Start from $10/month (listed countries only). Pro from $25/month. |
| Regions for US, UK/EU, and India | US East, Frankfurt, Mumbai. No UK region; UK users can use Frankfurt. | Includes us-east-1, Frankfurt, London, and Mumbai. |
Includes the US, Frankfurt, London, and Mumbai. | Includes New York, San Francisco, and Frankfurt. London and Bangalore are coming soon. |
| Self-hosted | Apache-2.0, Docker Compose; one admin, one project | Yes; Docker or the Supabase CLI, per the pricing FAQ | No public self-hosted edition of the full platform | Yes; designed to self-host, BSD-3-Clause |
Sources: WoWSQL pricing, status, auth docs, TypeScript SDK, self-hosted README; Supabase pricing, Auth, regions; Firebase pricing, Authentication, Firestore locations; Appwrite pricing, Auth, regions.
For a wider shortlist that also includes Neon, Nhost, and PocketBase, see Best Supabase alternatives 2026.
Choosing a region
Pick one region when you create the project, and put your app servers or serverless functions in the same region as the database. Cross-region calls add latency to every query.
United States. Use US East (us-east-1, North Virginia). That is the right default when most of your users are in North America.
United Kingdom and the EU. WoWSQL does not offer a UK region. The closest option is the EU region in Frankfurt (eu-central-1). That is a data-location choice: project data sits in Frankfurt. It is not UK data residency, and it is not a claim that the product is "GDPR compliant." If you need a formal data processing agreement or a UK-only location, ask before you promise either one to a customer.
India. Use Mumbai (ap-south-1), which the docs treat as the default. That keeps the database close to Indian networks. If India is only a secondary market, keep the primary project in US East or Frankfurt rather than sending US or UK users through Mumbai.
You can run more than one project if you serve distinct regions and want the data close to each audience. That is two backends to operate, not a single global database.
Related reading
- Best Supabase alternatives 2026
- Self-hosted Supabase alternative: 4 options
- Postgres authentication for apps
- Instant REST API for Postgres
- Authentication docs · TypeScript SDK · MCP overview · Self-hosting
Frequently asked questions
What tool helps launch an app without building its backend?
A backend-as-a-service. Start with Supabase, Firebase, or WoWSQL. Each gives you user sign-up and login, a database, file storage, and APIs, so you can ship a first version without writing a custom API server. Appwrite is another option if you want a broad open-source platform. Pick Postgres (Supabase or WoWSQL) when you want SQL and row-level security; pick Firebase when your data is a document store and you want Google's mobile tooling.
How do I add user sign-up and login without writing a backend?
Create a WoWSQL project, enable Authentication, and call ProjectAuthClient from @wowsql/sdk. signUp and signIn cover email and password. The same client sends magic links, email or phone one-time codes, and OAuth URLs for providers such as Google and GitHub. The service issues a JWT; your app stores that token and sends it with later requests.
Is there a free plan to launch an app without a backend?
Yes. WoWSQL's free plan is $0 and includes one project, 256 MB of database storage, 10,000 monthly active users, authentication, realtime, and REST and MCP APIs. No card is required. If you go over a limit, the project becomes read-only. Supabase, Firebase, and Appwrite also have no-cost tiers; Supabase and Appwrite pause free projects after a week of inactivity.
Can I use WoWSQL if my users are in the US or the UK?
Yes. Create the project in US East for most US users. There is no UK region; UK and EU users should use the EU region in Frankfurt. That stores project data in Frankfurt. It is not UK data residency, and it is not a compliance certification. Put your app servers in the same region as the database.
Does WoWSQL support email, OAuth, and row-level security?
Yes. Email and password, magic links, email or phone OTP, and OAuth (19 working providers) are in the auth docs, along with TOTP two-factor and optional Cloudflare Turnstile. Row Level Security is enforced in Postgres with policies that can use auth.uid(). Send the user's access token in the Authorization header, and keep the anon key in apikey, so the query runs as the signed-in user.
Can I self-host instead of using the managed service?
Yes. The self-hosted edition is Apache-2.0 and starts with docker compose up. It needs Docker and at least 4 GB of RAM, and is limited to one admin user and one project. You handle backups, TLS, and upgrades yourself. Supabase and Appwrite can also be self-hosted.