> ## Documentation Index
> Fetch the complete documentation index at: https://repocloud.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy as VPS

> A container app with a qualifying GitHub link can be deployed as a VPS instead, giving you root access and SSH

## Deploy as VPS Toggle

The **Deploy as VPS with AI system admin agent** switch lets you take a qualifying application from the RepoCloud marketplace and deploy it on its own VPS instead of in a managed container, with an AI agent doing the setup. This gives you the convenience of the catalog combined with the full control of a VPS deployment.

## How It Works

**1. Find an Application**

Browse the [RepoCloud marketplace](https://repocloud.io/results/) and click **Deploy Now** on an application.

**2. Switch On Deploy as VPS**

On the deploy page, leave autoscaling off and look for the **Deploy as VPS with AI system admin agent** switch. It appears only when the application:
- is a container app (not a VPS App, and not an app whose **Deploy Now** button already opens AI Deploy)
- is not one of the apps RepoCloud deploys from a Docker Compose file (their autoscale switch is on and cannot be changed)
- has a link of the form `https://github.com/<owner>/<repo>` in the catalog (a GitLab link does not count)

Platform (full-SSH) apps do not show it either.

**3. Tier Selection Changes**

When the switch is on:
- The $3 Tier 1 is disabled (VPS apps require at least $6/month, Tier 2)
- The tier selection moves to the first eligible VPS tier

**4. Redirect to AI Deploy**

Press **Continue**. You land on the [AI Deploy](https://repocloud.io/docs/deployment/ai-deploy.md) page with the application's GitHub repository URL, your project name, and your tier carried over. RepoCloud provisions the server and the AI agent installs the application.

> [!NOTE]
>
> The switch is only available for applications that have a public GitHub repository linked in the RepoCloud catalog. Applications without a `github.com` link do not show it.

## What Changes with VPS Deployment

When you deploy as VPS instead of a container:

| Aspect | Container (default) | VPS (switch on) |
|---|---|---|
| Server access | Web dashboard only | Full root SSH + browser console |
| Deployment method | One-click container template | AI agent installs from the GitHub source |
| Minimum tier | Tier 1 ($3/mo) where the app offers it | Tier 2 ($6/mo) |
| Autoscaling | Optional (off by default) | Not available |
| Snapshots | Not available | Up to 5 snapshots |
| Dedicated IPv4 | No | Yes, included |
| Updates | One-click Rebuild | Manual: over SSH, or ask the agent in the resumed chat |
| Balance needed to deploy | At least $0.50 | Above $3 |

## Requirements

The same requirements as [AI Deploy](https://repocloud.io/docs/deployment/ai-deploy.md) apply:

- A RepoCloud account with a verified email
- A balance above $3
- The application must have a public GitHub repository

## Use Cases

The switch is useful when you want:

- **Root access** to an application you would normally deploy as a container — for example, to customize system-level configuration, install additional packages, or run background services
- **SSH access** for debugging or development workflows
- **Snapshots** for point-in-time backups before making risky changes
- **Dedicated IPv4** for applications that need direct IP access
- **An AI agent to customize the application** — ask the [DevOps AI Agent](https://repocloud.io/docs/ai-agents/devops-ai-agent.md) to change how the application is set up after it is running

## Next Steps

> **[AI Deploy](https://repocloud.io/docs/deployment/ai-deploy.md)**
>
> Learn more about the AI-powered deployment process

> **[Customizing Applications](https://repocloud.io/docs/ai-agents/customizing-applications.md)**
>
> Recipes for changing an application with the agent

> **[VPS Apps](https://repocloud.io/docs/deployment/vps-apps.md)**
>
> Learn about VPS Apps: dedicated Ubuntu servers set up by the agent or by you

> **[Container Apps](https://repocloud.io/docs/deployment/container-apps.md)**
>
> Learn about the standard container deployment path