Back to the blog

Self-Hosted Sync After Atlas App Services

How BarqDB separates local data, JWT authentication, and a sync server you operate yourself.

A self-hosted sync stack changes the ownership line. Your team controls deployment, keys, limits, storage, upgrades, and recovery instead of attaching the app to a managed App Services backend.

BarqDB keeps the local database usable without the server. Sync is an added route, not a requirement for opening the app database.

Bring your own identity

Your identity provider signs an access token. BarqDB reads the tenant and user identity from that JWT and the server verifies it using your public key.

This makes authentication replaceable. It also means you must own key rotation, tenant boundaries, and token lifetimes.

Start with an operations checklist

Run TLS, keep unsigned-token mode out of production, back up the sync root, set tenant limits, monitor storage, and rehearse upgrades before moving real users.

Use the BarqDB production guide for the current server flags and exact SDK support.

Self-Hosted Sync After Atlas App Services | BarqDB