# Overview

## Key Features

### **Click-to-Deploy Non-Custodial Staking**

We have designed our product to enable an on-demand staking experience for the deployment of up to 100 Ethereum validators per transaction.

### **Distributed Validator Technology (DVT) Support**

Distributed Validators (DVs) on Ethereum improve decentralization and security by spreading validation responsibilities across multiple independent nodes and can also work across multiple operators. This reduces the risk of single points of failure, slashing penalties, and collusion, while increasing fault tolerance.

Validation Cloud's Ethereum staking user interface and API offers out of the box support for creating Distributed Ethereum Validators (DVs) via [SSV Network](https://ssv.network/dvt/).

We also have extensive experience deploying and maintaining [Obol](https://obol.org/) clusters and associated Distributed Validators.

### **Enterprise-Grade Security**

Our staking platform is audited and penetration tested by third parties from the commission smart contract to the staking API and user interface. The entire platform adheres to the stringent SOC 2 compliance standards set forth by the AICPA.

### **24/7 Availability**

Our dedicated team of experts is available around the clock to assist you with any technical concerns or queries, ensuring a seamless experience with our staking product.

If you would like to get in touch, please reach out to <bd@validationcloud.io>&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.validationcloud.io/staking/staking/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
