/* Import the Poppins font from Google Fonts */
@import url('https://fonts.googleapis.com/css2?family=Poppins:wght@400&display=swap');

/* Apply the Poppins font to the body and all headings */
body, h1, h2, h3, h4, h5, h6 {
    font-family: 'Poppins', sans-serif;
}



Learn how to integrate PowerSync with your favorite tools.

Integrations Overview

PowerSync

Sync Engine for Local-First & Offline-First Apps

PowerSync Overview

Our vision is that a local-first or offline-first app architecture should be easier for the developer than cloud-first, and give a better experience for the end-user — even when they're online.

PowerSync Philosophy

Quickstart / Overview

Quickstart Guide / Installation Overview

Connect a PowerSync Cloud instance to your backend database.

Database Connection

Integration guide for deploying a Postgres database and custom backend using Railway for Postgres and Node.js hosting.

Railway + PowerSync

Integration guide for deploying the [PowerSync Service](http://localhost:3333/architecture/powersync-service) on Coolify

Coolify + PowerSync

Deploy PowerSync Service on Coolify

This guide lays out all the steps of migrating from MongoDB Atlas Device Sync to PowerSync.

MongoDB Atlas Device Sync Migration Guide

WatermelonDB Migration Guide

The core components of PowerSync are the service and client SDKs

Architecture Overview

PowerSync Service

Client Architecture

PowerSync Protocol

PowerSync uses the concept of "checkpoints" to ensure the data is consistent.

Consistency

PowerSync supports multiple client-side frameworks with official SDKs

Introduction

Self-host PowerSync in your own infrastructure (PowerSync Open Edition or PowerSync Enterprise Self-Hosted Edition).

Getting Started

Using Docker Compose to simplify your local development stack

Local Development

Enterprise

A collection of tutorials showcasing solutions to common use cases across the PowerSync stack.

Overview

Tutorials

A collection of tutorials for client-side use cases.

A collection of tutorials related to self-hosting.

In this tutorial we will show you how to generate a development token for the self-hosted [PowerSync Service](https://powersync.mintlify.app/architecture/powersync-service#powersync-service).

Generate a Development Token

Gallery of example projects built with PowerSync.

Demo Apps / Example Projects

Performance and Limits

PowerSync feature states and their implications for factors such as API stability and support.

Feature Status

Hardware and OS

Supported Hardware and Operating Systems

Frequently Asked Questions about PowerSync.

How does PowerSync fit in to the local-first software movement?

Local-First Software

Release Notes

Roadmap

Blog

Details on PowerSync Cloud's cybersecurity posture

Security

Contact Us

GitHub

Community Discord

PowerSync Dashboard

PowerSync Website

Client SDKs

Self-Hosting

Resources

Get Started

Dashboard

Configure your backend database for PowerSync

Source Database Setup

Security & IP Filtering

Private Endpoints

Include the PowerSync Client SDK in your project

Client-Side Setup

You need to set up your client-side schema in your app project. This involves defining your schema in code using the PowerSync syntax.

Define your Schema

You need to instantiate the client-side PowerSync database — this is the core managed local SQLite database.

Instantiate PowerSync Database

The PowerSync 'backend connector' provides the connection between your application backend and the PowerSync client-slide managed SQLite database.

Integrate with your Backend

App Backend Setup

Your app backend needs to expose an API endpoint to write changes to your backend database that are received from the PowerSync client.

Writing Client Changes

Authentication Setup

Development Tokens

Firebase Auth

Auth0

Any authentication provider can be supported by generating custom JWTs for PowerSync.

Custom

Sync Rules

The simplest Sync Rules are for "global" data — synced to all users. 

Global Data

Organize Data Into Buckets

Parameter Queries

Data Queries

PowerSync's Sync Rules use the [SQLite type system](https://www.sqlite.org/datatype3.html).

Types

On the client, PowerSync only supports a single primary key column called `id`, of type `text`.

Client ID

Operators and functions can be used to transform columns/fields before being synced to a client.

Operators and Functions

Schemas and Connections

For simplicity, we recommend using only lower case identifiers for all table/collection and column/field names used in PowerSync. If you need to use a different case, continue reading.

Case Sensitivity

A group of rows/documents, from one or more tables/collections.

Glossary

Guide: Many-to-Many and Join Tables

This section covers use cases that will arise throughout the lifetime of your application as you add new features, refactor tech debt into oblivion, and upgrade dependencies.

Lifecycle / Maintenance

Implementing Schema Changes

The general approach is that for transient errors (e.g. server or database unavailable), the changes are kept in the client-side upload queue, and retried at 5 second intervals, keeping the original order. In the future it will be possible to control the retry behavior.

Handling Write / Validation Errors

Upgrading the Client SDK

Postgres Maintenance

[Buckets](/usage/sync-rules/organize-data-into-buckets) store data as a history of changes, not only the current state.

Compacting Buckets

Learn how to use PowerSync in common use cases

Use Case Examples

Syncing large attachments/files directly using PowerSync is not recommended.

Attachments / Files

You might want to run PowerSync operations while the client device is inactive or the app is in the background.

Background Syncing

While PowerSync does not use [CRDTs](https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type) directly as part of its sync or conflict resolution process, CRDT data (from a library such as [Yjs](https://github.com/yjs/yjs) or y-crdt) may be persisted and synced using PowerSync.

CRDTs

PowerSync is fully compatible with more advanced Postgres types.

Custom Types, Arrays and JSON

Data Encryption

Client-side full-text search (FTS) is available using the [SQLite FTS5 extension](https://www.sqlite.org/fts5.html).

Full-Text Search

Infinite scrolling is a software design technique that loads content continuously as the user scrolls down the page/screen.

Infinite Scrolling

Some use cases require data persistence before the user has registered or signed in.

Local-only Usage

Custom types, arrays and [PostGIS](https://postgis.net/) are frequently presented together since geospatial data is often complex and multidimensional.

PostGIS

In some scenarios, you may want to sync tables using different priorities. For example, you may want to sync a subset of all tables first to log a user in as fast as possible, then sync the remaining tables in the background.

Prioritized Sync

Use Custom Write Checkpoints to handle asynchronous data uploads, as in chained data pipelines.

Data Pipelines

Tools

Introduction to and overview of the PowerSync Dashboard and Admin Portal

Manage your PowerSync Cloud environment programmatically

CLI (Beta)

Diagnostics App

Overview of monitoring and alerting functionality for PowerSync Cloud instances

Monitoring and Alerting

CloudCode (for MongoDB Backend Functionality)

Tutorial-style integration guide for creating offline-first apps with Supabase and PowerSync, using a demo to-do list app in Flutter, React Native, Web, Kotlin Multiplatform and Swift.

Supabase + PowerSync

Examples of syncing attachments between a client app and Supabase Storage.

Handling Attachments

Real-time Streaming

RLS and Sync Rules

Local development with Supabase and PowerSync.

Integration guide for creating local-first apps with FlutterFlow and PowerSync with Supabase as the backend.

FlutterFlow + PowerSync

Learn how to sync attachments such as images and PDFs with PowerSync, FlutterFlow and Supabase Storage.

Flutter Web

PowerSync supports [Full-Text Search](/usage/use-case-examples/full-text-search) on all Flutter platforms.

Legacy integration guide for creating local-first apps with FlutterFlow and PowerSync with Supabase as the backend.

Legacy Guide

FlutterFlow + PowerSync Legacy Guide

Full SDK reference for using PowerSync in Flutter/Dart clients

Flutter

Web Support (Beta)

Flutter Web Support (Beta)

ORM Support (Alpha)

Flutter ORM Support (Alpha)

Code snippets and guidelines for common scenarios

Usage Examples

Guidelines for unit testing with PowerSync

Unit Testing

Encryption

API Reference

Full SDK reference for using PowerSync in React Native clients

React Native & Expo

React Native Web Support

ORM Support

JavaScript ORM Support

Full SDK reference for using PowerSync in JavaScript Web clients

JavaScript Web

JavaScript SPA Frameworks

Kotlin Multiplatform (Beta)

Swift (Beta)

Migrating from Alpha to Beta

SDK reference for using PowerSync in Node.js clients.

Node.js client (alpha)

SDK reference for using PowerSync in .NET clients.

.NET (alpha)

Deploy PowerSync on your own infrastructure (PowerSync Open Edition or PowerSync Enterprise Self-Hosted Edition).

Installation

Configuration details for connecting the PowerSync Service to your database

PowerSync Service Setup

From a security perspective, the primary activity required will be placing a load balancer with TLS in front of PowerSync. 

Securing Your Deployment

Healthchecks

Telemetry

Migrating users between PowerSync instances

Migrating between instances

Multiple PowerSync Instances

Appendix

A collection of tutorials exploring storage strategies.

In this tutorial, we will show you how to replace Supabase Storage with AWS S3 for handling attachments in the [React Native To-Do List demo app](https://github.com/powersync-ja/powersync-js/tree/main/demos/react-native-supabase-todolist).

Introduction

Installation

Usage

Integration Guides

Migration Guides

Architecture

Integrations Overview

Supabase + PowerSync

FlutterFlow + PowerSync

Railway + PowerSync