← Back to Portal Setup
Return to the Portal setup overview to explore other deployment options.
Migrate to the Cloud Portal
For users on EVM and Substrate networks
Portal is currently in beta. Please report any bugs or
suggestions to the SQD Portal Beta chat or
to Squid Devs.
Benefits of migrating to Portal
- Reduced reliance on centralized services: The permissionless SQD Network consists of over 2500 nodes ran by independent operators
- Improved stability: With a total capacity of roughly 2Pb, the permissionless SQD Network provides significant redundancy
- Improved speed: Portals use available bandwidth more effectively than gateways. Data fetching is 5-10 times faster in our tests, resulting in better sync performance for squids not bottlenecked by write operations
- Future-proof: All future development will focus on portals and the permissionless SQD Network.
Available portals
The SQD team operates two independent portals for Cloud users:- Cloud Portal - Only accessible from within the Cloud, ensuring stable performance for deployed squids
- Public Portal - Accessible from anywhere for easy experimentation and local development
We’re currently experimenting with data request complexity limits. If you see an HTTP 400 error with a message like:where
X is above 50, or any other HTTP 400 response, please let us know.Prerequisites
Before you begin, ensure you have:- An existing squid using the open private network gateway
- Access to your squid’s source code
- Node.js and your preferred package manager (npm, yarn, or pnpm) installed
Migration steps
1
Update to latest packages
Portal support requires the latest versions of SQD packages. Follow these steps to upgrade your dependencies.Navigate to your squid’s folder:Remove your lock file and Upgrade all SQD packages to the Install the updated dependencies:
node_modules folder to ensure a clean installation:- NPM
- Yarn
- PNPM
@latest major version:- NPM
- Yarn
- PNPM
Verify that all
@subsquid/* packages in your package.json have been updated to the latest versions.2
Configure your code to use Portal
Update your squid configuration to use the Portal endpoints instead of the gateway.Navigate to the Portal’s page in the Cloud console and select your network to view network-specific configuration instructions.Follow the displayed instructions to update your data source configuration. The changes typically involve:
- Replacing
.setGateway()calls with.setPortal()calls - Using the appropriate Portal endpoint URL for your network
Verify your configuration changes compile without errors by running
npm run build or equivalent.3
Test your migration (recommended)
While you can simply redeploy your squid without re-syncing, we strongly recommend performing a full re-sync during this beta period. This allows you to verify everything works correctly and experience the improved data fetching performance.Follow the zero-downtime update procedure:For detailed instructions on zero-downtime updates, see the slots and tags documentation.
- Deploy your updated squid into a new slot
- Wait for it to complete syncing, monitoring the improved data fetching performance
- Assign your production tag to the new deployment to redirect GraphQL requests
Verify that your GraphQL API returns the same data as before and that your squid syncs successfully to the chain head.