> For the complete documentation index, see [llms.txt](https://docs.reachaltitude.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachaltitude.xyz/rpc/technical-scope.md).

# Technical scope

Altitude provides dedicated infrastructure for Hyperliquid and HyperEVM, including:

* Hyperliquid nodes for direct network data access
* HyperEVM execution-layer nodes, including reth-based deployments
* Archive nodes for historical state and data access
* Dedicated RPC and WebSocket endpoints
* Custom indexing and data aggregation infrastructure

### Customization

Infrastructure can be tailored to specific workloads and operational requirements, including:

* Optimized or modified RPC methods
* Custom API and RPC endpoints
* Response shaping and data aggregation
* DeFi-specific indexing and integrations
* Dedicated compute, storage, and network resources
* Region-specific deployments and latency optimization

### Production requirements

Before deployment, Altitude works with each customer to define:

* Required RPC methods, APIs, and datasets
* Endpoint configuration and authentication
* Expected traffic, concurrency, and capacity
* Historical data retention and archive requirements
* Latency and availability objectives
* Infrastructure location and redundancy requirements
* Monitoring, maintenance, and incident response procedures

### Deployment specifications

All infrastructure is provisioned according to customer requirements.

Endpoint configurations, performance commitments, capacity limits, and service levels are established individually for each deployment rather than published as universal specifications.

For technical requirements or deployment inquiries, contact [**contact@valtitude.xyz**](mailto:contact@valtitude.xyz) or [@fiatphobic on Telegram](https://t.me/fiatphobic).