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

# Welcome to Neon Cloud

Neon Cloud is a powerful cloud infrastructure platform designed for developers and businesses who need reliable, scalable computing resources without the complexity.

## What is Neon Cloud?

Neon Cloud provides:

* **Virtual Machines** - Deploy Linux and Windows servers in seconds
* **Block Storage** - High-performance NVMe SSD storage for your data
* **Networking** - Build secure, isolated networks with load balancing
* **1-Click Apps** - Deploy popular applications instantly
* **Data Protection** - Automated backups and snapshots

## Why Choose Neon Cloud?

### Developer-Friendly

* Simple, intuitive interface
* Powerful API for automation
* Quick deployment times

### Reliable Infrastructure

* 99.95% uptime SLA
* Enterprise-grade hardware
* Multiple data center locations

### Transparent Pricing

* Pay only for what you use
* No hidden fees
* Prepaid credit system

## Getting Help

* **Documentation** - You're here! Browse our guides
* **Support Tickets** - Get help from our team
* **API Docs** - Available at [api.neoncloud.com/api/docs](https://api.neoncloud.com/api/docs/alto#/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neoncloud.com/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.