# VPN Service | Cycle.io

Canonical URL: https://cycle.io/docs/platform/vpn-service

## VPN Service.

The VPN service is an optional service that is deployed with every [environment](https://cycle.io/docs/platform/introduction-to-environments), providing a way to join outside computers (such as a development machine) into an environment's private network.

The VPN service is an [OpenVPN](https://cycle.io/learn/what-is-a-vpn#openvpn) container that supports custom user-access controls.

For security purposes, the VPN is **disabled by default**, and must be started manually.

### Access Controls

The VPN service can be configured to allow any account with access to the environment to use their Cycle credentials to log in, utilize custom VPN logins specifically created for this environment, or both.

#### Configure VPN Access Controls

[##### Portal](https://cycle.io/docs/portal/environment-vpn)[##### API](https://cycle.io/docs/api/platform/tag/hubs#tag/servicesvpn/POST/v1/environments/{environmentId}/services/vpn/tasks)

### Connecting to the VPN

The VPN service will generate OpenVPN connection files upon request. This can be accomplished via the portal or API.

### Interacting with Containers Over the VPN

Once an outside computer is connected over the VPN, it can interact with container instances running within the environment just as any other container would.

##### Cycle TLD

To ensure requests are being routed over the VPN into the environment, the [`.cycle` TLD](https://cycle.io/docs/platform/discovery-service#the-cycle-tld) can be appended to force resolution via the discovery service.

```bash
# Assuming the container hostname is `api`, these will both work
curl http://api
curl http://api.cycle
```

Or, for example, if a container is hosting a webserver over port `3000`, it will be accessible via a browser pointed at `http://<hostname>.cycle:3000`

##### VPN Certificate

The certificate generated with the VPN will expire after 1000 days. The portal documentation covers regenerating that certificate if needed:

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
