> For the complete documentation index, see [llms.txt](https://doc.cloudbit.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cloudbit.ch/platform/pricing/vpn-and-peering.md).

# VPN & Peering

### How VPN pricing works

The VPN service is charged per Site-to-Site VPN connection. You can run more than one Site-to-Site VPN connection. Charges accrue hourly for as long as the VPN connection exists.

### How Peering pricing works

The Peering service is charged per peering connection (interconnection of two private networks). You can run more than one peering connection. Charges accrue hourly for as long as the VPN connection exists.

### Pricing

| Connection type | Hourly price° | Monthly price°¹ |
| --------------- | ------------- | --------------- |
| VPN             | CHF 0.05      | CHF 40          |
| Peering         | CHF 0.11      | CHF 80          |

### Included

{% hint style="success" %}
**20 TB Outbound Traffic.** Per organization-account 20 TB of outbound traffic per month is included. Inbound and internal traffic is always free.
{% endhint %}

° Prices are in CHF (Swiss franc) and don't include VAT. 1 CHF is usually [equal](https://www.google.com/search?q=1+CHF+in+USD\&cad=h) to 1 USD.\
¹ Monthly price estimates are based on 730 hours of usage.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.cloudbit.ch/platform/pricing/vpn-and-peering.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 `automate deployments from our CI pipeline` 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.