# Scribase for mobile apps

> Scribase for mobile: auth, file storage and realtime on real Postgres, the client SDK you already know, relational data, and a flat price per project.

Source: https://scribase.com/for/mobile-backend

Mobile teams want auth, file storage, and live updates without stitching five services together — and without a bill that punishes a chatty client. Scribase gives you all of it behind one SDK on the device, on relational Postgres with a flat price per project.

## What this audience is building

- Auth, storage, and realtime from one backend, one SDK
- Relational queries instead of denormalized documents
- Pricing that does not punish a chatty mobile client

## How Scribase meets each need

**One SDK, one backend** — Your existing client SDK handles auth, data, storage, and realtime against Scribase by changing the URL and keys, so the app needs no rewrite.

**Relational data, not documents** — Model your app in Postgres with joins and constraints instead of denormalizing into documents, and enforce access with row-level security that realtime honors too.

**Flat pricing for chatty clients** — There is no per-read or per-write meter, so a busy client syncing often does not translate into a surprise invoice. You pick a plan with hard caps.

_# point the client you already ship at Scribase_

```
import { createClient } from '@supabase/supabase-js'

const client = createClient(
  process.env.SCRIBASE_URL!,
  process.env.SCRIBASE_ANON_KEY!,
)
```

## FAQ

**Can I keep my existing client SDK in my mobile app?**

Yes. The data-plane paths are contract-tested with the standard JavaScript client, so it works by setting the URL and keys, with no rewrite.

**Does Scribase do offline-first sync?**

Not yet. Scribase provides relational Postgres, realtime subscriptions, and standard queries at a flat price per project; offline-first sync is not built in.

## Related

- [Mobile app backend use case](https://scribase.com/use-cases/mobile-app-backend)
- [Pricing](https://scribase.com/pricing)