Accessing a Portal

When building data pipelines with Portal, you have two options for accessing Portal endpoints:

​

Option 1: Self-Hosted Portal

Run your own Portal instance for complete control over your data access infrastructure. Best for:

• Private or custom networks
• Teams with strict data sovereignty requirements
• Maximum control over infrastructure
• Teams prepared to operate RPC, storage, and Portal services

Key benefits:

• Complete control over data access
• Capacity controlled by your own infrastructure and SQD Network allocation
• SQD Network history plus real-time data from compatible self-hosted services
• Real-time-only support for custom EVM networks
• Open-source implementation you can audit and modify

​

Option 2: Managed Portal

Use SQD-hosted Portal endpoints for instant access without infrastructure management. Best for:

• Getting started quickly
• Production apps without infrastructure overhead
• Teams who want to focus on building rather than operations

Key benefits:

• Instant access, no infrastructure to manage
• Production-ready with high availability
• Free tier available for development
• Access to 200+ networks with zero setup

​

Choosing the Right Option

Both options use the Portal API interface for supported operations. The decision depends on your data sources and operational requirements:

• Choose self-hosted if you need control over RPC providers, retention, custom EVM networks, or data-access infrastructure
• Choose managed if you want to get started quickly, prefer not to manage infrastructure, or need production-ready endpoints immediately

​

Next Steps