# Hosted cloud

> Source: https://docs.erpc.cloud/deployment/cloud
> Managed eRPC instances with regional cache storage — no infrastructure setup required.
> Format: machine-readable markdown export of the docs page above.
> All collapsible AI sections are inlined and fully expanded.

# Hosted cloud

Skip the infrastructure work and get a fully managed eRPC instance with cache storage in your preferred region. Compute and storage are provisioned in minutes; you own the config and we handle the rest.

Available regions include EU (close to AWS `eu-central-1` / Hetzner EU) and US (close to AWS `us-east-1` / Hetzner US).

## Pricing

| Feature | Unit cost / month |
|---|---|
| Compute instance | $50 per 2 vCPU + 4 GB RAM |
| Cache data storage | $0.30 per 1 GB |

**Example:** a LiFi project on Arbitrum caching 10 M transactions and traces plus 200 M blocks uses ~400 GB of storage:

- 1 instance: $50 / mo
- 400 GB cache: $120 / mo
- **Total: ~$170 / mo**

[Contact us on Telegram](https://t.me/erpc_cloud) to bring up a cloud instance in minutes.

## Agent reference

Copy one of these prompts into your AI agent session (Claude Code, Cursor, …) — each one
points the agent at this page's machine-readable reference so it can do the work correctly:

**Prompt Example #1: configure eRPC on a hosted cloud instance**

```text
I have a managed eRPC cloud instance (erpc.cloud) and want to configure it correctly.
The config schema is the same as self-hosted — help me write or review my eRPC config
for my use case. For deployment details follow the child-page references:
https://docs.erpc.cloud/deployment/docker.llms.txt and
https://docs.erpc.cloud/deployment/kubernetes.llms.txt. Cloud page:
https://docs.erpc.cloud/deployment/cloud.llms.txt
```

**Prompt Example #2: estimate cloud cost for my caching workload**

```text
Help me estimate the monthly cost of a hosted eRPC cloud instance for my workload:
I need to cache RPC responses for a high-traffic dApp and want to understand the
compute and storage pricing. Then help me write an eRPC config that minimises storage
use for my specific chains. Work with my existing eRPC config. Reference:
https://docs.erpc.cloud/deployment/cloud.llms.txt
```

**Prompt Example #3: harden config before going to production on cloud**

```text
I am about to point production traffic at my hosted eRPC cloud instance. Review
my eRPC config and apply the production hardening checklist — auth, rate limits, CORS,
GOMEMLIMIT guidance, and any footguns in my current config. Start from this page's
reference at https://docs.erpc.cloud/deployment/cloud.llms.txt, then follow the
production checklist at https://docs.erpc.cloud/operation/production.llms.txt.
Work with my existing eRPC config.
```

---

### Hosted cloud — agent notes

This page describes the commercial managed offering, not the open-source
software. For self-hosted deployment details see:

- [Docker](/deployment/docker.llms.txt) — image, compose, flags.
- [Kubernetes](/deployment/kubernetes.llms.txt) — manifests, probes, resources.
- [Production checklist](/operation/production.llms.txt) — hardening grounded in code behavior.

Configuration on hosted instances uses the same `erpc.yaml` / `erpc.ts` schema
documented across this site; nothing in the config surface is cloud-specific.

---


## Navigation (machine-readable surface)

- Up: [All pages index](https://docs.erpc.cloud/llms.txt)
- Root index of every page: [llms.txt](https://docs.erpc.cloud/llms.txt) · everything in one file: [llms-full.txt](https://docs.erpc.cloud/llms-full.txt)

### Sibling pages

- [Docker](https://docs.erpc.cloud/deployment/docker.llms.txt) — A 30 MB distroless image, one mount, two ports — eRPC runs anywhere Docker runs, with a pre-wired Grafana dashboard ready the moment you start.
- [Kubernetes](https://docs.erpc.cloud/deployment/kubernetes.llms.txt) — Stateless by design — scale eRPC to any replica count, roll restarts without dropping requests, and wire Prometheus scraping in one manifest apply.
- [Railway](https://docs.erpc.cloud/deployment/railway.llms.txt) — From zero to a running eRPC proxy with Grafana monitoring in one click — no infra to manage, public endpoints ready immediately.