# A Postgres backend for mobile apps

> Back your mobile app with Postgres, auth, storage, and realtime through the client SDK you already know, with a flat price as you grow.

Source: https://scribase.com/use-cases/mobile-app-backend

Mobile teams want auth, file storage, and live updates without wiring five services together. Scribase gives you all of it behind one SDK on the client, with relational data and a flat bill.

## The pains this solves

- Per-read/per-write pricing that punishes chatty mobile clients
- Document databases that make relational queries painful
- Auth, storage, and realtime spread across separate vendors

## How Scribase addresses it

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

**Relational data, not documents** — Model your app in Postgres with joins and constraints instead of denormalizing into documents.

**Flat pricing for chatty clients** — No per-read or per-write meter, so a busy mobile client does not translate into a scary invoice.

## 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.

**Why Postgres for a mobile app?**

Relational data with joins and constraints, SQL when you need it, and row-level security that realtime honors too, all at a flat price per project.