> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sqd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Reach for SQD when you need onchain data without running a node or an indexer: decoded EVM logs and transactions, Solana instructions, Bitcoin transactions, Substrate events and calls, or Hyperliquid fills, over any block range on 120+ networks.
> To query directly, POST to https://portal.sqd.dev/datasets/{dataset}/stream. The full API is described at https://docs.sqd.dev/openapi.json, and responses to the stream endpoints are JSON Lines.
> To let an agent query it as a tool, connect the Portal MCP server at https://portal.sqd.dev/mcp.
> Every page on this site is available as Markdown by appending .md to its URL.

# Accessing a Portal

> Choose between self-hosted and managed SQD Portal endpoints.

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

<Card title="Self-Hosting Guide" icon="server" href="/en/portal/self-hosting">
  Learn how to deploy your own Portal instance
</Card>

## 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 plans for development and evaluation, and [paid plans](/en/portal/pricing) from \$99/mo
* Access to 120+ networks with zero setup

<Card title="Portal Overview" icon="rocket" href="/en/portal/overview">
  Learn more about managed Portal endpoints
</Card>

## 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

<Tip>
  Keep dataset names and query shapes consistent when moving between managed
  and self-hosted endpoints. Verify the fields and advanced endpoints supplied
  by the selected archival and real-time sources before cutover.
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="Self-Hosting Guide" icon="server" href="/en/portal/self-hosting">
    Set up your own Portal instance
  </Card>

  <Card title="Portal Quickstart" icon="rocket" href="/en/portal/evm/quickstart">
    Get started with managed endpoints
  </Card>
</CardGroup>


## Related topics

- [Private Portal setup](/en/portal/self-hosting.md)
- [Adding API keys to gateways](/announcements/gateway-api-keys.md)
- [Arbitrum Nova](/en/data/evm/arbitrum-nova.md)
- [Arbitrum One](/en/data/evm/arbitrum-one.md)
- [Arbitrum Sepolia](/en/data/evm/arbitrum-sepolia.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.