Skip to main content
This page covers PowerSync Cloud. For self-hosted PowerSync, refer to this section.

​
Create a PowerSync Instance

When creating a project in the PowerSync Dashboard, a Development and Production instance will be created by default. Select the instance you want to configure. If you need to create a new instance, follow the steps below.
  1. In the dashboard, select your project and open the instance selection dropdown. Click Add Instance.
  1. Give your instance a name, such as “Production”.
  2. [Optional] You can change the default cloud region from US to EU, JP (Japan), AU (Australia) or BR (Brazil) if desired.
    • Note: Additional cloud regions will be considered on request, especially for customers on our Enterprise plan. Please contact us if you need a different region.
  3. Click Create Instance.

​
Specify Connection Details

Each database provider has their quirks when it comes to specifying connection details, so we have documented database-specific and provider-specific instructions below:

​
Postgres Provider Specifics

Select your Postgres hosting provider for steps to connect your newly-created PowerSync instance to your Postgres database:
  1. From your Supabase Dashboard, select Connect in the top navigation bar (or follow this link):
  2. In the Direct connection section, copy the complete connection string (including the [YOUR-PASSWORD] placeholder)
  3. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  4. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  5. Paste the connection string into the URI field. PowerSync will automatically parse this URI to populate the database connection details.
  6. Update the Username and Password fields to use the powersync_role and password you created when configuring your Supabase for PowerSync (see Source Database Setup).
  7. Note: PowerSync includes Supabase’s CA certificate by default, so you can use verify-full SSL mode without additional configuration.

Your Supabase connection details should look similar to this.

  1. Verify your setup by clicking Test Connection and resolve any errors.
  2. Click Save Connection.
PowerSync will now create an isolated cloud environment for your instance. This typically takes a minute or two.

​
Enable Supabase Auth

After your database connection is configured, enable Supabase Auth:
  1. In the PowerSync Dashboard, go to the Client Auth view.
  2. Enable the “Use Supabase Auth” checkbox.
  3. If your Supabase project uses the legacy JWT signing keys, copy your JWT Secret from your project’s settings (JWT Keys) and paste the secret into the “Supabase JWT Secret (optional) Legacy” field. If you’re using Supabase’s new JWT signing keys, you can leave this field empty.
  4. Click Save and Deploy to apply the changes.
PowerSync is compatible with Supabase’s new JWT signing keys. If you’re using the new keys, you don’t need to provide the legacy JWT secret. See this Discord thread for details.

​
Troubleshooting

Supabase is configured with a maximum of 4 logical replication slots, with one often used for Supabase Realtime.It is therefore easy to run out of replication slots, resulting in an error such as “All replication slots are in use” when deploying. To resolve this, delete inactive replication slots by running this query:
select slot_name, pg_drop_replication_slot(slot_name) from pg_replication_slots where active = false;
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Locate the connection details from RDS:
    • Copy the “Endpoint” value.
    • Paste the endpoint into the “Host” field.
    • Complete the remaining fields: “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” and “SSL Mode” are required. You can paste a connection string into the “URI” field to simplify this.
    • “Name” can be any name for the connection.
    • “Port” is 5432 for Postgres databases.
    • “Username” and “Password” maps to the powersync_role created in Source Database Setup.
    • PowerSync has the AWS RDS CA certificate pre-configured — verify-full SSL mode can be used directly, without any additional configuration required.
  4. Click Test Connection and fix any errors.
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.

​
Troubleshooting

If you get an error such as “IPs in this range are not supported”, the instance is likely not configured to be publicly accessible. A DNS lookup on the host should give a public IP, and not for example 10.x.x.x or 172.31.x.x.
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Fill in your connection details from Azure.
    1. “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” and “SSL Mode” are required. You can also paste a connection string into the “URI” field to simplify data entry.
    2. “Name” can be any name for the connection.
    3. “Port” is 5432 for Postgres databases.
    4. “Username” and “Password” maps to the powersync_role created in Source Database Setup.
    5. PowerSync has the Azure CA certificate pre-configured — verify-full SSL mode can be used directly, without any additional configuration required.
  4. Click Test Connection and fix any errors.
    • If you encounter the error "must be superuser or replication role to start walsender", ensure that you’ve followed all the steps for enabling logical replication documented here.
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Fill in your connection details from Google Cloud SQL.
    • “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” and “SSL Mode” are required. You can paste a connection string into the “URI” field to simplify data entry.
    • “Name” can be any name for the connection.
    • “Port” is 5432 for Postgres databases.
    • “Username” and “Password” maps to the powersync_role created in Source Database Setup.
    • The server certificate can be downloaded from Google Cloud SQL.
    • If SSL is enforced, a client certificate and key must also be created on Google Cloud SQL, and configured on the PowerSync instance.
  4. Click Test Connection and fix any errors.
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Fill in your connection details from Neon.
    1. “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” and “SSL Mode” are required. You can paste a connection string into the “URI” field to simplify data entry.
    2. “Name” can be any name for the connection.
    3. “Port” is 5432 for Postgres databases.
    4. “Username” and “Password” maps to the powersync_role created in Source Database Setup.
    5. Note that if you’re using a self-signed SSL certificate for your database server, click the “Download Certificate” button to dynamically fetch the recommended certificate directly from your server.
    6. Also note if you get any error such as server certificate not trusted: SELF_SIGNED_CERT_IN_CHAIN, click “Download Certificate” to attempt automatic resolution.
  4. Click Test Connection and fix any errors.
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Fill in your connection details from Fly Postgres.
    1. “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” and “SSL Mode” are required. You can paste a connection string into the “URI” field to simplify data entry.
    2. “Name” can be any name for the connection.
    3. “Port” is 5432 for Postgres databases.
    4. “Username” and “Password” maps to the powersync_role created in Source Database Setup.
    5. Note that if you’re using a self-signed SSL certificate for your database server, click the “Download Certificate” button to dynamically fetch the recommended certificate directly from your server.
    6. Also note if you get any error such as server certificate not trusted: SELF_SIGNED_CERT_IN_CHAIN, click “Download Certificate” to attempt automatic resolution.
  4. Click Test Connection and fix any errors.
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Head to your PlanetScale database dashboard page at https://app.planetscale.com/<ORGANIZATION>/<DATABASE_NAME> and click on the “Connect” button to get your database connection parameters.
    1. In the PowerSync dashboard, “Name”, “Host”, “Port”, “Database name”, “Username” and “Password” are required.
    2. “Name” can be any name for the connection.
    3. “Host” is the host connection parameter for your database.
    4. “Port” is 5432 for Postgres databases.
    5. “Username” and “Password” maps to the powersync_role created in Source Database Setup.
      1. Important: PlanetScale requires your branch ID to be appended to your username. The username should be powersync_role.<branch_id>. Your PlanetScale branch ID can be found on the same connection details page.
    6. SSL Mode can remain the default verify-full.
  4. Click Test Connection and fix any errors.
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
For other providers and self-hosted databases:
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “Postgres” tab is selected.
  3. Fill in your connection details.
  4. “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” and “SSL Mode” are required. You can paste a connection string into the “URI” field to simplify data entry.
  5. “Name” can be any name for the connection.
  6. “Port” is 5432 for Postgres databases.
  7. “Username” and “Password” maps to the powersync_role created in Source Database Setup.
  8. Note that if you’re using a self-signed SSL certificate for your database server, click the “Download Certificate” button to dynamically fetch the recommended certificate directly from your server.
  9. Also note if you get any error such as server certificate not trusted: SELF_SIGNED_CERT_IN_CHAIN, click “Download Certificate” to attempt automatic resolution.
  10. Click Test Connection and fix any errors.
  11. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.

​
MongoDB Specifics

  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “MongoDB” tab is selected.
  3. Fill in your connection details from MongoDB:
    1. Copy your cluster’s connection string and paste it into the PowerSync instance URI field. PowerSync will automatically parse this URI to populate other connection details.
      • The format should be mongodb+srv://[username:password@]host/[database]. For example, mongodb+srv://admin:<db_password>@cluster0.abcde1.mongodb.net/powersync
    2. Enter your database user’s password into the Password field. See the necessary permissions in Source Database Setup.
    3. “Database name” is the database in your cluster to replicate.
  4. Click Test Connection and fix any errors. If have any issues connecting, reach out to our support engineers on our Discord server or otherwise contact us.
    1. Make sure that your database allows access to PowerSync’s IPs — see Security and IP Filtering
  5. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete. Also see:

​
MySQL (Beta) Specifics

Select your MySQL hosting provider for steps to connect your newly-created PowerSync instance to your MySQL database:
To enable binary logging and GTID replication in AWS Aurora, you need to create a DB Parameter Group and configure it with the necessary parameters. Follow these steps:
  1. Navigate to Amazon RDS console In the navigation pane, choose Parameter groups and click on Create Parameter Group.
  2. Add all the required binlog configuration parameters. For example:
  3. Associate your newly created parameter group with your Aurora cluster:
    1. In the navigation pane, choose Databases.
    2. Select your Aurora cluster.
    3. Choose Modify.
    4. In the DB Parameter Group section, select the parameter group you created.
    5. Click Continue and then Apply immediately.
  4. Whitelist PowerSync’s IPs in your Aurora cluster’s security group to allow access. See Security and IP Filtering for more details.
  5. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  6. Click Connect to Source Database and ensure the “MySQL” tab is selected.
  7. Fill in your MySQL connection details from AWS Aurora:
    1. “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” are required.
    2. “Name” can be any name for the connection.
    3. “Host” is the endpoint for your Aurora cluster.
    4. “Database name” is the default database to replicate.
    5. “Username” and “Password” maps to your database user.
  8. Click Test Connection and fix any errors.
  9. Click Save Connection.
PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
For other providers and self-hosted databases:
  1. In the PowerSync Dashboard, select your project and instance and go to the Database Connections view.
  2. Click Connect to Source Database and ensure the “MySQL” tab is selected.
  3. Fill in your MySQL connection details:
    1. “Name”, “Host”, “Port”, “Database name”, “Username”, “Password” are required.
    2. “Name” can be any name for the connection.
    3. “Host” the endpoint for your database.
    4. “Database name” is the default database to replicate. Additional databases are derived by qualifying the tables in the Sync Rules.
    5. “Username” and “Password” maps to your database user.
  4. Click Test Connection and fix any errors.
  5. Click Save Connection. PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
Make sure that your MySQL database allows access to PowerSync’s IPs — see Security and IP Filtering