---
# System prepended metadata

title: L2 Cloud Providers

---

## Zeeve

[Zeeve](app.zeeve.io) provides a Polygon CDK (validium), Parachains (polkadot) and support hosted subgraphs. Moreover, you can launch a uniswap DEX on your own chain.

### L2 setup
- Polygon CDK Validium
- Polkadot Parachains
- Avalanche
- Binance chain

### RPC support

![image](https://hackmd.io/_uploads/B1MzVyXDa.png)

### Mainnet support

### Pricing

Standard plan:

![image](https://hackmd.io/_uploads/BJ9yXy7vp.png)

But also it offer running other nodes with other options.

## Presto 

[Gateway presto](Presto.gateway.fm) provides a containerized version of **Polygon CDK** (more details about the repos can be found below) as a part of the supernets strategy that Polygon is trying to promote.

### L2 Setup
Presto offers multiple setups for the L2 blockchain:

- Rollups (zkEVM node)
- Validiums (zkEVM node + off-chain data availability)

It also offers a bridge, RPC services, block explorer (mainly blockscout) and a full support for the development toolings such Hardhat, web3, ethers.js, ThirdWeb.

### Pricing

- Free trial — live 🟢 — available at presto.gateway.fm
- Paid plans — in development 🚧
- Enterprise customers — live 🟢 — [How to Become an Enterprise Customer?](https://www.notion.so/How-to-Become-an-Enterprise-Customer-399550f40c1f4dfc9f8e11263f7c246f?pvs=21) and [Enterprise vs Paid — what is the difference?](https://www.notion.so/Enterprise-vs-Paid-what-is-the-difference-eea20637f5334261a600f2fcbe8c778f?pvs=21)



## More technical details:

#### Rollup vs Validium

|        | Rollup                                                    | Validium                                                                           |
| ------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Node type**            | [zkEVM node](https://github.com/0xPolygonHermez/zkevm-node) | [Validium node](https://github.com/0xPolygon/cdk-validium-node): zkEVM node with validium extensions                  |
| **Data availability**    | On-chain via L1                                            | Off-chain via a local option, or a [DAC](../concepts/dac.md) + [DA node](https://github.com/0xPolygon/cdk-data-availability) |
| **Components**           | zkEVM components\*                                        | zkEVM components\* + PostgreSQL database + on-chain committees                   |
| **Contracts** | [zkEVM smart contracts](https://github.com/0xPolygonHermez/zkevm-contracts)  <ul><li>`PolygonZkEVM` (main rollup contract)</li> <li> `PolygonZkEVMBridge`</li> <li>`PolygonZkEVMGlobalExitRoot`</li></ul>  | [Validium-specific DAC contract](https://github.com/0xPolygon/cdk-validium-contracts) <ul><li>`CDKDataCommittee.sol`</li><li> `CDKValidium.sol` </li></ul> |
| **Infrastructure** | Standard infrastructure                                     | Dedicated infrastructure for data availability layer and DACs                      |
| **Tx flow** | All transaction data is published on L1 | Validium only publishes the hash of the transaction data to L1. The sequencer sends both the hash and the transaction data to the DAC for verification. Once approved, the hash+signatures are sent to the Consensus L1 contract of the validium protocol.
| **Security** | High security due to on-chain data availability and zero-knowledge proofs. |Off-chain data availability can affect security if the sequencer goes offline or if DAC members collude to withhold state data. |
| **Gas fees** | High, because all transaction data is stored on Ethereum. | Low, because only the hash of the transaction data is stored on Ethereum. |
| **Proof generation** | Uses Prover to generate proofs of batched transactions for validation. | Uses Prover to generate proofs of batched transactions for validation. |
| **Final settlement** | Transaction batches and their corresponding proofs are added to the Ethereum state. | The hash of transaction data and its proof are added to the Ethereum state, referred to as the consolidated state. |



#### Polygon CDK  Repos.


| Component                                                                     | Description                                                          |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [CDK validium node](https://github.com/0xPolygon/cdk-validium-node)           | Node implementation for the CDK networks in Validium mode            |
| [CDK validium contracts](https://github.com/0xPolygon/cdk-validium-contracts) | Smart contracts implementation for the CDK networks in Validium mode |
| [CDK data availability layer](https://github.com/0xPolygon/cdk-data-availability)   | Data availability nodes implementation for the CDK networks          |
| [Prover/Executor](https://github.com/0xPolygonHermez/zkevm-prover)          | zkEVM engine and prover implementation                               |
| [Bridge service](https://github.com/0xPolygonHermez/zkevm-bridge-service)     | Bridge service implementation for CDK networks                       |
| [Bridge UI](https://github.com/0xPolygonHermez/zkevm-bridge-ui)               | UI for the CDK networks bridge                                       |