Skip to main content
SQD Network portals are currently in closed beta. Please report any bugs or suggestions to the SQD Portal Closed Beta chat or Squid Devs.
This guide walks you through replacing a gateway of the open private version of SQD Network with a portal of the permissionless SQD Network as the primary data source for your Cloud squids.

​
Portal types

The SQD team operates two independent portals that serve the needs of Cloud users:
  • Cloud Portal: Only visible from within the Cloud, ensuring stable performance for squids deployed there
  • Public Portal: Can be accessed from anywhere for easy experimentation and local development
We’re currently experimenting with tightening the data request complexity limits. If you see an HTTP 400 error with a message like this:
Couldn't parse query: query contains X item requests, but only 50 is allowed
where X is some number above 50, or any other HTTP 400 response, please let us know.

​
Migration steps

​
Step 1: Install the portal-api processor

Navigate to your squid’s folder and install the portal-api version of the processor package: 
npm i @subsquid/evm-processor@portal-api

​
Step 2: Configure your data source

Follow the network-specific instructions from the Cloud:
  1. Enable the preview mode
  2. Navigate to the Portal’s page
  3. Click on the tile of your network to see the instructions
Once you’re done, your squid will use the Cloud Portal when deployed and the Public Portal for local runs.

​
Step 3: Re-sync with zero downtime

Evaluate the performance of your new data source by re-syncing your squid. Follow the zero-downtime update procedure:
  1. Deploy your squid into a new slot
  2. Wait for it to sync, observing the improved data fetching
  3. Assign your production tag to the new deployment to redirect the GraphQL requests there
See Slots and Tags for details.