# Introduction to RepoCloud
Source: https://docs.repocloud.io/introduction

Your one-stop destination for deploying, managing, and scaling open-source applications in the cloud

## Welcome to RepoCloud

RepoCloud is an open-source app cloud marketplace where users can deploy their favorite open-source applications with a single click. Our platform features an easy-to-use interface enabling users to manage and deploy their instances without the complexities of traditional server management.

<CardGroup>
  <Card title="Deploy in One Click" icon="rocket" href="/user-guide/one-click-deployment">
    Launch your favorite open-source applications in minutes
  </Card>

  <Card title="Cost-Effective Pricing" icon="money-bill-wave" href="/pricing/overview">
    Pay only for what you use with prices at half of major cloud providers
  </Card>
</CardGroup>

## What Sets Us Apart

At RepoCloud, we believe that powerful technology shouldn't require a PhD in server management. That's why we've created a platform that makes deploying applications as easy as clicking a button.

<CardGroup>
  <Card title="One-Click Updates" icon="arrows-rotate" href="/user-guide/updates">
    Keep your applications secure and up-to-date with a single click
  </Card>

  <Card title="Easy Scaling" icon="chart-line" href="/user-guide/scaling">
    Scale your resources as your needs expand with dynamic autoscaling
  </Card>

  <Card title="270+ Applications" icon="box-archive" href="https://repocloud.io/results">
    Choose from a wide variety of open-source applications for your needs
  </Card>

  <Card title="User-Friendly Interface" icon="display" href="/user-guide/managing-instances">
    Manage your deployments without the need for terminal access
  </Card>
</CardGroup>

## Who Is RepoCloud For?

Our platform is perfect for developers, small businesses, and tech enthusiasts who want the power of self-hosted applications without the operational overhead. We handle the infrastructure, security patches, and scaling, so you can focus on what matters most - using your applications to their full potential.

<CardGroup>
  <Card title="Developers & Teams" icon="code">
    Focus on building your product instead of managing infrastructure
  </Card>

  <Card title="Small Businesses" icon="building">
    Deploy business-critical applications without dedicated IT staff
  </Card>

  <Card title="Tech Enthusiasts" icon="user-gear">
    Easily host your favorite tools without the complexity
  </Card>

  <Card title="Content Creators" icon="podcast">
    Launch platforms for your content without technical headaches
  </Card>
</CardGroup>

Get started today by [creating an account](https://repocloud.io/register) or explore our [quickstart guide](/quickstart) to learn more.


# How RepoCloud Works
Source: https://docs.repocloud.io/platform/how-it-works

Understanding the architecture and workflow of the RepoCloud platform

## Platform Architecture

RepoCloud simplifies the deployment and management of open-source applications through a streamlined architecture designed for performance, reliability, and ease of use.

### Container-Based Deployments

All applications on RepoCloud are deployed as containerized instances, which provides several benefits:

<CardGroup>
  <Card title="Isolation" icon="shield-halved">
    Each application runs in its own isolated environment for enhanced security
  </Card>

  <Card title="Resource Efficiency" icon="leaf">
    Containers share system resources efficiently while maintaining separation
  </Card>

  <Card title="Consistent Environments" icon="clone">
    Applications run in identical environments across development and production
  </Card>

  <Card title="Fast Deployment" icon="bolt">
    Containers can be deployed and scaled in seconds rather than minutes
  </Card>
</CardGroup>

### Managed Infrastructure

RepoCloud handles the underlying infrastructure so you don't have to:

* **Maintained templates**: Application templates are kept up to date, and you apply updates to your instance with a one-click rebuild
* **Resource management**: With autoscaling enabled, CPU, RAM, and storage are allocated dynamically based on your needs
* **High availability**: Infrastructure is designed for redundancy and reliability, with a public [status page](https://status.repocloud.io) tracking all server clusters
* **Network optimization**: 1 Gbps connections with automatic SSL for every application

## Deployment Workflow

<Steps>
  <Step title="Application Selection">
    Browse our catalog of over 270 pre-configured applications and select the one you want to deploy.
  </Step>

  <Step title="Configuration">
    Name your project, choose autoscaling or a fixed server size, and fill in any application-specific settings (such as admin credentials). Most applications have sensible defaults that work out of the box.
  </Step>

  <Step title="Deployment">
    RepoCloud automatically provisions the necessary infrastructure, deploys your application container, and configures networking and storage. Your app receives its own HTTPS URL on an auto-generated subdomain (in the format `https://<your-app-id>.<hosting-domain>`).
  </Step>

  <Step title="Management">
    Once deployed, you can manage your application through our intuitive dashboard: view logs, edit environment variables, add custom domains, track resource usage, rebuild to update, and pause or delete the instance.
  </Step>
</Steps>

## Technical Implementation

Under the hood, RepoCloud uses industry-standard technology to ensure reliable and efficient operations:

* **Docker containers**: Applications are packaged as Docker containers for consistency and portability
* **Orchestration**: We use advanced container orchestration to manage deployments, scaling, and availability
* **Storage solutions**: Persistent data is stored on high-performance NVMe SSD storage
* **Networking layer**: Custom networking stack with automatic SSL certificate management and DNS configuration

<Note>
  While RepoCloud abstracts away most of the technical complexity, users do not have direct terminal access (SSH/CLI) to their instances. This design choice allows us to maintain security, reliability, and simplified management.
</Note>

## Unique Features

### Elastic Hourly Autoscaling

Our elastic hourly autoscaling feature continuously monitors your application's resource usage and automatically adjusts resources as needed:

* Scales up instantly when demand increases
* Scales down when resources aren't needed
* Charges only for the resources you actually use
* Provides significant cost savings compared to fixed-size instances

## Next Steps

<CardGroup>
  <Card title="Technical Details" icon="gears" href="/platform/technical-details">
    Explore detailed technical specifications of the RepoCloud platform
  </Card>

  <Card title="Supported Applications" icon="box-archive" href="https://repocloud.io/results">
    Browse our catalog of 270+ applications available for deployment
  </Card>

  <Card title="Deployment Guide" icon="rocket" href="/user-guide/deployment-basics">
    Learn how to deploy and manage your applications
  </Card>
</CardGroup>


# Technical Details
Source: https://docs.repocloud.io/platform/technical-details

Technical specifications and architecture details of the RepoCloud platform

## Infrastructure Overview

RepoCloud is built on a modern, scalable infrastructure designed to provide reliable and efficient application hosting. Our architecture allows for rapid deployment, seamless scaling, and simplified management of containerized applications.

### Deployment Architecture

<Note>
  RepoCloud uses containerized applications with an orchestration layer, networking stack, storage system, management API, and monitoring system to provide a complete application hosting platform.
</Note>

Our platform is designed with these key components:

* **Container Runtime**: Applications run in isolated Docker containers
* **Orchestration Layer**: Manages container deployment, scaling, and lifecycle
* **Networking Stack**: Handles traffic routing, load balancing, and SSL/TLS termination
* **Storage System**: Provides persistent storage for application data
* **Management API**: Powers the dashboard and enables programmatic control
* **Monitoring System**: Tracks application health and resource usage

## Technical Specifications

### Compute Resources

RepoCloud offers flexible compute resources to accommodate various application needs:

| Tier | RAM   | vCPU | SSD Storage | Price (Monthly) |
| ---- | ----- | ---- | ----------- | --------------- |
| 1    | 1 GB  | 1    | 20 GB       | \$3.00          |
| 2    | 2 GB  | 1    | 30 GB       | \$6.00          |
| 3    | 2 GB  | 2    | 40 GB       | \$9.00          |
| 4    | 4 GB  | 2    | 40 GB       | \$12.00         |
| 5    | 8 GB  | 4    | 80 GB       | \$24.00         |
| 6    | 16 GB | 8    | 160 GB      | \$48.00         |
| 7    | 32 GB | 16   | 320 GB      | \$96.00         |

Additional NVMe SSD storage can be added to any tier at deployment time ("Add Extra SSD") for \$0.10 per GB per month.

All compute resources feature:

* Intel vCPU processors
* NVMe SSD storage
* DDR4 ECC RAM
* 1 Gbps network connectivity

### Networking Capabilities

Our networking infrastructure provides:

* **Automatic SSL**: Free SSL certificates for all applications
* **Custom Domains**: Support for your own domain names
* **DDoS Protection**: Basic protection against common attacks
* **Shared IP**: Applications share IP addresses for efficient resource utilization

<Note>
  RepoCloud uses shared hosting without dedicated IPv4 addresses for regular applications. For workloads requiring dedicated IPs or root access, consider our platform apps like Coolify or Dokploy.
</Note>

### Storage Architecture

Storage on RepoCloud is designed for performance and reliability:

* **Persistent Storage**: Data persists across container restarts and updates
* **Performance Optimization**: NVMe SSDs for high I/O performance
* **Scalability**: Extra SSD storage can be added at deployment time
* **Backups**: RepoCloud does not provide instance-level backups; use your application's built-in backup mechanisms (e.g., exporting n8n workflows as JSON, or WordPress backup plugins) and export data regularly

## Technical Limitations

While RepoCloud offers substantial flexibility, there are some technical limitations to be aware of:

1. **No SSH/Console Access**: Users interact with instances through the GUI only; terminal access is not provided for regular applications
2. **No Dedicated IPv4**: Applications use shared IP addresses by default
3. **Container Restrictions**: Applications run as containers, not VMs, which limits certain types of customization
4. **Resource Limits**: Each tier has defined resource limits that cannot be exceeded without upgrading

For use cases requiring greater control, our [platform apps](/platforms/introduction) (Coolify and Dokploy) provide enhanced capabilities including:

* Dedicated IPv4 addresses
* Full root access
* CI/CD integration
* Heroku/Vercel/Netlify-like interfaces

## Application Updates and Management

RepoCloud ensures your applications stay up-to-date and secure:

* **Automatic Template Updates**: Application templates are regularly updated with the latest stable versions
* **One-Click Rebuilds**: Update your instance to the latest version with the "Rebuild / Update" button
* **Version Pinning**: The "Edit Docker Image" option lets you set a specific image version (tag) for your instance
* **Configuration Persistence**: Application data and configurations persist across updates
* **Environment Variable Management**: Easily modify application settings through environment variables

## Data Management

Each application on RepoCloud has its own mechanisms for data management:

* **Application-Specific Migrations**: For example, WordPress uses plugins for migrations
* **Built-in Backup Tools**: Many applications include their own backup functionality
* **Data Persistence**: Application data is stored in persistent volumes

## Additional Resources

<CardGroup>
  <Card title="Platform Apps" icon="server" href="/platforms/introduction">
    Explore our platform apps for advanced control
  </Card>

  <Card title="Supported Applications" icon="box-archive" href="https://repocloud.io/results">
    Browse our catalog of 270+ applications available for deployment
  </Card>

  <Card title="Pricing Details" icon="money-bill" href="/pricing/overview">
    Learn more about our pricing model
  </Card>

  <Card title="Autoscaling" icon="chart-line" href="/pricing/autoscaling">
    Understand how autoscaling works and can save you money
  </Card>
</CardGroup>


# Coolify
Source: https://docs.repocloud.io/platforms/coolify

Self-hosted Heroku/Netlify alternative on a dedicated VPS with git-push deploys, 280+ templates, managed databases, and automatic SSL

## Coolify on RepoCloud

Coolify is an open-source, self-hosted platform-as-a-service (PaaS) that turns any server into a Heroku-like deployment environment. On RepoCloud, Coolify runs on a dedicated VPS with full root access, SSH, a browser console, and all the management tools in the RepoCloud dashboard.

<CardGroup>
  <Card title="Git-Push Deploys" icon="code-branch">
    Connect GitHub, GitLab, Bitbucket, or Gitea and deploy on every push with automatic builds via Nixpacks, Dockerfile, or Docker Compose
  </Card>

  <Card title="280+ Templates" icon="grid-2">
    One-click deployment for WordPress, n8n, Grafana, Plausible, MinIO, Ghost, and hundreds more
  </Card>

  <Card title="Managed Databases" icon="database">
    Provision PostgreSQL, MySQL, MariaDB, MongoDB, and Redis in a few clicks with backups and monitoring
  </Card>

  <Card title="Automatic SSL" icon="lock">
    Traefik reverse proxy with Let's Encrypt certificates, per-branch preview URLs, and wildcard domain support
  </Card>

  <Card title="Full Root Access" icon="terminal">
    SSH into your server, use the browser console, and manage everything at the OS level
  </Card>

  <Card title="S3 Backups" icon="cloud-arrow-up">
    Automated backups to any S3-compatible storage with one-click restore
  </Card>
</CardGroup>

## Prerequisites

* A RepoCloud account with credit balance (VPS Apps work with free sign-up credit)
* An email address for the Coolify admin account

## Deploying Coolify on RepoCloud

<Steps>
  <Step title="Find Coolify in the Marketplace">
    Go to the RepoCloud marketplace and search for "Coolify". Click on the Coolify VPS listing.
  </Step>

  <Step title="Enter a Project Name">
    Choose a friendly name for your project (e.g., "my-coolify"). This is for your reference in the RepoCloud dashboard.
  </Step>

  <Step title="Enter Your Admin Email">
    Provide the email address you want to use for the Coolify admin account. It defaults to your RepoCloud account email.
  </Step>

  <Step title="Choose Resource Settings">
    Select a tier for your server. Tiers below 2 GB RAM are greyed out because Coolify requires at least 2 GB to install without running out of memory. Servers can be upgraded to a higher tier but not downsized.
  </Step>

  <Step title="Deploy">
    A dedicated IPv4 address is included with every VPS at no extra charge. Click **Deploy Coolify** and wait 5–10 minutes.
  </Step>

  <Step title="Check Your Email">
    Once deployment finishes, you receive an email with:

    * **Dashboard URL** — the HTTPS link to your Coolify dashboard
    * **App Credentials** — admin email and any generated passwords
    * **SSH command** — `ssh root@<your-ip>`
    * **SSH Private Key** — save it to a file, `chmod 600`, and use it to connect
  </Step>
</Steps>

<Note>
  Coolify requires a minimum of 2 GB RAM. If you select a tier with less, the deployment page disables it and shows "Below minimum system requirements for this app."
</Note>

## First-Time Setup

After deployment, open the dashboard URL from your email. Coolify walks you through an onboarding wizard:

<Steps>
  <Step title="Create Your Admin Account">
    On first visit, register with the admin email and a secure password. The first account created becomes the Coolify administrator.
  </Step>

  <Step title="Choose Server Type">
    Select **Quick Start** to use the current server (localhost) for deployments. This is the right choice for most users — the Coolify VPS is both the control plane and the deployment target. Advanced users can choose "Recommended" to connect a separate remote server later.
  </Step>

  <Step title="Configure SSH Authentication">
    Select **Use Existing Key**. Coolify automatically generated an SSH key during installation that it uses to manage the local Docker runtime. No manual key setup is needed.
  </Step>

  <Step title="Create Your First Project">
    Coolify organizes work into projects. Create one (e.g., "My First Project") to group your applications, databases, and services.
  </Step>
</Steps>

<Tip>
  After the wizard, go to **Settings** in the Coolify sidebar and set your **Instance Domain** (e.g., `https://coolify.yourdomain.com`) if you want to access the dashboard through your own domain with automatic SSL.
</Tip>

## Deploying Applications

### From a Git Repository

<Steps>
  <Step title="Create a New Resource">
    In the Coolify dashboard, click **New Resource** and select **Application**.
  </Step>

  <Step title="Connect Your Git Provider">
    Choose GitHub, GitLab, Bitbucket, or Gitea. For GitHub, authorize Coolify via the GitHub App integration. For other providers, add a deploy key or OAuth token.
  </Step>

  <Step title="Select Repository and Branch">
    Pick the repository and branch you want to deploy. Enable "Auto Deploy" to redeploy on every push.
  </Step>

  <Step title="Configure the Build">
    Coolify auto-detects your build system via **Nixpacks** (the default). You can also select a **Dockerfile** or **Docker Compose** build. Set environment variables, build arguments, and resource limits as needed.
  </Step>

  <Step title="Add a Domain">
    Under the **Domains** tab, add a domain or subdomain. Coolify provisions a Let's Encrypt SSL certificate automatically. If you do not have a domain yet, Coolify assigns a port-based URL on your server's IP.
  </Step>

  <Step title="Deploy">
    Click **Deploy**. Watch the build log in real time. Once the build completes, your app is live at the configured domain.
  </Step>
</Steps>

### From a Template

Coolify ships with 280+ pre-configured service templates:

<Steps>
  <Step title="Browse Templates">
    In the Coolify dashboard, click **New Resource** and select **Service**. Browse or search the template catalog.
  </Step>

  <Step title="Select a Template">
    Choose a template (e.g., WordPress, Plausible Analytics, n8n, Uptime Kuma). Each template comes with sensible defaults.
  </Step>

  <Step title="Configure and Deploy">
    Adjust any settings (domain, environment variables, resource limits) and click **Deploy**. Coolify pulls the required images and starts the service.
  </Step>
</Steps>

Popular templates include:

* **CMS**: WordPress, Ghost, Strapi, Directus
* **Analytics**: Plausible, Umami, Matomo
* **Automation**: n8n, Huginn, Activepieces
* **Monitoring**: Uptime Kuma, Grafana, Prometheus
* **Storage**: MinIO, Nextcloud, Seafile
* **Development**: Gitea, Code Server, Coder

## Managing Databases

Coolify can provision and manage databases as first-class resources:

* **PostgreSQL** — with pgAdmin or direct connection strings
* **MySQL / MariaDB** — standalone or as part of a service stack
* **MongoDB** — single node or replica set
* **Redis** — caching, pub/sub, and session storage

For each database, Coolify provides:

* Connection strings and credentials
* Automated backups on a schedule (configure S3-compatible storage under **Settings > Backup**)
* One-click restore from any backup point
* Resource monitoring (CPU, memory, disk usage)

## Custom Domains and SSL

Coolify manages its own domains and SSL certificates through its built-in Traefik reverse proxy. This is separate from the RepoCloud custom domain feature.

**For applications deployed inside Coolify:**

1. Go to the application's **Domains** tab in the Coolify dashboard
2. Add your domain (e.g., `app.yourdomain.com`)
3. Create a DNS **A record** pointing to your VPS IPv4 address
4. Coolify automatically provisions a Let's Encrypt certificate

**For the Coolify dashboard itself:**

1. Go to **Settings** in the Coolify sidebar
2. Set the **Instance Domain** (e.g., `https://coolify.yourdomain.com`)
3. Create a DNS **A record** pointing to your VPS IPv4 address
4. Save — Coolify reconfigures Traefik to serve the dashboard on that domain with SSL

<Warning>
  Do not use the RepoCloud "Custom Domain" feature in the manage page for domains intended for applications running inside Coolify. Use Coolify's own domain management instead, as it controls the Traefik routing rules and certificate issuance.
</Warning>

## RepoCloud Manage Page

Your Coolify VPS has a dedicated manage page in the RepoCloud dashboard with these sections:

<AccordionGroup>
  <Accordion title="Access">
    View your server's default domain (HTTPS link to Coolify dashboard), dedicated IPv4 address, SSH connection command (`ssh root@<ip>`), and app credentials (admin email and generated passwords).
  </Accordion>

  <Accordion title="Power">
    **Power Off** stops the server (data is preserved). **Power On** starts it again. **Reboot** performs a graceful restart. Use these for maintenance or to stop billing on a fixed-tier server.
  </Accordion>

  <Accordion title="Console">
    Opens a browser-based serial console (xterm.js) for emergency access. Useful if SSH is unreachable — for example, after a firewall misconfiguration or a failed system update.
  </Accordion>

  <Accordion title="SSH Keys">
    Lists all registered SSH public keys. RepoCloud auto-generates an Ed25519 key pair at deployment and sends the private key in your email. You can add more keys (e.g., from other machines or team members) and remove old ones.
  </Accordion>

  <Accordion title="Resize">
    Switch between tiers. Upsizing is always available; disk cannot be shrunk after an upgrade (if you need a smaller disk, create a new instance). Changes take effect within a few minutes.
  </Accordion>

  <Accordion title="Snapshots">
    Create up to 5 point-in-time snapshots. Take one before upgrading Coolify or making risky changes so you can roll back. To restore, click **Restore** next to the target snapshot. If newer snapshots exist, a warning lists which ones will be permanently destroyed. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when complete.
  </Accordion>

  <Accordion title="Custom Domain (VPS-level)">
    Point your own domain to the VPS itself by creating an A record to your IPv4 and registering it here. This sets the top-level domain for the server — individual app domains are managed inside Coolify.
  </Accordion>

  <Accordion title="Danger Zone">
    Permanently delete the server, all data, snapshots, and the IPv4 reservation. Requires typing the project name to confirm.
  </Accordion>
</AccordionGroup>

## Upgrading Coolify

Coolify manages its own updates. When a new version is available, a notification appears in the Coolify dashboard sidebar.

<Steps>
  <Step title="Check for Updates">
    In the Coolify dashboard, look for the update notification in the sidebar or go to **Settings > About**.
  </Step>

  <Step title="Create a Snapshot">
    Before upgrading, create a snapshot from the RepoCloud manage page so you can roll back if something goes wrong.
  </Step>

  <Step title="Run the Upgrade">
    Click the update button in the Coolify dashboard. Coolify pulls the new images and restarts its own containers. Your deployed applications are not affected.
  </Step>

  <Step title="Verify">
    After the upgrade, confirm the new version number in **Settings > About** and verify your applications are still running.
  </Step>
</Steps>

<Tip>
  You can also upgrade via SSH by running the official Coolify upgrade command: `curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash`. This is the same script used for initial installation and handles upgrades in-place.
</Tip>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Dashboard not loading after deployment">
    The Coolify dashboard runs on port 8000 behind the VPS's default domain. If the URL from your email does not load, wait a few more minutes — the installation script needs time to pull Docker images and start all services. If it still does not load after 15 minutes, open the browser console from the RepoCloud manage page and check `docker ps` for running containers.
  </Accordion>

  <Accordion title="Out of memory during installation on small tiers">
    Coolify requires at least 2 GB RAM. If you deployed on a tier with less memory (which should not be possible through the UI — tiers below 2 GB are disabled), the install script may fail during `apt-get install` or Docker image pulls. Resize to a 2 GB or larger tier from the manage page.
  </Accordion>

  <Accordion title="Let's Encrypt certificate not issuing">
    Ensure your DNS A record points to the correct IPv4 address (shown in the manage page Access section). Let's Encrypt uses the HTTP-01 challenge on port 80 — the Traefik container must be running and port 80 must not be blocked. Check Coolify's Traefik logs: in the sidebar, go to **Settings > Traefik** and check the log output.
  </Accordion>

  <Accordion title="Cannot SSH into the server">
    Verify you are using the correct IP address and that your SSH key file has `chmod 600` permissions. If SSH hangs or is refused, use the browser console from the RepoCloud manage page to diagnose — check `systemctl status sshd` and `ufw status` from the console.
  </Accordion>

  <Accordion title="Applications fail to build">
    Check the build log in the Coolify dashboard for specific errors. Common causes: missing Dockerfile or unsupported Node.js/Python version for Nixpacks. Ensure your repository has a supported build configuration. You can always switch the build method between Nixpacks, Dockerfile, and Docker Compose.
  </Accordion>
</AccordionGroup>

## Use Cases

Coolify is ideal for:

* **Indie developers and startups** who want Heroku-like convenience without vendor lock-in or per-app pricing
* **Agencies** deploying multiple client sites from Git with automatic SSL and preview environments
* **Teams** that need managed databases alongside their applications with centralized monitoring
* **Self-hosters** migrating from other PaaS providers who want to keep their deployment workflow

## Next Steps

<CardGroup>
  <Card title="Deploy Coolify" icon="rocket" href="https://repocloud.io/details/Coolify%20VPS">
    Launch your Coolify VPS from the RepoCloud marketplace
  </Card>

  <Card title="Coolify Documentation" icon="book" href="https://coolify.io/docs">
    Read the official Coolify documentation for advanced features
  </Card>

  <Card title="Dokploy" icon="docker" href="/platforms/dokploy">
    Explore Dokploy as an alternative Docker-focused deployment platform
  </Card>

  <Card title="VPS Apps Overview" icon="server" href="/platforms/introduction">
    Learn about all VPS Apps and the RepoCloud manage page
  </Card>
</CardGroup>


# Dokploy
Source: https://docs.repocloud.io/platforms/dokploy

Docker-native deployment platform on a dedicated VPS with Nixpacks, Docker Compose, Traefik routing, and one-click databases

## Dokploy on RepoCloud

Dokploy is an open-source, self-hosted PaaS built specifically for Docker container management. On RepoCloud, Dokploy runs on a dedicated VPS with full root access, SSH, a browser console, and all the management tools in the RepoCloud dashboard.

<CardGroup>
  <Card title="Docker-Native" icon="docker">
    Purpose-built for Docker — deploy from Git repos, Docker images, or Docker Compose files with a unified interface
  </Card>

  <Card title="Auto-Detect Builds" icon="wand-magic-sparkles">
    Nixpacks auto-detects your language and dependencies, or use Heroku Buildpacks, Paketo, or a custom Dockerfile
  </Card>

  <Card title="Traefik Routing" icon="route">
    Built-in Traefik reverse proxy handles SSL certificates, domain routing, and load balancing automatically
  </Card>

  <Card title="One-Click Databases" icon="database">
    Provision PostgreSQL, MySQL, MariaDB, MongoDB, and Redis as first-class services alongside your apps
  </Card>

  <Card title="Full Root Access" icon="terminal">
    SSH into your server, use the browser console, and manage everything at the OS level
  </Card>

  <Card title="Docker Swarm" icon="layer-group">
    Built on Docker Swarm for service orchestration with replicas, rolling updates, and health checks
  </Card>
</CardGroup>

## Prerequisites

* A RepoCloud account with credit balance (VPS Apps work with free sign-up credit)
* An email address for the Dokploy admin account

## Deploying Dokploy on RepoCloud

<Steps>
  <Step title="Find Dokploy in the Marketplace">
    Go to the RepoCloud marketplace and search for "Dokploy". Click on the Dokploy VPS listing.
  </Step>

  <Step title="Enter a Project Name">
    Choose a friendly name for your project (e.g., "my-dokploy"). This is for your reference in the RepoCloud dashboard.
  </Step>

  <Step title="Enter Your Admin Email">
    Provide the email address you want to use for the Dokploy admin account. It defaults to your RepoCloud account email.
  </Step>

  <Step title="Choose Resource Settings">
    Select a tier for your server. Tiers below 2 GB RAM are greyed out because Dokploy requires at least 2 GB for Docker Swarm initialization. Servers can be upgraded to a higher tier but not downsized.
  </Step>

  <Step title="Deploy">
    A dedicated IPv4 address is included with every VPS at no extra charge. Click **Deploy Dokploy** and wait 5–10 minutes.
  </Step>

  <Step title="Check Your Email">
    Once deployment finishes, you receive an email with:

    * **Dashboard URL** — the HTTPS link to your Dokploy dashboard
    * **App Credentials** — admin email and generated password
    * **SSH command** — `ssh root@<your-ip>`
    * **SSH Private Key** — save it to a file, `chmod 600`, and use it to connect
  </Step>
</Steps>

<Note>
  Dokploy requires a minimum of 2 GB RAM. Deploying on 1 GB causes out-of-memory errors during Docker Swarm initialization.
</Note>

## First-Time Setup

<Steps>
  <Step title="Open the Dashboard">
    Open the dashboard URL from your deployment email. Dokploy serves its web interface on port 3000, proxied through the VPS's default HTTPS domain.
  </Step>

  <Step title="Create Your Admin Account">
    On first visit, register with your name, email, and a secure password. The first account created becomes the Dokploy administrator.
  </Step>

  <Step title="Configure Your Domain (Optional)">
    For production use, go to **Settings** in the sidebar and set a domain for the Dokploy dashboard itself. Create a DNS A record pointing to your VPS IPv4, then enter the domain in Dokploy. It configures Traefik to serve the dashboard over HTTPS and you can close direct port 3000 access.
  </Step>
</Steps>

<Tip>
  After setup, consider restricting port 3000 to your IP address via `ufw`. All traffic should go through the Traefik HTTPS endpoint (port 443) once a domain is configured.
</Tip>

## Deploying Applications

### From a Git Repository

<Steps>
  <Step title="Create a Project">
    In the Dokploy dashboard, click **Create Project** and give it a name (e.g., "demo-project").
  </Step>

  <Step title="Add an Application">
    Inside the project, click **Create Service** and select **Application**. Name it (e.g., "my-app").
  </Step>

  <Step title="Configure the Source">
    Under the **General** tab, choose your provider (GitHub, GitLab, Bitbucket, or a raw Git URL). Enter the repository URL and branch.
  </Step>

  <Step title="Select Build Type">
    Choose a build method:

    * **Nixpacks** (default) — auto-detects your language and builds without a Dockerfile
    * **Heroku Buildpacks** — compatible with Heroku buildpack configurations
    * **Paketo Buildpacks** — Cloud Foundry buildpacks
    * **Dockerfile** — use a Dockerfile from your repo
  </Step>

  <Step title="Deploy">
    Click **Deploy**. Watch the build progress in the **Deployments** tab and runtime output in **Logs**.
  </Step>
</Steps>

### From a Docker Image

<Steps>
  <Step title="Create a Service">
    Inside a project, click **Create Service** and select **Application**.
  </Step>

  <Step title="Set the Docker Image">
    Under **General**, select **Docker** as the provider type and enter the image name (e.g., `nginx:latest` or `ghcr.io/your-org/your-image:v1.2`).
  </Step>

  <Step title="Configure and Deploy">
    Set environment variables, port mappings, and volumes as needed. Click **Deploy**.
  </Step>
</Steps>

### Docker Compose Stacks

Dokploy has first-class support for Docker Compose:

<Steps>
  <Step title="Create a Compose Service">
    Inside a project, click **Create Service** and select **Compose**.
  </Step>

  <Step title="Add Your Compose File">
    Paste your `docker-compose.yml` content or link a Git repository that contains one.
  </Step>

  <Step title="Configure Domains">
    Assign domains to any services in the stack that need external access. Dokploy configures Traefik labels for routing and SSL.
  </Step>

  <Step title="Deploy the Stack">
    Click **Deploy**. All services in the Compose file are built and started together.
  </Step>
</Steps>

## Managing Databases

Dokploy provisions databases as dedicated services:

<Steps>
  <Step title="Create a Database Service">
    Inside a project, click **Create Service** and select **Database**. Choose from PostgreSQL, MySQL, MariaDB, MongoDB, or Redis.
  </Step>

  <Step title="Configure">
    Set the database name, credentials, and any custom configuration. Dokploy pulls the official image and starts the container.
  </Step>

  <Step title="Connect Your App">
    Use the connection string shown in the database service details. For apps in the same Dokploy project, use the Docker internal hostname (e.g., `db-service:5432`).
  </Step>
</Steps>

Dokploy provides for each database:

* Connection credentials and strings
* Real-time log viewer
* Resource monitoring (CPU, memory, disk)
* Volume-backed persistent storage

## Custom Domains and SSL

Dokploy manages domains and SSL through its built-in Traefik reverse proxy:

**For applications deployed inside Dokploy:**

1. Open the application in the Dokploy dashboard
2. Go to the **Domains** tab
3. Click **Add Domain** and enter your domain (e.g., `app.yourdomain.com`)
4. Enable **HTTPS**
5. Create a DNS **A record** pointing to your VPS IPv4 address
6. Dokploy configures Traefik and provisions a Let's Encrypt certificate automatically

Traefik handles certificate renewal (30 days before expiry). If a certificate fails to issue, check that port 80 is open and DNS has propagated.

<Warning>
  Use Dokploy's own domain management for applications running inside it. The RepoCloud "Custom Domain" in the manage page is for the VPS itself, not for individual apps inside Dokploy.
</Warning>

## RepoCloud Manage Page

Your Dokploy VPS has a dedicated manage page in the RepoCloud dashboard with these sections:

<AccordionGroup>
  <Accordion title="Access">
    View your server's default domain (HTTPS link to Dokploy dashboard), dedicated IPv4 address, SSH connection command, and app credentials.
  </Accordion>

  <Accordion title="Power">
    **Power Off**, **Power On**, and **Reboot** controls. Available once deployment is complete.
  </Accordion>

  <Accordion title="Console">
    Browser-based serial console for emergency access without SSH.
  </Accordion>

  <Accordion title="SSH Keys">
    Manage SSH public keys for root access. An Ed25519 key pair is auto-generated at deployment.
  </Accordion>

  <Accordion title="Resize">
    Switch between tiers. Disk cannot be shrunk after an upgrade.
  </Accordion>

  <Accordion title="Snapshots">
    Create up to 5 point-in-time snapshots. Take one before risky changes. To restore, click **Restore** next to the target snapshot. If newer snapshots exist, a warning lists which ones will be permanently destroyed. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when complete.
  </Accordion>

  <Accordion title="Custom Domain (VPS-level)">
    Point your own domain to the VPS by creating an A record to your IPv4.
  </Accordion>

  <Accordion title="Danger Zone">
    Permanently delete the server and all data.
  </Accordion>
</AccordionGroup>

## Advanced Usage

### Docker Swarm

Dokploy runs on Docker Swarm by default. This gives you:

* **Service replicas** — scale any service to multiple replicas for redundancy
* **Rolling updates** — zero-downtime deployments with configurable update strategies
* **Health checks** — automatic restart of unhealthy containers
* **Service discovery** — containers can reach each other by service name

### Custom Networks

Create isolated Docker networks for groups of services:

* Navigate to **Settings > Docker** in the Dokploy dashboard
* Create custom overlay networks
* Assign services to specific networks for isolation

### Persistent Storage

Dokploy manages Docker volumes for data persistence:

* **Named volumes** are created automatically for databases
* **Bind mounts** can be configured for services that need specific host paths
* All persistent data is stored on the VPS disk and survives container restarts

### Terminal Access

Dokploy provides terminal access at two levels:

* **Host terminal** — access the VPS operating system (also available via SSH or the RepoCloud browser console)
* **Container terminal** — attach to any running container's shell directly from the Dokploy dashboard

## Troubleshooting

<AccordionGroup>
  <Accordion title="Dashboard not loading after deployment">
    Dokploy's dashboard runs on port 3000 behind the VPS's default HTTPS domain. If the URL does not load, wait a few more minutes for all containers to start. If it remains unreachable after 15 minutes, use the browser console from the RepoCloud manage page and run `docker service ls` to check service status.
  </Accordion>

  <Accordion title="Out of memory during Docker Swarm init">
    Dokploy requires at least 2 GB RAM. On 1 GB servers, Docker Swarm initialization fails and SSH may become unresponsive. Resize to 2 GB or larger from the RepoCloud manage page.
  </Accordion>

  <Accordion title="Build fails with Nixpacks">
    Check the build log in the Deployments tab. Common causes: unsupported runtime version, missing `package.json` or `requirements.txt`, or incorrect build command. Switch the build type to Dockerfile if Nixpacks cannot detect your project correctly.
  </Accordion>

  <Accordion title="SSL certificate not provisioning">
    Verify your DNS A record points to the correct IPv4 (check the manage page Access section). Let's Encrypt uses port 80 for the HTTP-01 challenge — ensure it is not blocked. Check the Traefik logs under **Settings > Traefik** in the Dokploy dashboard.
  </Accordion>

  <Accordion title="Cannot SSH into the server">
    Ensure your key file has `chmod 600` permissions and you are connecting as `root`. If SSH is unresponsive, use the browser console from the RepoCloud manage page and check `systemctl status sshd`.
  </Accordion>
</AccordionGroup>

## Use Cases

Dokploy is ideal for:

* **Docker-first teams** who think in containers and Compose files rather than buildpacks
* **Developers** who want Vercel-like Git deploy workflows with full infrastructure control
* **DevOps engineers** who need Docker Swarm orchestration without the complexity of Kubernetes
* **Agencies** deploying multiple client apps on a single server with isolated networks and domains

## Next Steps

<CardGroup>
  <Card title="Deploy Dokploy" icon="rocket" href="https://repocloud.io/details/Dokploy%20VPS">
    Launch your Dokploy VPS from the RepoCloud marketplace
  </Card>

  <Card title="Dokploy Documentation" icon="book" href="https://docs.dokploy.com">
    Read the official Dokploy documentation
  </Card>

  <Card title="Coolify" icon="snowflake" href="/platforms/coolify">
    Explore Coolify as an alternative full-stack PaaS
  </Card>

  <Card title="VPS Apps Overview" icon="server" href="/platforms/introduction">
    Learn about all VPS Apps and the RepoCloud manage page
  </Card>
</CardGroup>


# Hermes Agent
Source: https://docs.repocloud.io/platforms/hermes-agent

Autonomous AI agent from Nous Research on a dedicated VPS with multi-model routing via OpenRouter, a web dashboard, and messaging integrations

## Hermes Agent on RepoCloud

Hermes Agent is an open-source autonomous AI agent from Nous Research that breaks complex goals into sub-tasks, executes them through tool integrations, and handles errors without human supervision. On RepoCloud, Hermes Agent runs on a dedicated VPS with full root access, SSH, a browser console, and all the management tools in the RepoCloud dashboard.

<CardGroup>
  <Card title="Autonomous Execution" icon="robot">
    Define a goal and Hermes plans, executes, observes, and refines until the job is done or it needs your input
  </Card>

  <Card title="400+ Models" icon="brain">
    Route through Claude, GPT, Gemini, and open-source models via OpenRouter — pick the best cost-quality tradeoff for each task
  </Card>

  <Card title="Web Dashboard" icon="display">
    Real-time progress view with step-by-step reasoning, tool calls, and output artifacts in a full TUI and web interface
  </Card>

  <Card title="Messaging Gateway" icon="comments">
    Connect Telegram, Discord, Slack, WhatsApp, and Signal for cross-platform conversation continuity
  </Card>

  <Card title="Memory and Skills" icon="graduation-cap">
    Agent-curated memory with periodic nudges and autonomous skill creation after complex tasks — skills self-improve during use
  </Card>

  <Card title="Full Root Access" icon="terminal">
    SSH into your server, customize the environment, install tools, and manage everything at the OS level
  </Card>
</CardGroup>

## Prerequisites

Before deploying Hermes Agent on RepoCloud, you need an **OpenRouter API key**:

<Steps>
  <Step title="Create an OpenRouter Account">
    Go to [openrouter.ai](https://openrouter.ai) and sign up or log in.
  </Step>

  <Step title="Add Credits">
    Navigate to **Credits** and add funds. OpenRouter charges per token based on the model you use — prices vary from fractions of a cent (open-source models) to a few cents per thousand tokens (frontier models).
  </Step>

  <Step title="Generate an API Key">
    Go to **Keys**, click **Create Key**, and give it a name (e.g., "hermes-agent"). Copy the key — it starts with `sk-or-`.
  </Step>
</Steps>

<Note>
  Hermes Agent uses pay-per-use OpenRouter billing. The API key you provide powers all LLM calls; token costs are billed to your OpenRouter account, separate from your RepoCloud subscription. OpenRouter provides access to 400+ models from 70+ providers with a single key.
</Note>

## Deploying Hermes Agent on RepoCloud

<Steps>
  <Step title="Find Hermes Agent in the Marketplace">
    Go to the RepoCloud marketplace and search for "Hermes Agent". Click on the listing.
  </Step>

  <Step title="Enter a Project Name">
    Choose a friendly name for your project (e.g., "my-hermes").
  </Step>

  <Step title="Enter Your Admin Email">
    Provide the email address for the Hermes admin account.
  </Step>

  <Step title="Enter Your OpenRouter API Key">
    Paste your `sk-or-...` API key. This is stored on the VPS and used by Hermes to authenticate with OpenRouter.
  </Step>

  <Step title="Choose Resource Settings">
    Select a tier for your server. Tiers below 2 GB RAM are greyed out because Hermes Agent requires at least 2 GB. Servers can be upgraded to a higher tier but not downsized.
  </Step>

  <Step title="Deploy">
    A dedicated IPv4 address is included with every VPS at no extra charge. Click **Deploy Hermes Agent** and wait 5–10 minutes.
  </Step>

  <Step title="Check Your Email">
    Once deployment finishes, you receive an email with:

    * **Dashboard URL** — the HTTPS link to your Hermes web interface
    * **App Credentials** — admin password for the web dashboard
    * **SSH command** — `ssh root@<your-ip>`
    * **SSH Private Key** — save it to a file, `chmod 600`, and use it to connect
  </Step>
</Steps>

## First-Time Setup

<Steps>
  <Step title="Open the Web Dashboard">
    Open the dashboard URL from your deployment email. Hermes serves a web interface for browser-based interaction with the agent.
  </Step>

  <Step title="Log In">
    Hermes uses password-based authentication. Use the password from your deployment email (shown in the RepoCloud manage page under **Access > App Credentials**). The login endpoint is `/auth/password-login` — the dashboard redirects you there automatically.
  </Step>

  <Step title="Verify Your Model Connection">
    Once logged in, start a conversation to confirm the OpenRouter API key is working. If the agent responds, your setup is complete.
  </Step>
</Steps>

<Warning>
  Hermes uses a `BasicAuthProvider` — navigate directly to the dashboard URL and use the password login form. If you see an "Internal Server Error" at `/auth/login`, go to `/auth/password-login` instead; the OAuth redirect flow is not supported by the basic auth provider.
</Warning>

## Configuring Models

### Default Configuration

Hermes is deployed with OpenRouter as the default provider. Your API key is stored in `~/.hermes/.env`:

```bash theme={null}
OPENROUTER_API_KEY=sk-or-your-key-here
```

The model configuration lives in `~/.hermes/config.yaml`:

```yaml theme={null}
model:
  provider: openrouter
  default: ~anthropic/claude-sonnet-latest
```

The `~` prefix resolves to the latest version in that model family automatically.

### Switching Models

Change the active model via SSH:

```bash theme={null}
ssh root@<your-ip>
hermes config set model anthropic/claude-opus-4-8
```

Or use the interactive model selector:

```bash theme={null}
hermes model
```

This presents a curated list of agentic models for each provider. The change takes effect immediately for new conversations.

### Popular Model Choices

| Model                             | Best For                                | Context |
| --------------------------------- | --------------------------------------- | ------- |
| `~anthropic/claude-sonnet-latest` | General tasks, balanced speed/quality   | 200K    |
| `~anthropic/claude-opus-latest`   | Complex reasoning, long tasks           | 200K    |
| `~openai/gpt-4o`                  | Fast responses, broad knowledge         | 128K    |
| `openrouter/auto`                 | Automatic model selection by OpenRouter | Varies  |
| `openrouter/pareto-code`          | Cost-optimized coding tasks             | Varies  |

<Note>
  Most agentic configurations require a model with at least 64K context tokens. Smaller context windows may be rejected because the system prompt and tool schemas fill them.
</Note>

### Auxiliary Models

Hermes can offload side tasks (titling, summarization, vision) to cheaper models while using a frontier model for the main agent loop:

```yaml theme={null}
auxiliary:
  title:
    provider: openrouter
    model: google/gemini-2.5-flash
  vision:
    provider: openrouter
    model: google/gemini-2.5-flash
```

Edit `~/.hermes/config.yaml` via SSH to configure auxiliary models.

## Using Hermes Agent

### Starting Conversations

From the web dashboard, type a goal or question. Hermes will:

1. **Plan** — break the goal into sub-tasks
2. **Execute** — run each sub-task using available tools (terminal, file system, web search, APIs)
3. **Observe** — check the results and handle errors
4. **Refine** — adjust the approach based on observations and iterate

The dashboard shows real-time progress with step-by-step reasoning, tool calls, and output artifacts.

### Tool Framework

Hermes has a pluggable tool framework that connects to:

* **Terminal** — run shell commands on the VPS
* **File system** — read, write, and manage files
* **Web search** — search the internet for information
* **APIs** — connect to external services via HTTP
* **Databases** — query and manage data stores

Configure tool access via SSH:

```bash theme={null}
hermes tools
```

### Skills System

Hermes creates reusable skills after completing complex tasks:

* Skills are saved automatically and improve during subsequent use
* Browse and manage skills from the dashboard
* Skills can be shared across sessions and conversations

### Session Management

* Conversations persist across sessions
* Full-text search (FTS5) across session history with LLM summarization
* Use `/session` commands to list, switch, and manage sessions

## Messaging Integrations

Hermes includes a gateway process that connects to messaging platforms. Configure via SSH:

```bash theme={null}
hermes gateway
```

Supported platforms:

* **Telegram** — set a bot token and chat with Hermes via Telegram
* **Discord** — connect a bot to your Discord server
* **Slack** — integrate with a Slack workspace
* **WhatsApp** — connect via the WhatsApp Business API
* **Signal** — secure messaging integration

Each platform maintains conversation continuity — start a conversation in the web dashboard and continue it from Telegram, or vice versa.

<Tip>
  To set up Telegram, create a bot via [@BotFather](https://t.me/BotFather) on Telegram, copy the bot token, and configure it: `hermes config set TELEGRAM_BOT_TOKEN your-token-here`. Then start the gateway: `hermes gateway`.
</Tip>

## RepoCloud Manage Page

Your Hermes Agent VPS has a dedicated manage page in the RepoCloud dashboard:

<AccordionGroup>
  <Accordion title="Access">
    View your server's default domain (HTTPS link to Hermes dashboard), dedicated IPv4 address, SSH connection command, and app credentials (login password).
  </Accordion>

  <Accordion title="Power">
    **Power Off**, **Power On**, and **Reboot** controls.
  </Accordion>

  <Accordion title="Console">
    Browser-based serial console for emergency access.
  </Accordion>

  <Accordion title="SSH Keys">
    Manage SSH public keys for root access.
  </Accordion>

  <Accordion title="Resize">
    Switch between tiers. Disk cannot be shrunk after an upgrade. Hermes benefits from more RAM for complex agent tasks.
  </Accordion>

  <Accordion title="Snapshots">
    Create up to 5 point-in-time snapshots. To restore, click **Restore** next to the target snapshot. If newer snapshots exist, a warning lists which ones will be permanently destroyed. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when complete.
  </Accordion>

  <Accordion title="Custom Domain">
    Point your own domain to the VPS by creating an A record to your IPv4.
  </Accordion>

  <Accordion title="Danger Zone">
    Permanently delete the server and all data.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Internal Server Error at /auth/login">
    Hermes uses a `BasicAuthProvider` that does not support OAuth redirect flows. Navigate to `/auth/password-login` directly, or access the dashboard root URL which should redirect correctly. Use the password from your deployment email.
  </Accordion>

  <Accordion title="Agent not responding or 'No credentials found'">
    SSH into the server and verify the API key: `cat ~/.hermes/.env | grep OPENROUTER`. If missing, re-add it: `hermes config set OPENROUTER_API_KEY sk-or-...`.
  </Accordion>

  <Accordion title="Model rejected due to context length">
    Most agentic setups need 64K+ context. If you chose a model with a smaller window, switch to one with sufficient context: `hermes config set model ~anthropic/claude-sonnet-latest` (200K context).
  </Accordion>

  <Accordion title="High OpenRouter costs">
    Frontier models (Claude Opus, GPT-4o) cost more per token. For routine tasks, use a cheaper model as the default and switch to frontier models only for complex work. Configure auxiliary models for side tasks (titling, summarization) to reduce costs.
  </Accordion>

  <Accordion title="Messaging gateway not connecting">
    Ensure the bot token or API credentials are correct. SSH in and check `hermes gateway status`. Restart with `hermes gateway restart`. Verify that the VPS has outbound internet access to the messaging platform's API endpoints.
  </Accordion>
</AccordionGroup>

## Use Cases

Hermes Agent is ideal for:

* **Developers** who want an autonomous AI assistant on their own infrastructure for research, coding, and task execution
* **Teams** that need a shared AI agent accessible from Slack, Discord, or Telegram
* **Power users** who want to route tasks through different LLM models depending on cost, speed, and quality requirements
* **Automation builders** who need an agent that can execute multi-step workflows involving terminal commands, file manipulation, and API calls

## Next Steps

<CardGroup>
  <Card title="Deploy Hermes Agent" icon="rocket" href="https://repocloud.io/details/Hermes%20Agent">
    Launch your Hermes Agent VPS from the RepoCloud marketplace
  </Card>

  <Card title="Hermes Documentation" icon="book" href="https://hermes-agent.nousresearch.com/docs">
    Read the official Hermes Agent documentation from Nous Research
  </Card>

  <Card title="OpenClaw" icon="code" href="/platforms/openclaw">
    Explore OpenClaw for Claude-powered code generation
  </Card>

  <Card title="VPS Apps Overview" icon="server" href="/platforms/introduction">
    Learn about all VPS Apps and the RepoCloud manage page
  </Card>
</CardGroup>


# VPS Apps Overview
Source: https://docs.repocloud.io/platforms/introduction

Dedicated virtual private servers with root access, SSH, browser console, snapshots, and full server management

## VPS Apps

VPS Apps give you a dedicated virtual private server running the application of your choice. Unlike standard RepoCloud deployments that run in a managed container, a VPS App gives you an entire server with root access, SSH, and a full suite of management tools.

<Note>
  VPS Apps provide dedicated compute, root SSH access, a browser-based serial console, point-in-time snapshots, live resizing, and a dedicated IPv4 address — all managed from the RepoCloud dashboard.
</Note>

## Available VPS Apps

<CardGroup>
  <Card title="Coolify" icon="snowflake" href="/platforms/coolify">
    Self-hosted Heroku/Netlify alternative with git-push deploys, 280+ one-click service templates, managed databases, and automatic SSL
  </Card>

  <Card title="Dokploy" icon="docker" href="/platforms/dokploy">
    Docker-native deployment platform with Nixpacks auto-detection, Docker Compose support, Traefik routing, and one-click databases
  </Card>

  <Card title="OpenClaw" icon="code" href="/platforms/openclaw">
    AI-powered coding platform using Claude models to generate, test, and iterate on code in persistent workspaces
  </Card>

  <Card title="Hermes Agent" icon="robot" href="/platforms/hermes-agent">
    Autonomous AI agent from Nous Research with multi-model routing via OpenRouter, a web dashboard, and messaging integrations
  </Card>

  <Card title="Ubuntu" icon="server" href="/platforms/ubuntu">
    A clean Ubuntu 24.04 LTS server with nothing pre-installed — full root access to build whatever you need
  </Card>
</CardGroup>

## What Makes VPS Apps Different

VPS Apps are fundamentally different from standard RepoCloud applications:

| Feature         | Standard Apps                 | VPS Apps                          |
| --------------- | ----------------------------- | --------------------------------- |
| Infrastructure  | Shared container on EasyPanel | Dedicated virtual private server  |
| Root access     | No                            | Yes (SSH + browser console)       |
| Autoscale       | Yes (default)                 | Not available (fixed tiers only)  |
| Fixed tiers     | Tiers 1–7                     | Tiers 1–7 plus a premium Tier P   |
| SSH access      | No                            | Full root SSH with key management |
| Browser console | No                            | Serial console via xterm.js       |
| Snapshots       | No                            | Up to 5 point-in-time snapshots   |
| Power controls  | Pause only                    | Power off, power on, reboot       |
| Dedicated IPv4  | Included                      | Included                          |
| Custom domains  | CNAME-based                   | A-record to your IPv4             |

## Pricing

VPS Apps use fixed tiers with hourly billing. Select a tier during deployment — each tier specifies the CPU, RAM, and SSD allocation for your server. A dedicated IPv4 address is included with every VPS at no extra charge.

| Tier | vCPU | RAM   | SSD    | Hourly   | Monthly |
| ---- | ---- | ----- | ------ | -------- | ------- |
| 1    | 1    | 1 GB  | 20 GB  | \$0.0042 | \$3     |
| 2    | 1    | 2 GB  | 30 GB  | \$0.0083 | \$6     |
| P    | 2    | 2 GB  | 40 GB  | \$0.0139 | \$10    |
| 3    | 2    | 2 GB  | 40 GB  | \$0.0125 | \$9     |
| 4    | 2    | 4 GB  | 40 GB  | \$0.0167 | \$12    |
| 5    | 4    | 8 GB  | 80 GB  | \$0.0333 | \$24    |
| 6    | 8    | 16 GB | 160 GB | \$0.0667 | \$48    |
| 7    | 16   | 32 GB | 320 GB | \$0.1333 | \$96    |

<Note>
  Every VPS includes a dedicated IPv4 address at no extra charge. Servers can be upgraded to a higher tier but not downsized — resizing to a larger tier permanently increases the disk allocation.
</Note>

### Minimum Requirements

Each app has tested minimum resource requirements. Tiers below the minimum are greyed out on the deployment page:

| App          | Minimum RAM | Minimum vCPU |
| ------------ | ----------- | ------------ |
| Coolify      | 2 GB        | 1            |
| Dokploy      | 2 GB        | 1            |
| OpenClaw     | 2 GB        | 1            |
| Hermes Agent | 2 GB        | 1            |
| Ubuntu       | 1 GB        | 1            |

## Deployment Process

Deploying a VPS App follows a streamlined process:

<Steps>
  <Step title="Find the App">
    Search the RepoCloud marketplace for the app you want (e.g., "Coolify" or "Ubuntu")
  </Step>

  <Step title="Configure Deployment">
    Enter a project name, provide any required inputs (such as an admin email or API key), and select a server tier.
  </Step>

  <Step title="Deploy">
    Click "Deploy" and wait for provisioning to complete (1–2 minutes for Ubuntu, 5–10 minutes for application VPS apps)
  </Step>

  <Step title="Receive Deployment Email">
    You will receive an email with your server's URL (for web apps), app credentials, SSH connection details, and your private key
  </Step>

  <Step title="Manage Your Server">
    Use the RepoCloud dashboard to access your server's manage page with all management tools
  </Step>
</Steps>

## Manage Page

Every VPS instance has a dedicated manage page accessible from the dashboard. It provides these sections:

<AccordionGroup>
  <Accordion title="Access">
    View your server's default domain, IPv4 address, SSH connection command, and app credentials (admin username, password, dashboard URL, etc.)
  </Accordion>

  <Accordion title="Power">
    Power off, power on, or reboot your server. Available once deployment is complete.
  </Accordion>

  <Accordion title="Console">
    Open a browser-based serial console (xterm.js) for emergency access without an SSH client. Useful for recovering from SSH lockouts or diagnosing boot issues.
  </Accordion>

  <Accordion title="SSH Keys">
    View, add, and remove SSH public keys for root access. RepoCloud auto-generates an Ed25519 key pair during deployment and sends the private key in your deployment email.
  </Accordion>

  <Accordion title="Resize">
    Change your server's CPU, RAM, and disk by selecting a different tier. Resizing up is always supported; disk size cannot be reduced after an upgrade.
  </Accordion>

  <Accordion title="Snapshots">
    Create point-in-time snapshots of your server (up to 5). Use them before risky changes so you can roll back with one click. To restore, click **Restore** next to the target snapshot. If newer snapshots exist, a warning lists which ones will be permanently destroyed by the rollback. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when the operation completes.
  </Accordion>

  <Accordion title="Custom Domain">
    Point your own domain to the server by creating a DNS A record to your IPv4 address, then registering it in the dashboard. Requires a dedicated IPv4 address.
  </Accordion>

  <Accordion title="Danger Zone">
    Permanently delete your server, all its data, snapshots, and IPv4 reservation. Requires typing the project name to confirm.
  </Accordion>
</AccordionGroup>

## Legacy Platform Apps

If you deployed Coolify or Dokploy before the VPS system launched, your instance runs on the older EasyPanel-based platform. Those instances continue to work and are managed through the standard RepoCloud manage page (environment variables, Docker image updates, custom domains via CNAME). The VPS manage page features (SSH, console, power controls, snapshots, resize) are only available on new VPS deployments.

## Next Steps

<CardGroup>
  <Card title="Coolify" icon="snowflake" href="/platforms/coolify">
    Deploy a self-hosted PaaS with git-push workflows
  </Card>

  <Card title="Dokploy" icon="docker" href="/platforms/dokploy">
    Deploy a Docker-native container management platform
  </Card>

  <Card title="OpenClaw" icon="code" href="/platforms/openclaw">
    Deploy an AI coding platform powered by Claude
  </Card>

  <Card title="Hermes Agent" icon="robot" href="/platforms/hermes-agent">
    Deploy an autonomous AI agent with 400+ models
  </Card>

  <Card title="Ubuntu" icon="server" href="/platforms/ubuntu">
    Deploy a clean Linux server from scratch
  </Card>
</CardGroup>


# OpenClaw
Source: https://docs.repocloud.io/platforms/openclaw

AI-powered coding platform on a dedicated VPS using Claude models for code generation, testing, and iteration in persistent workspaces

## OpenClaw on RepoCloud

OpenClaw is an open-source AI coding platform that uses Anthropic's Claude models to generate, test, and iterate on software in persistent workspaces. On RepoCloud, OpenClaw runs on a dedicated VPS with full root access, SSH, a browser console, and all the management tools in the RepoCloud dashboard.

<CardGroup>
  <Card title="Claude-Powered" icon="brain">
    Uses Anthropic's Claude models for code generation, testing, debugging, and natural-language-to-code translation
  </Card>

  <Card title="Multi-Provider" icon="plug">
    Supports Anthropic, OpenAI, OpenRouter, and custom endpoints — switch models without code changes
  </Card>

  <Card title="Gateway Architecture" icon="shield-halved">
    A secure gateway manages API credentials, token routing, and provider failover independently from your workspaces
  </Card>

  <Card title="Persistent Workspaces" icon="folder-open">
    Project files survive server reboots and sessions — pick up where you left off at any time
  </Card>

  <Card title="Full Root Access" icon="terminal">
    SSH into your server, install custom toolchains, and manage the entire environment at the OS level
  </Card>

  <Card title="Your Infrastructure" icon="lock">
    All code, prompts, and API keys stay on your own server — nothing leaves unless you push it
  </Card>
</CardGroup>

## Prerequisites

Before deploying OpenClaw on RepoCloud, you need an **Anthropic API key**:

<Steps>
  <Step title="Create an Anthropic Account">
    Go to [console.anthropic.com](https://console.anthropic.com) and sign up or log in.
  </Step>

  <Step title="Add a Payment Method">
    Navigate to **Billing** and add a credit card. New accounts need a payment method before API keys will work.
  </Step>

  <Step title="Generate an API Key">
    Go to **Settings > API Keys**, click **Create Key**, and give it a name (e.g., "openclaw"). Copy the key immediately — it starts with `sk-ant-` and is shown only once.
  </Step>
</Steps>

<Note>
  OpenClaw uses pay-per-use Anthropic billing. The API key you provide powers all Claude calls; token costs are billed to your Anthropic account, separate from your RepoCloud subscription.
</Note>

## Deploying OpenClaw on RepoCloud

<Steps>
  <Step title="Find OpenClaw in the Marketplace">
    Go to the RepoCloud marketplace and search for "OpenClaw". Click on the OpenClaw VPS listing.
  </Step>

  <Step title="Enter a Project Name">
    Choose a friendly name for your project (e.g., "my-openclaw").
  </Step>

  <Step title="Enter Your Admin Email">
    Provide the email address for the OpenClaw admin account.
  </Step>

  <Step title="Enter Your Anthropic API Key">
    Paste your `sk-ant-...` API key. This is stored securely on the VPS and used by the OpenClaw gateway to authenticate with Anthropic's API.
  </Step>

  <Step title="Choose Resource Settings">
    Select a tier for your server. Tiers below 2 GB RAM are greyed out because OpenClaw's installation requires at least 2 GB. Servers can be upgraded to a higher tier but not downsized.
  </Step>

  <Step title="Deploy">
    A dedicated IPv4 address is included with every VPS at no extra charge. Click **Deploy OpenClaw** and wait 5–10 minutes.
  </Step>

  <Step title="Check Your Email">
    Once deployment finishes, you receive an email with:

    * **Dashboard URL** — the HTTPS link to your OpenClaw interface
    * **App Credentials** — gateway token for API access
    * **SSH command** — `ssh root@<your-ip>`
    * **SSH Private Key** — save it to a file, `chmod 600`, and use it to connect
  </Step>
</Steps>

## First-Time Setup

<Steps>
  <Step title="Open the Dashboard">
    Open the dashboard URL from your deployment email. OpenClaw serves a web interface where you can interact with the AI assistant and manage workspaces.
  </Step>

  <Step title="Authenticate">
    Use the gateway token from your deployment email (also visible in the RepoCloud manage page under **Access > App Credentials**) to authenticate.
  </Step>

  <Step title="Verify Your API Connection">
    OpenClaw is pre-configured with the Anthropic API key you provided during deployment. You can verify the connection by starting a conversation — if the model responds, the key is working.
  </Step>
</Steps>

## Configuring AI Models

### Default Configuration

OpenClaw is deployed with Anthropic as the default provider. Your API key is stored in `~/.openclaw/.env` on the server:

```bash theme={null}
ANTHROPIC_API_KEY=sk-ant-your-key-here
```

The default model configuration lives in `~/.openclaw/openclaw.json`:

```json5 theme={null}
{
  "env": { "ANTHROPIC_API_KEY": "sk-ant-..." },
  "agents": {
    "defaults": {
      "model": { "primary": "anthropic/claude-sonnet-4-6" }
    }
  }
}
```

### Adding Additional Providers

You can add more AI providers by SSH-ing into the server and editing the configuration:

**OpenRouter** (access to 400+ models with one key):

```bash theme={null}
ssh root@<your-ip>
openclaw config set OPENROUTER_API_KEY sk-or-your-key-here
```

**OpenAI**:

```bash theme={null}
openclaw config set OPENAI_API_KEY sk-your-key-here
```

### Switching Models

Change the active model at any time:

```bash theme={null}
openclaw config set model anthropic/claude-opus-4-8
```

Or use the interactive model selector:

```bash theme={null}
openclaw model
```

This presents a menu of available providers and their supported models. The change takes effect immediately for new conversations.

## Using OpenClaw

### Code Generation

Start a conversation with a natural-language description of what you want to build. OpenClaw will:

1. **Scaffold the project** — create directory structure, config files, and boilerplate
2. **Write implementation code** — generate functions, classes, and modules based on your description
3. **Create tests** — write unit tests and integration tests alongside the implementation
4. **Iterate on feedback** — refine the code based on your review, error messages, or new requirements

The web interface shows diffs, terminal output, and the file tree in real time as the AI works.

### Working with Existing Code

You can also point OpenClaw at existing projects:

1. Clone your repository onto the VPS via SSH
2. Open the project in OpenClaw
3. Ask the AI to refactor, add features, fix bugs, or write tests for existing code

### Terminal and File Access

OpenClaw has direct access to the server's file system and terminal. It can:

* Run build commands (`npm install`, `pip install`, `cargo build`)
* Execute tests and report results
* Read and modify files across the entire project
* Install system packages via `apt`

## Security Considerations

<Warning>
  Your Anthropic API key is stored on the VPS in `~/.openclaw/.env`. Anyone with SSH access to the server can read it. Manage SSH keys carefully and remove keys for users who should no longer have access.
</Warning>

OpenClaw's security model:

* **API keys stay on your server** — they are never sent to RepoCloud or any third party
* **Code stays on your server** — generated files live in the VPS file system; nothing is uploaded unless you push to a remote Git repository
* **Network isolation** — the gateway process communicates only with the configured AI provider APIs (e.g., `api.anthropic.com`)
* **File permissions** — `~/.openclaw/.env` should be `chmod 600` (this is the default)

To rotate your API key:

```bash theme={null}
ssh root@<your-ip>
openclaw config set ANTHROPIC_API_KEY sk-ant-new-key-here
openclaw gateway restart
```

## RepoCloud Manage Page

Your OpenClaw VPS has a dedicated manage page in the RepoCloud dashboard with these sections:

<AccordionGroup>
  <Accordion title="Access">
    View your server's default domain (HTTPS link to OpenClaw), dedicated IPv4 address, SSH connection command, and app credentials (gateway token).
  </Accordion>

  <Accordion title="Power">
    **Power Off**, **Power On**, and **Reboot** controls.
  </Accordion>

  <Accordion title="Console">
    Browser-based serial console for emergency access.
  </Accordion>

  <Accordion title="SSH Keys">
    Manage SSH public keys for root access.
  </Accordion>

  <Accordion title="Resize">
    Switch between tiers. Disk cannot be shrunk after an upgrade.
  </Accordion>

  <Accordion title="Snapshots">
    Create up to 5 point-in-time snapshots before making changes. To restore, click **Restore** next to the target snapshot. If newer snapshots exist, a warning lists which ones will be permanently destroyed. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when complete.
  </Accordion>

  <Accordion title="Custom Domain">
    Point your own domain to the VPS by creating an A record to your IPv4.
  </Accordion>

  <Accordion title="Danger Zone">
    Permanently delete the server and all data.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="'No credentials found' error">
    The Anthropic API key is not configured or the gateway cannot read it. SSH into the server and check: `cat ~/.openclaw/.env | grep ANTHROPIC`. If the key is missing, re-add it with `openclaw config set ANTHROPIC_API_KEY sk-ant-...` and restart the gateway.
  </Accordion>

  <Accordion title="Model responses are slow or timing out">
    Large prompts or complex code generation tasks can take 30–60 seconds. If responses consistently time out, check your Anthropic account for rate limits or billing issues. You can also try a faster model (e.g., `anthropic/claude-sonnet-4-6` instead of `anthropic/claude-opus-4-8`).
  </Accordion>

  <Accordion title="Installation fails with out-of-memory">
    OpenClaw requires at least 2 GB RAM. The installation process pulls Docker images and compiles dependencies; on 1 GB servers, this causes OOM kills. Resize to 2 GB or larger from the RepoCloud manage page.
  </Accordion>

  <Accordion title="Cannot access the dashboard">
    Wait 10–15 minutes after deployment for the installation to complete. If it remains unreachable, use the browser console from the RepoCloud manage page to check service status. Verify that the gateway process is running.
  </Accordion>

  <Accordion title="API key charges seem high">
    OpenClaw sends your code context to Claude on each interaction. Large codebases increase token usage. Use the Anthropic console to monitor usage and set spend limits. Consider using a smaller model for routine tasks and reserving larger models for complex problems.
  </Accordion>
</AccordionGroup>

## Use Cases

OpenClaw is ideal for:

* **Solo developers** who want an AI pair programmer on their own infrastructure with no data leaving their server
* **Teams** that need a shared AI coding environment with persistent workspaces and centralized API key management
* **Security-conscious organizations** that require all code and prompts to stay on controlled infrastructure
* **Developers exploring AI coding** who want a self-hosted alternative to cloud-based AI editors

## Next Steps

<CardGroup>
  <Card title="Deploy OpenClaw" icon="rocket" href="https://repocloud.io/details/OpenClaw%20VPS">
    Launch your OpenClaw VPS from the RepoCloud marketplace
  </Card>

  <Card title="OpenClaw Documentation" icon="book" href="https://docs.openclaw.ai">
    Read the official OpenClaw documentation
  </Card>

  <Card title="Hermes Agent" icon="robot" href="/platforms/hermes-agent">
    Explore Hermes Agent for autonomous multi-model AI workflows
  </Card>

  <Card title="VPS Apps Overview" icon="server" href="/platforms/introduction">
    Learn about all VPS Apps and the RepoCloud manage page
  </Card>
</CardGroup>


# Ubuntu
Source: https://docs.repocloud.io/platforms/ubuntu

Clean Ubuntu 24.04 LTS server on a dedicated VPS with root SSH access, browser console, snapshots, and live resizing

## Ubuntu on RepoCloud

Ubuntu VPS gives you a clean Ubuntu 24.04 LTS virtual private server with nothing pre-installed — just the operating system and root access. Start from a blank slate and build whatever you need: web servers, databases, development environments, CI runners, monitoring stacks, VPN endpoints, or anything else that runs on Linux.

<CardGroup>
  <Card title="Clean Slate" icon="broom">
    Minimal Ubuntu 24.04 LTS — no bloatware, no opinionated configuration, just the OS and apt package management
  </Card>

  <Card title="Full Root Access" icon="terminal">
    Root SSH access from deployment with an auto-generated Ed25519 key pair sent in your deployment email
  </Card>

  <Card title="10-Year Support" icon="shield-halved">
    Canonical's standard security maintenance for Ubuntu 24.04 LTS covers patches through April 2034
  </Card>

  <Card title="Flexible Pricing" icon="money-bill">
    Start from \$3/month (1 vCPU, 1 GB RAM). Scale up any time. Dedicated IPv4 included with every server.
  </Card>

  <Card title="Snapshots" icon="camera">
    Create point-in-time snapshots before risky changes and roll back with one click
  </Card>

  <Card title="Browser Console" icon="display">
    Serial console access from the RepoCloud dashboard for emergency recovery without SSH
  </Card>
</CardGroup>

## Deploying Ubuntu on RepoCloud

<Steps>
  <Step title="Find Ubuntu in the Marketplace">
    Go to the RepoCloud marketplace and search for "Ubuntu". Click on the Ubuntu VPS listing.
  </Step>

  <Step title="Enter a Project Name">
    Choose a friendly name for your project (e.g., "my-server").
  </Step>

  <Step title="Choose Resource Settings">
    Select a tier for your server. All tiers are available starting from Tier 1 (1 vCPU, 1 GB RAM, \$3/month). A dedicated IPv4 address is included with every VPS at no extra charge. Servers can be upgraded to a higher tier but not downsized.
  </Step>

  <Step title="Deploy">
    Click **Deploy Ubuntu** and wait 1–2 minutes. Ubuntu bare-metal provisioning is faster than application VPS apps because there is no software installation step.
  </Step>

  <Step title="Check Your Email">
    Once deployment finishes, you receive an email with:

    * **SSH command** — `ssh root@<your-ip>`
    * **SSH Private Key** — save it to a file, `chmod 600`, and use it to connect
    * **Manage Instance** button — link to the RepoCloud manage page
  </Step>
</Steps>

<Note>
  Ubuntu VPS does not show a URL on the dashboard because it is a bare server with no web application. Access it exclusively through SSH or the browser console.
</Note>

## Connecting via SSH

### Save Your Private Key

Your deployment email includes an Ed25519 private key. Save it to a file on your local machine:

```bash theme={null}
# Paste the key contents into a file
nano ~/.ssh/repocloud_ubuntu

# Set correct permissions (required — SSH refuses keys with open permissions)
chmod 600 ~/.ssh/repocloud_ubuntu
```

### Connect

```bash theme={null}
ssh -i ~/.ssh/repocloud_ubuntu root@<your-ipv4-address>
```

Your IPv4 address is shown in the RepoCloud manage page under **Access**.

### Add More SSH Keys

You can add additional SSH keys from the RepoCloud manage page (**SSH Keys** section) or directly on the server:

```bash theme={null}
# On the server
cat >> ~/.ssh/authorized_keys << 'EOF'
ssh-ed25519 AAAA... your-other-key
EOF
```

## Initial Server Setup

After connecting via SSH, here is a recommended baseline setup:

### Update Packages

```bash theme={null}
apt update && apt upgrade -y
```

### Configure the Firewall

Ubuntu ships with UFW (Uncomplicated Firewall) available but not enabled:

```bash theme={null}
ufw allow 22/tcp     # SSH
ufw allow 80/tcp     # HTTP (if hosting a website)
ufw allow 443/tcp    # HTTPS (if hosting a website)
ufw enable
```

### Create a Non-Root User (Optional)

```bash theme={null}
adduser deploy
usermod -aG sudo deploy

# Copy SSH authorized keys
mkdir -p /home/deploy/.ssh
cp ~/.ssh/authorized_keys /home/deploy/.ssh/
chown -R deploy:deploy /home/deploy/.ssh
chmod 700 /home/deploy/.ssh
chmod 600 /home/deploy/.ssh/authorized_keys
```

### Set the Timezone

```bash theme={null}
timedatectl set-timezone UTC    # or your preferred timezone
```

### Enable Automatic Security Updates

```bash theme={null}
apt install -y unattended-upgrades
dpkg-reconfigure -plow unattended-upgrades
```

## Common Use Cases

### Web Server (Nginx)

```bash theme={null}
apt install -y nginx
systemctl enable nginx
ufw allow 'Nginx Full'
```

Place your site in `/var/www/html/` or configure virtual hosts in `/etc/nginx/sites-available/`.

For HTTPS, install Certbot:

```bash theme={null}
apt install -y certbot python3-certbot-nginx
certbot --nginx -d yourdomain.com
```

### Database Server (PostgreSQL)

```bash theme={null}
apt install -y postgresql postgresql-contrib
systemctl enable postgresql

# Create a database and user
sudo -u postgres createuser --interactive
sudo -u postgres createdb mydb
```

### Development Environment

```bash theme={null}
# Node.js (via NodeSource)
curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
apt install -y nodejs

# Python
apt install -y python3 python3-pip python3-venv

# Docker
curl -fsSL https://get.docker.com | bash
```

### VPN Endpoint (WireGuard)

```bash theme={null}
apt install -y wireguard
wg genkey | tee /etc/wireguard/privatekey | wg pubkey > /etc/wireguard/publickey
```

Configure `/etc/wireguard/wg0.conf` with your network settings, then:

```bash theme={null}
systemctl enable wg-quick@wg0
systemctl start wg-quick@wg0
```

### CI Runner (GitHub Actions)

```bash theme={null}
# Download the runner
mkdir actions-runner && cd actions-runner
curl -o actions-runner-linux-x64.tar.gz -L \
  https://github.com/actions/runner/releases/latest/download/actions-runner-linux-x64-2.321.0.tar.gz
tar xzf actions-runner-linux-x64.tar.gz

# Configure (use the token from your GitHub repository settings)
./config.sh --url https://github.com/your-org/your-repo --token YOUR_TOKEN
./svc.sh install
./svc.sh start
```

## RepoCloud Manage Page

Your Ubuntu VPS has a dedicated manage page in the RepoCloud dashboard:

<AccordionGroup>
  <Accordion title="Access">
    View your server's IPv4 address and SSH connection command. Ubuntu does not show a clickable URL because there is no web application — use the SSH command directly.
  </Accordion>

  <Accordion title="Power">
    **Power Off** stops the server (data preserved on disk). **Power On** starts it again. **Reboot** performs a graceful restart.
  </Accordion>

  <Accordion title="Console">
    Browser-based serial console for emergency access. Invaluable when SSH is unreachable — for example, after a firewall misconfiguration (`ufw` blocking port 22) or a failed kernel update.
  </Accordion>

  <Accordion title="SSH Keys">
    Lists all registered SSH public keys. Add keys for team members or other machines. Remove old keys when access should be revoked.
  </Accordion>

  <Accordion title="Resize">
    Switch between tiers. All tiers are available (no minimum restriction for Ubuntu). Disk cannot be shrunk after an upgrade — to downsize disk, create a new instance.
  </Accordion>

  <Accordion title="Snapshots">
    Create up to 5 point-in-time snapshots. Best practice: snapshot before upgrading the kernel, changing firewall rules, or any other potentially destructive operation. To restore, click **Restore** next to the target snapshot. If newer snapshots exist, the confirmation dialog lists exactly which ones will be permanently destroyed by the ZFS rollback — the target snapshot itself always survives. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when complete.
  </Accordion>

  <Accordion title="Custom Domain">
    Point your own domain to the server by creating a DNS A record to your dedicated IPv4 address.
  </Accordion>

  <Accordion title="Danger Zone">
    Permanently delete the server, all data, snapshots, and any IPv4 reservation.
  </Accordion>
</AccordionGroup>

## Snapshots and Backup Strategy

Snapshots capture the entire disk state at a point in time. Use them as safety nets:

1. **Before upgrades**: `apt upgrade`, kernel updates, or major configuration changes
2. **Before experiments**: testing new software stacks, network configurations, or security policies
3. **Regular intervals**: create a weekly snapshot and delete old ones (5 max)

### Restoring a Snapshot

Click **Restore** next to the snapshot you want to roll back to. If newer snapshots exist between the target and the current state, a warning lists them — those snapshots will be **permanently destroyed** because ZFS rollback cannot preserve them. The target snapshot itself always survives. The server restarts during the restore operation (typically 10–25 seconds) and the page refreshes automatically when complete.

For off-server backups, consider:

* `rsync` to another server or local machine
* `restic` or `borgbackup` to S3-compatible storage
* Database-specific dump tools (`pg_dump`, `mysqldump`) for database backups

## Resizing

You can change tiers at any time from the manage page — resizing takes a few minutes. Resizing to a larger tier permanently increases the disk allocation; you cannot resize back down to a smaller tier afterward.

### When to Resize

* **CPU-bound workloads** (compilation, encoding): move to a tier with more vCPUs
* **Memory-bound workloads** (databases, caches): move to a tier with more RAM
* **Storage-bound workloads**: note that disk cannot be shrunk after upsizing

## Troubleshooting

<AccordionGroup>
  <Accordion title="Cannot SSH after deployment">
    Verify you saved the private key with `chmod 600`. Ensure you are using the correct IP from the manage page. If all else fails, use the browser console from the manage page.
  </Accordion>

  <Accordion title="Locked out by UFW">
    If you accidentally blocked SSH with a firewall rule, use the browser console from the RepoCloud manage page. The serial console bypasses the network stack entirely. Run `ufw allow 22/tcp` and `ufw reload` to restore SSH access.
  </Accordion>

  <Accordion title="Server unreachable after kernel update">
    A bad kernel update can prevent boot. Use the browser console to access the GRUB menu and select the previous kernel. If that does not work, restore from a snapshot.
  </Accordion>

  <Accordion title="Disk full">
    Check usage with `df -h`. Clean package caches: `apt clean`. Remove old kernels: `apt autoremove`. Check `/var/log` for large log files. If you need more space, resize to a larger tier from the manage page.
  </Accordion>
</AccordionGroup>

## Use Cases

Ubuntu VPS is ideal for:

* **Developers** who need a clean Linux environment for coding, testing, or running dev tools
* **System administrators** setting up custom infrastructure (web servers, databases, monitoring)
* **DevOps engineers** running CI runners, build servers, or deployment pipelines
* **Network engineers** deploying VPN endpoints, DNS servers, or reverse proxies
* **Students and learners** practicing Linux administration in a real cloud environment
* **Anyone** who needs a dedicated Linux server without the opinions of a pre-installed application

## Next Steps

<CardGroup>
  <Card title="Deploy Ubuntu" icon="rocket" href="https://repocloud.io/details/Ubuntu">
    Launch your Ubuntu VPS from the RepoCloud marketplace
  </Card>

  <Card title="Ubuntu Server Guide" icon="book" href="https://ubuntu.com/server/docs">
    Read the official Ubuntu Server documentation from Canonical
  </Card>

  <Card title="Coolify" icon="snowflake" href="/platforms/coolify">
    Deploy a pre-configured PaaS instead of building from scratch
  </Card>

  <Card title="VPS Apps Overview" icon="server" href="/platforms/introduction">
    Learn about all VPS Apps and the RepoCloud manage page
  </Card>
</CardGroup>


# Elastic Autoscaling
Source: https://docs.repocloud.io/pricing/autoscaling

Pay only for the resources you actually use with RepoCloud's dynamic scaling system

## Elastic Hourly Autoscaling

RepoCloud's Elastic Hourly Autoscaling is an intelligent resource management system that automatically adjusts your application's resources based on actual usage, helping you optimize performance while minimizing costs.

## How Autoscaling Works

Traditional cloud hosting requires you to choose a fixed resource tier and pay for those resources 24/7, regardless of actual usage. With RepoCloud's autoscaling:

<Steps>
  <Step title="Real-time Monitoring">
    Our system continuously monitors your application's resource utilization (CPU, RAM, and storage).
  </Step>

  <Step title="Dynamic Resource Allocation">
    When demand increases, additional resources are instantly allocated to maintain performance.
  </Step>

  <Step title="Automatic Optimization">
    During periods of lower activity, resources scale down automatically to reduce costs.
  </Step>

  <Step title="Hourly Billing">
    You're billed hourly based on the actual resources consumed, rather than a fixed monthly amount.
  </Step>
</Steps>

## The Autoscaling Advantage

<CardGroup>
  <Card title="Cost Efficiency" icon="money-bill-wave">
    Pay only for what you use, reducing waste from idle resources
  </Card>

  <Card title="Performance Optimization" icon="gauge-high">
    Automatically handle traffic spikes without manual intervention
  </Card>

  <Card title="Resource Efficiency" icon="leaf">
    Stop paying for idle servers during low-traffic periods
  </Card>

  <Card title="Simplified Management" icon="sliders">
    No need to predict exact resource requirements in advance
  </Card>
</CardGroup>

## Understanding Resource Scaling

RepoCloud's autoscaling works by dynamically adjusting three primary resources:

### CPU Scaling

<AccordionGroup>
  <Accordion title="How CPU Scaling Works">
    * CPU usage is monitored in real-time
    * When CPU utilization exceeds thresholds, additional CPU cores are allocated
    * During low CPU utilization, resources are reduced to the minimum needed
    * Scaling occurs without interruption to your application
  </Accordion>

  <Accordion title="Benefits of CPU Scaling">
    * Handle processing-intensive tasks efficiently
    * Maintain application responsiveness during peak loads
    * Reduce costs during periods of low computational demand
    * Avoid over-provisioning CPU resources
  </Accordion>
</AccordionGroup>

### Memory (RAM) Scaling

<AccordionGroup>
  <Accordion title="How RAM Scaling Works">
    * Memory usage is continuously monitored
    * When RAM utilization approaches capacity, additional memory is allocated
    * When memory needs decrease, allocation is reduced
    * Scaling ensures your application always has sufficient memory without waste
  </Accordion>

  <Accordion title="Benefits of RAM Scaling">
    * Prevent out-of-memory errors during traffic spikes
    * Support memory-intensive operations when needed
    * Optimize costs based on actual memory requirements
    * Scale memory independently from CPU resources
  </Accordion>
</AccordionGroup>

### Storage Scaling

<AccordionGroup>
  <Accordion title="How Storage Scaling Works">
    * Storage usage is monitored
    * Additional storage is automatically allocated as needed
    * You're billed only for the storage you actually use
    * Scaling occurs without application downtime
  </Accordion>

  <Accordion title="Benefits of Storage Scaling">
    * Never run out of disk space unexpectedly
    * Pay only for the storage you utilize
    * Accommodate growing data needs without manual intervention
    * Optimize costs for applications with variable storage requirements
  </Accordion>
</AccordionGroup>

## Real-World Savings Examples

### Example 1: Blog with Variable Traffic

A blog typically receives most of its traffic during business hours and very little overnight:

* **Fixed Tier Approach**: Would require provisioning for peak traffic (4GB RAM, 2vCPU) at \$12/month
* **With Autoscaling**: Average resource usage might be only 1.5GB RAM and 0.8vCPU across 24 hours
* **Resulting Billing**: Approximately \$4.50/month (62.5% savings)

### Example 2: Business Application with Weekend Drop-offs

An internal business application used primarily Monday to Friday:

* **Fixed Tier Approach**: Requires 8GB RAM, 4vCPU at \$24/month
* **With Autoscaling**: Resources scale down by 80% during weekends (28.6% of the month)
* **Resulting Billing**: Approximately \$18.50/month (about 23% savings)

### Example 3: E-commerce with Seasonal Peaks

An e-commerce store with significant traffic during holiday seasons:

* **Fixed Tier Approach**: Would need to provision for peak season (16GB RAM, 8vCPU) at \$48/month year-round
* **With Autoscaling**: Resources might average 4GB RAM, 2vCPU during regular periods
* **Resulting Billing**: Averaged across the year, approximately \$18/month (62.5% savings)

<Tip>
  Applications with highly variable usage patterns typically see the greatest savings from autoscaling, sometimes reaching 70-90% cost reduction compared to fixed-tier pricing.
</Tip>

## Setting Up Autoscaling

Autoscaling is enabled on the deployment page and is switched on by default:

<Steps>
  <Step title="Choose Your Application">
    Select an application from the marketplace and click "Deploy Now"
  </Step>

  <Step title="Enable Autoscaling">
    For managed application deployments, leave the autoscaling option enabled. VPS Platform Apps use fixed tiers only — select a tier that meets the minimum requirements shown on the deploy page.
  </Step>

  <Step title="Deploy">
    Click "Deploy App". Your instance will scale between resource tiers automatically from then on, with no further configuration required.
  </Step>
</Steps>

<Note>
  Once deployed, an autoscaling instance shows "Autoscaling" as its Server Size on the management page. There are no scaling knobs to tune—the platform handles resource adjustments for you.
</Note>

## Monitoring Autoscaling

RepoCloud gives you full visibility into how your instance has been scaling:

<CardGroup>
  <Card title="Usage Chart" icon="chart-line">
    Click "View Usage Chart" on your instance's management page to see which resource tier (from 1 GB RAM / 1 vCPU up to 32 GB RAM / 16 vCPU) your application occupied hour by hour
  </Card>

  <Card title="Usage History" icon="file-csv">
    Download a detailed usage history from the Billing tab to reconcile exactly what you were charged for
  </Card>
</CardGroup>

## Billing with Autoscaling

With autoscaling enabled, your billing works differently from fixed-tier pricing:

1. **Hourly Metering**: Resource usage is measured on an hourly basis
2. **Hourly Rate**: Each hour is billed at the rate of the resource tier your instance used during that hour
3. **Credit Deduction**: Hourly charges are deducted from your prepaid account credit
4. **Baseline Cost**: An instance that runs continuously all month costs at least the Tier 1 rate (\$3.00 per month); pausing an instance reduces billing to 25% of the normal rate

<Note>
  Billing for autoscaled applications is transparent. The usage chart and downloadable usage history show you exactly what you're being charged for.
</Note>

## Autoscaling Limitations

While autoscaling is powerful, there are some limitations to be aware of:

* **VPS Platform Apps**: Autoscaling is not available for [VPS Platform Apps](/platforms/introduction) (Coolify, Dokploy, OpenClaw, Hermes Agent, Ubuntu). These use fixed resource tiers with a dedicated IPv4 address included at no extra charge
* **Resource Constraints**: Some applications may have minimum resource requirements to function properly
* **Scaling Delays**: There may be a brief delay (typically seconds) in responding to sudden, extreme spikes in demand

## When to Choose Fixed Resources

While autoscaling works well for most applications, fixed resources might be better in some scenarios:

<AccordionGroup>
  <Accordion title="Predictable Workloads">
    If your application has very consistent resource needs with minimal variation, a fixed tier might provide more predictable billing.
  </Accordion>

  <Accordion title="Budget Certainty">
    When you need absolute certainty about your monthly costs for budgeting purposes, fixed tiers provide guaranteed pricing.
  </Accordion>

  <Accordion title="Performance Guarantees">
    Applications requiring guaranteed resources at all times, regardless of actual usage, may benefit from fixed allocation.
  </Accordion>

  <Accordion title="Resource-Intensive Applications">
    Applications that consistently use near-maximum resources won't benefit as much from autoscaling.
  </Accordion>
</AccordionGroup>

## Optimizing for Autoscaling

To get the most from autoscaling, consider these best practices:

1. **Monitor Usage Patterns**: Review your instance's usage chart to understand its typical resource footprint
2. **Design for Variability**: Structure your application to efficiently handle variable resources
3. **Pause Idle Instances**: Pause instances you aren't using to reduce their billing to 25% of the normal rate
4. **Test Performance**: Verify that your application performs well at different resource levels

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How quickly does autoscaling respond to traffic spikes?">
    Autoscaling typically responds within seconds to changes in resource needs. For most applications, this is fast enough to handle even sudden traffic spikes without noticeable performance degradation.
  </Accordion>

  <Accordion title="Will my application experience downtime during scaling?">
    Most scaling operations occur without any downtime. In some cases, applications might experience a brief period (seconds) of reduced performance during scaling, but complete downtime is rare.
  </Accordion>

  <Accordion title="How is billing calculated with autoscaling?">
    Resource usage is metered hourly, and each hour is billed at the rate of the tier your instance occupied during that hour. Charges are deducted from your prepaid account credit.
  </Accordion>

  <Accordion title="Can I cap my spending?">
    The hard ceiling for any single instance is the top tier's rate (\$96.00/month equivalent). For strict cost control, deploy with a fixed server size instead of autoscaling—your instance then never bills above that tier's rate. Because billing draws from prepaid credit, spending also can't exceed the credit you've purchased unless Auto Recharge is enabled.
  </Accordion>

  <Accordion title="What happens if my credit balance runs out?">
    Billing is prepaid, so you'll need to keep your balance topped up for instances to keep running. Enable Auto Recharge in the Billing tab to automatically purchase credit whenever your balance drops below a threshold you set.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="Resource Tiers" icon="layer-group" href="/pricing/tiers">
    Explore our fixed resource tier options
  </Card>

  <Card title="Price Comparison" icon="scale-balanced" href="/pricing/comparison">
    Compare RepoCloud pricing with other cloud providers
  </Card>
</CardGroup>


# Price Comparison
Source: https://docs.repocloud.io/pricing/comparison

See how RepoCloud pricing compares to other cloud providers

## Cloud Provider Pricing Comparison

RepoCloud's pricing is designed to be substantially more affordable than major cloud providers while delivering equivalent or superior performance. This page provides a direct comparison between RepoCloud and other popular cloud hosting services.

## Cost Savings Overview

On average, RepoCloud customers save approximately **50% on their cloud infrastructure costs** compared to major providers like AWS, Azure, and Google Cloud, while maintaining enterprise-grade performance and reliability.

<CardGroup>
  <Card title="Up to 93% Savings" icon="money-bill-wave">
    With elastic autoscaling, many customers achieve even higher savings
  </Card>

  <Card title="No Hidden Costs" icon="eye-slash">
    Transparent pricing without complex fee structures
  </Card>

  <Card title="Pay-as-you-Go" icon="wallet">
    No long-term contracts or upfront commitments
  </Card>

  <Card title="Built-in Features" icon="boxes-stacked">
    SSL, custom domains, and monitoring included at no extra cost
  </Card>
</CardGroup>

## Detailed Price Comparison by Tier

### Entry-Level (1GB RAM / 1vCPU)

| Cloud Provider | Plan          | RAM    | vCPU | Monthly Cost | Savings with RepoCloud |
| -------------- | ------------- | ------ | ---- | ------------ | ---------------------- |
| RepoCloud      | Tier 1        | 1 GB   | 1    | \$3.00       | -                      |
| AWS EC2        | t3.micro      | 1 GB   | 2    | \$7.59       | 60%                    |
| Azure          | B1s           | 1 GB   | 1    | \$7.59       | 60%                    |
| DigitalOcean   | Basic 1 GB    | 1 GB   | 1    | \$6.00       | 50%                    |
| Fly.io         | shared-cpu-1x | 1 GB   | 1    | \$5.70       | 47%                    |
| Google Cloud   | e2-micro      | 1 GB   | 0.25 | \$6.11       | 51%                    |
| Linode         | Nanode 1 GB   | 1 GB   | 1    | \$5.00       | 40%                    |
| Railway        | usage-based   | 1 GB   | 1    | \$30.00      | 90%                    |
| Render         | Starter       | 0.5 GB | 0.5  | \$7.00       | 57%                    |
| Replit         | Reserved VM   | 1 GB   | 0.25 | \$6.40       | 53%                    |
| Vultr          | Regular 1 GB  | 1 GB   | 1    | \$5.00       | 40%                    |
| Zeabur         | serverless    | 1 GB   | 1    | \$10.80      | 72%                    |

<Note>
  Competitor prices reflect each provider's cheapest comparable on-demand plan (same RAM, closest vCPU, US region, no commitments), last verified against published vendor pricing in July 2026. Prices may change; please check each provider's official pricing page for the most current information.
</Note>

### Small Business (4GB RAM / 2vCPU)

| Cloud Provider | Plan          | RAM  | vCPU | Monthly Cost | Savings with RepoCloud |
| -------------- | ------------- | ---- | ---- | ------------ | ---------------------- |
| RepoCloud      | Tier 4        | 4 GB | 2    | \$12.00      | -                      |
| AWS EC2        | t3.medium     | 4 GB | 2    | \$30.37      | 60%                    |
| Azure          | B2s           | 4 GB | 2    | \$30.37      | 60%                    |
| DigitalOcean   | Basic 4 GB    | 4 GB | 2    | \$24.00      | 50%                    |
| Fly.io         | shared-cpu-2x | 4 GB | 2    | \$21.40      | 44%                    |
| Google Cloud   | e2-medium     | 4 GB | 1    | \$24.46      | 51%                    |
| Linode         | Linode 4 GB   | 4 GB | 2    | \$24.00      | 50%                    |
| Railway        | usage-based   | 4 GB | 2    | \$80.00      | 85%                    |
| Render         | Pro           | 4 GB | 2    | \$85.00      | 86%                    |
| Replit         | Reserved VM   | 4 GB | 1    | \$25.60      | 53%                    |
| Vultr          | Regular 4 GB  | 4 GB | 2    | \$20.00      | 40%                    |
| Zeabur         | serverless    | 4 GB | 2    | \$43.20      | 72%                    |

<Note>
  Competitor prices reflect each provider's cheapest comparable on-demand plan (same RAM, closest vCPU, US region, no commitments), last verified against published vendor pricing in July 2026. Prices may change; please check each provider's official pricing page for the most current information.
</Note>

### Enterprise (16GB RAM / 8vCPU)

| Cloud Provider | Plan          | RAM   | vCPU | Monthly Cost | Savings with RepoCloud |
| -------------- | ------------- | ----- | ---- | ------------ | ---------------------- |
| RepoCloud      | Tier 6        | 16 GB | 8    | \$48.00      | -                      |
| AWS EC2        | t3.xlarge     | 16 GB | 4    | \$121.47     | 60%                    |
| Azure          | B4ms          | 16 GB | 4    | \$121.18     | 60%                    |
| DigitalOcean   | Basic 16 GB   | 16 GB | 8    | \$96.00      | 50%                    |
| Fly.io         | shared-cpu-8x | 16 GB | 8    | \$85.59      | 44%                    |
| Google Cloud   | e2-standard-4 | 16 GB | 4    | \$97.84      | 51%                    |
| Linode         | Linode 16 GB  | 16 GB | 6    | \$96.00      | 50%                    |
| Railway        | usage-based   | 16 GB | 8    | \$320.00     | 85%                    |
| Render         | Pro Max       | 16 GB | 4    | \$225.00     | 79%                    |
| Replit         | Reserved VM   | 16 GB | 4    | \$211.00     | 77%                    |
| Vultr          | Regular 16 GB | 16 GB | 6    | \$80.00      | 40%                    |
| Zeabur         | serverless    | 16 GB | 8    | \$172.80     | 72%                    |

<Note>
  Competitor prices reflect each provider's cheapest comparable on-demand plan (same RAM, closest vCPU, US region, no commitments), last verified against published vendor pricing in July 2026. Prices may change; please check each provider's official pricing page for the most current information.
</Note>

## Cost Comparison with Autoscaling

While the above tables show fixed-tier comparisons, RepoCloud's elastic autoscaling can provide even greater savings:

## Autoscaling Advantage

With autoscaling, resources adjust automatically based on actual usage, so you only pay for what you need. For applications with variable traffic or usage patterns, this can result in significant cost savings:

* **Example 1**: A blog that receives traffic primarily during business hours might use only 30% of its allocated resources over a 24-hour period, resulting in \~70% cost savings with autoscaling.
* **Example 2**: A business application used mainly on weekdays might see resource usage drop to 10-15% on weekends, resulting in substantial monthly savings.
* **Example 3**: A seasonal e-commerce site might need high resources during peak seasons but minimal resources during off-seasons.

## Additional Cost Considerations

When comparing cloud providers, it's important to consider all costs, not just the base instance price:

### Included Features

RepoCloud includes several features at no additional cost that other providers often charge extra for:

<CardGroup>
  <Card title="SSL Certificates" icon="shield-check">
    Free SSL for all applications
  </Card>

  <Card title="Custom Domains" icon="globe">
    No extra charge for custom domains
  </Card>

  <Card title="DDoS Protection" icon="shield-halved">
    Basic protection included
  </Card>

  <Card title="Managed Updates" icon="arrows-rotate">
    Free application updates
  </Card>

  <Card title="Monitoring" icon="chart-line">
    Basic monitoring included
  </Card>

  <Card title="Bandwidth" icon="network-wired">
    Generous data transfer allowances
  </Card>
</CardGroup>

## Total Cost of Ownership

When evaluating cloud providers, consider the total cost of ownership (TCO), which includes:

* **Instance Costs**: The basic cost of your compute resources
* **Data Transfer**: Costs for incoming and outgoing traffic
* **Additional Services**: Databases, load balancers, managed services
* **Management Overhead**: Time and expertise required to manage the infrastructure
* **Scaling Costs**: Expenses associated with handling traffic spikes

RepoCloud's all-in-one approach reduces TCO by:

1. **Simplifying Management**: Less technical expertise required
2. **Reducing Additional Services**: Many features are integrated
3. **Optimizing Resource Usage**: Autoscaling minimizes waste
4. **Eliminating Hidden Costs**: Transparent pricing model

## Making the Right Choice

While RepoCloud offers significant cost advantages, the right choice depends on your specific needs:

<AccordionGroup>
  <Accordion title="When RepoCloud is Ideal">
    RepoCloud is particularly cost-effective for:

    * Small to medium-sized businesses
    * Startups and individual developers
    * Applications with variable workloads
    * Self-hosted open-source applications
    * Projects with limited DevOps resources
    * Users who prefer simplicity over complex configurations
  </Accordion>

  <Accordion title="When to Consider Alternatives">
    Other providers might be more suitable for:

    * Complex multi-service architectures requiring specialized services
    * Applications needing very specific compliance certifications
    * Workloads requiring specialized hardware (like GPUs)
    * Enterprise applications already optimized for a specific cloud provider
  </Accordion>
</AccordionGroup>

## Calculate Your Savings

To get a personalized cost comparison between RepoCloud and your current cloud provider:

1. Review your current cloud spending
2. Identify the resources you're currently using (RAM, CPU, storage)
3. Find the equivalent RepoCloud tier in our [pricing structure](/pricing/tiers)
4. Consider how autoscaling might further reduce your costs based on your usage patterns
5. Contact our team for a detailed analysis and migration plan

<CardGroup>
  <Card title="Contact Sales" icon="envelope" href="mailto:team@repocloud.io">
    Get a personalized quote for your specific needs
  </Card>
</CardGroup>

## Next Steps

<CardGroup>
  <Card title="Autoscaling" icon="chart-line" href="/pricing/autoscaling">
    Learn more about our cost-saving elastic autoscaling
  </Card>

  <Card title="Resource Tiers" icon="layer-group" href="/pricing/tiers">
    Explore our resource tier specifications in detail
  </Card>

  <Card title="Getting Started" icon="rocket" href="/quickstart">
    Deploy your first application on RepoCloud
  </Card>
</CardGroup>


# Pricing Plans
Source: https://docs.repocloud.io/pricing/introduction

Overview of RepoCloud's pricing options and plans

# Pricing and Plans

Welcome to the RepoCloud Pricing section. Here you'll find detailed information about our pricing structure, resource tiers, and billing options to help you choose the plan that best fits your needs.

## Pricing Philosophy

RepoCloud is built on the principle that cloud hosting should be powerful, flexible, and affordable. Our pricing model is designed to provide significant cost savings compared to major cloud providers while delivering enterprise-grade performance and reliability.

## Key Topics

<CardGroup>
  <Card title="Pricing Overview" icon="money-bill" href="/pricing/overview">
    Understand RepoCloud's cost-efficient pricing model
  </Card>

  <Card title="Resource Tiers" icon="layer-group" href="/pricing/tiers">
    Explore detailed specifications for each resource tier
  </Card>

  <Card title="Pricing Comparison" icon="scale-balanced" href="/pricing/comparison">
    See how RepoCloud pricing compares to other cloud providers
  </Card>

  <Card title="Autoscaling" icon="chart-line" href="/pricing/autoscaling">
    Learn about our cost-saving elastic autoscaling technology
  </Card>
</CardGroup>

## Transparent Pricing

At RepoCloud, we believe in complete pricing transparency. There are no hidden fees or unexpected charges—what you see is what you pay. Our pricing page clearly outlines all costs associated with our services, allowing you to accurately budget for your cloud infrastructure.

## Cost Efficiency

Most users save approximately 50% on their cloud infrastructure costs compared to major providers like AWS, Azure, and Google Cloud, while maintaining enterprise-grade performance and reliability. With our elastic autoscaling technology, many customers achieve even higher savings.

## Questions?

If you have questions about our pricing or need help selecting the right plan, please contact our team at [team@repocloud.io](mailto:team@repocloud.io).


# Pricing Overview
Source: https://docs.repocloud.io/pricing/overview

Understanding RepoCloud's cost-efficient pricing model

## Pricing Overview

RepoCloud is built on the principle that cloud hosting should be powerful, flexible, and affordable. Our pricing model is designed to provide significant cost savings compared to major cloud providers while delivering enterprise-grade performance and reliability.

## Elastic Hourly Autoscaling

Our signature pricing feature is Elastic Hourly Autoscaling, available for managed application deployments. It allows you to pay only for what you actually use.

<CardGroup>
  <Card title="Traditional Cloud Pricing" icon="server">
    With traditional cloud providers, you pay for peak capacity 24/7, even when your server is idle, leading to wasted resources and higher costs.
  </Card>

  <Card title="RepoCloud Autoscaling" icon="chart-line">
    Our system dynamically adjusts resources based on actual usage, scaling up instantly when needed and down when not required, with per-hour metering.
  </Card>
</CardGroup>

### How Autoscaling Works

1. Your application starts with minimum necessary resources
2. As demand increases, resources scale up instantly without downtime
3. During periods of low activity, resources scale down automatically
4. You're billed hourly based on actual resource consumption

**Example Savings:** Instead of allocating a fixed 16GB RAM instance at \$48/month, RepoCloud might adjust your actual usage down to an average of 1GB RAM at \$3/month during low-traffic periods, potentially resulting in up to 93% cost savings.

<Note>
  Autoscaling is available for managed application deployments only. VPS Platform Apps (Coolify, Dokploy, OpenClaw, Hermes Agent, Ubuntu) use fixed resource tiers with a dedicated IPv4 address included at no extra charge.
</Note>

## Resource Tiers

All VPS Platform Apps use fixed resource tiers. Managed applications can choose between autoscaling and fixed tiers:

| Tier | RAM   | vCPU | SSD Storage | Hourly Price | Monthly Price |
| ---- | ----- | ---- | ----------- | ------------ | ------------- |
| 1    | 1 GB  | 1    | 20 GB       | \$0.0042     | \$3.00        |
| 2    | 2 GB  | 1    | 30 GB       | \$0.0083     | \$6.00        |
| 3    | 2 GB  | 2    | 40 GB       | \$0.0125     | \$9.00        |
| 4    | 4 GB  | 2    | 40 GB       | \$0.0167     | \$12.00       |
| 5    | 8 GB  | 4    | 80 GB       | \$0.0333     | \$24.00       |
| 6    | 16 GB | 8    | 160 GB      | \$0.0667     | \$48.00       |
| 7    | 32 GB | 16   | 320 GB      | \$0.1333     | \$96.00       |

<Note>
  All plans include powerful Intel vCPU, NVMe SSD, DDR4 ECC RAM, SSL certificates, custom domain support, and unmetered 1 Gbps connections. Each tier includes a free outbound data transfer allowance (see Additional Resources below).
</Note>

## Additional Resources

Beyond the base resource tiers, you can also add:

* **Dedicated IPv4 Address**: Included at no extra charge with every VPS instance
* **Snapshots**: \$0.10 per GB per month — point-in-time backups, up to 5 per instance
* **Additional NVMe SSD storage**: \$0.10 per GB per month
* **Data Transfer In**: \$0 per GB (free)
* **Data Transfer Out**: \$0.10 per GB beyond the tier-specific free allowance (1 TB for Tier 1, scaling up to 10 TB for Tier 7)

## Billing Model

RepoCloud operates on a simple, transparent, credit-based billing model:

* **Prepaid Credit**: Your account carries a credit balance, visible at the top of your dashboard and in the Billing tab
* **Hourly Metering**: Resource usage is metered hourly and deducted from your balance
* **Auto Recharge**: In the Billing tab, you can enable Auto Recharge to automatically purchase a set amount of credit whenever your balance drops below a threshold you choose (requires a payment method on file)
* **Usage History**: Download a detailed usage history from the Billing tab at any time
* **Paused Instances**: Pausing an instance reduces its billing to 25% of the normal rate; deleting it stops billing entirely
* **Baseline Cost**: The smallest tier is \$3.00 per month, so an instance that runs continuously all month costs at least that much
* **No Hidden Fees**: What you see is what you pay
* **No Long-term Contracts**: Pay as you go with no lock-in

When you sign up, new customers receive free credit for their first 30 days to test and run applications. Once this is exhausted, standard pricing applies.

## Cost Comparison

RepoCloud's pricing is designed to be approximately half that of major cloud providers:

<Tabs>
  <Tab title="1GB RAM / 1 vCPU">
    | Cloud Provider | RAM    | vCPU | Monthly Cost |
    | -------------- | ------ | ---- | ------------ |
    | RepoCloud      | 1 GB   | 1    | \$3.00       |
    | AWS EC2        | 1 GB   | 2    | \$7.59       |
    | Azure          | 1 GB   | 1    | \$7.59       |
    | DigitalOcean   | 1 GB   | 1    | \$6.00       |
    | Google Cloud   | 1 GB   | 0.25 | \$6.11       |
    | Railway        | 1 GB   | 1    | \$30.00      |
    | Render         | 0.5 GB | 0.5  | \$7.00       |
  </Tab>

  <Tab title="4GB RAM / 2 vCPU">
    | Cloud Provider | RAM  | vCPU | Monthly Cost |
    | -------------- | ---- | ---- | ------------ |
    | RepoCloud      | 4 GB | 2    | \$12.00      |
    | AWS EC2        | 4 GB | 2    | \$30.37      |
    | Azure          | 4 GB | 2    | \$30.37      |
    | DigitalOcean   | 4 GB | 2    | \$24.00      |
    | Google Cloud   | 4 GB | 1    | \$24.46      |
    | Railway        | 4 GB | 2    | \$80.00      |
    | Render         | 4 GB | 2    | \$85.00      |
  </Tab>

  <Tab title="16GB RAM / 8 vCPU">
    | Cloud Provider | RAM   | vCPU | Monthly Cost |
    | -------------- | ----- | ---- | ------------ |
    | RepoCloud      | 16 GB | 8    | \$48.00      |
    | AWS EC2        | 16 GB | 4    | \$121.47     |
    | Azure          | 16 GB | 4    | \$121.18     |
    | DigitalOcean   | 16 GB | 8    | \$96.00      |
    | Google Cloud   | 16 GB | 4    | \$97.84      |
    | Railway        | 16 GB | 8    | \$320.00     |
    | Render         | 16 GB | 4    | \$225.00     |
  </Tab>
</Tabs>

<Note>
  Competitor prices reflect each provider's cheapest comparable on-demand plan (same RAM, closest vCPU, US region, no commitments), last verified in July 2026. See the [full price comparison](/pricing/comparison) for plan names and additional providers.
</Note>

## Choosing the Right Plan

When selecting a plan, consider these factors:

1. **Application Requirements**: Different applications have different resource needs
2. **Expected Traffic**: Higher traffic requires more resources
3. **Usage Patterns**: Variable usage benefits most from autoscaling
4. **Budget Constraints**: Fixed plans offer predictable monthly costs

<Tip>
  For managed application deployments, we recommend starting with autoscaling enabled. This allows your application to find its natural resource usage pattern. VPS Platform Apps use fixed tiers only — choose a tier that meets the application's minimum requirements.
</Tip>

## FAQ

<AccordionGroup>
  <Accordion title="Can I change plans after deployment?">
    Fixed-size instances can be manually scaled to a different tier from the instance's management page. VPS Platform Apps use fixed tiers exclusively. Managed application instances with autoscaling adjust between tiers automatically.
  </Accordion>

  <Accordion title="Is there a free trial?">
    Yes, new customers receive free credit for their first 30 days to test the platform.
  </Accordion>

  <Accordion title="How is billing calculated for autoscaling?">
    With autoscaling, we measure your resource usage hourly and charge the hourly rate of the resource tier your instance used during that hour. You can see exactly which tier was used each hour in your instance's usage chart.
  </Accordion>

  <Accordion title="Are there any long-term commitments?">
    No, RepoCloud operates on a prepaid, pay-as-you-go model with no long-term contracts.
  </Accordion>

  <Accordion title="How do I pay?">
    You purchase account credit through the Billing tab of your dashboard using a credit or debit card, where you can also enable Auto Recharge to top up your balance automatically.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="Tier Details" icon="layer-group" href="/pricing/tiers">
    Explore detailed specifications for each resource tier
  </Card>

  <Card title="Autoscaling" icon="chart-line" href="/pricing/autoscaling">
    Learn more about how autoscaling works
  </Card>

  <Card title="Price Comparison" icon="scale-balanced" href="/pricing/comparison">
    See detailed comparisons with other cloud providers
  </Card>
</CardGroup>


# Pricing Tiers
Source: https://docs.repocloud.io/pricing/tiers

Detailed information on RepoCloud's pricing tiers and resource specifications

## Resource Tiers Overview

RepoCloud offers flexible resource tiers designed to accommodate a wide range of applications and workloads. Each tier provides a balanced combination of CPU, RAM, and storage resources at a fraction of the cost of major cloud providers.

## Resource Tiers

RepoCloud provides seven resource tiers, each offering progressively more computing power, memory, and storage capacity:

| Tier | RAM   | vCPU | SSD Storage | Hourly Price | Monthly Price |
| ---- | ----- | ---- | ----------- | ------------ | ------------- |
| 1    | 1 GB  | 1    | 20 GB       | \$0.0042     | \$3.00        |
| 2    | 2 GB  | 1    | 30 GB       | \$0.0083     | \$6.00        |
| 3    | 2 GB  | 2    | 40 GB       | \$0.0125     | \$9.00        |
| 4    | 4 GB  | 2    | 40 GB       | \$0.0167     | \$12.00       |
| 5    | 8 GB  | 4    | 80 GB       | \$0.0333     | \$24.00       |
| 6    | 16 GB | 8    | 160 GB      | \$0.0667     | \$48.00       |
| 7    | 32 GB | 16   | 320 GB      | \$0.1333     | \$96.00       |

<Note>
  If you need more storage than a tier includes, add extra NVMe SSD storage at deployment time with the "Add Extra SSD" option (\$0.10 per GB per month).
</Note>

## Tier Specifications in Detail

### Tier 1: Basic

**Specifications**: 1 GB RAM, 1 vCPU, 20 GB SSD Storage\
**Pricing**: \$0.0042/hour (\$3.00/month)

**Best For**:

* Small personal blogs
* Simple static websites
* Development environments
* Basic testing instances
* Low-traffic applications

**Limitations**:

* Limited processing power for resource-intensive applications
* Sufficient only for low concurrent user counts
* Not recommended for database-heavy applications

### Tier 2: Starter

**Specifications**: 2 GB RAM, 1 vCPU, 30 GB SSD Storage\
**Pricing**: \$0.0083/hour (\$6.00/month)

**Best For**:

* Personal websites with moderate traffic
* Small WordPress installations
* Development environments for larger projects
* Basic content management systems
* Small team collaboration tools

**Limitations**:

* Limited to a single CPU core
* May struggle with more demanding applications
* Moderate concurrent user capacity

### Tier 3: Standard

**Specifications**: 2 GB RAM, 2 vCPU, 40 GB SSD Storage\
**Pricing**: \$0.0125/hour (\$9.00/month)

**Best For**:

* Small business websites
* Multiple web applications
* Development and staging environments
* Content management systems
* Light e-commerce sites

**Limitations**:

* Memory-intensive applications may need more RAM
* Moderate concurrent user capacity
* Not ideal for large databases

### Tier 4: Professional

**Specifications**: 4 GB RAM, 2 vCPU, 40 GB SSD Storage\
**Pricing**: \$0.0167/hour (\$12.00/month)

**Best For**:

* Small to medium business websites
* E-commerce platforms
* Content-rich websites
* More demanding CMS installations
* Development environments for larger applications

**Limitations**:

* May need more CPU for compute-intensive applications
* Moderate database capacity
* Medium concurrent user capacity

### Tier 5: Business

**Specifications**: 8 GB RAM, 4 vCPU, 80 GB SSD Storage\
**Pricing**: \$0.0333/hour (\$24.00/month)

**Best For**:

* High-traffic websites
* Medium-sized e-commerce stores
* Database-intensive applications
* Small data analytics applications
* Media streaming platforms

**Limitations**:

* Very resource-intensive applications may need more power
* Large database operations may require higher tiers
* High but not enterprise-level concurrent user capacity

### Tier 6: Enterprise

**Specifications**: 16 GB RAM, 8 vCPU, 160 GB SSD Storage\
**Pricing**: \$0.0667/hour (\$48.00/month)

**Best For**:

* Large business applications
* High-traffic e-commerce platforms
* Media processing applications
* Data analytics workloads
* Multi-container deployments

**Limitations**:

* The most demanding enterprise applications may require Tier 7
* Very high concurrent user capacity
* Handles most workloads efficiently

### Tier 7: Ultimate

**Specifications**: 32 GB RAM, 16 vCPU, 320 GB SSD Storage\
**Pricing**: \$0.1333/hour (\$96.00/month)

**Best For**:

* Very high-traffic websites and applications
* Enterprise-grade deployments
* Large database systems
* Advanced data analytics
* Media processing and transcoding
* Computationally intensive workloads

**Limitations**:

* Our highest tier available
* For extremely demanding workloads beyond this tier, multiple instances may be needed

## Technical Specifications

All resource tiers on RepoCloud include the following technical specifications:

### Compute

* **CPU Type**: Intel vCPUs
* **CPU Performance**: High-performance vCPUs

### Memory

* **RAM Type**: DDR4 ECC RAM

### Storage

* **Storage Type**: NVMe SSD for all tiers
* **I/O Performance**: High I/O operations per second (IOPS)
* **Extra Storage**: Additional NVMe SSD can be added at deployment for \$0.10 per GB per month
* **Backups**: RepoCloud does not provide instance-level backups—use your application's built-in backup tools (e.g., n8n workflow exports, WordPress backup plugins) and export important data regularly

### Networking

* **Network Speed**: 1 Gbps connections
* **Bandwidth**: Unlimited bandwidth (data transfer in is free; data transfer out is priced at \$0.10 per GB as listed on the pricing page)
* **Network Security**: DDoS protection
* **SSL Support**: Free SSL certificates included

## Choosing the Right Tier

When selecting a resource tier, consider these factors:

### Application Requirements

Different applications have different resource needs:

<AccordionGroup>
  <Accordion title="WordPress">
    * **Small Blog**: Tier 1-2
    * **Medium Site**: Tier 3-4
    * **Large Site**: Tier 5+
    * **WooCommerce**: Tier 4+ (depending on product count)
  </Accordion>

  <Accordion title="Databases">
    * **Small Database**: Tier 2-3
    * **Medium Database**: Tier 4-5
    * **Large Database**: Tier 6-7
  </Accordion>

  <Accordion title="Development Tools">
    * **Git Repositories**: Tier 2-3
    * **CI/CD Tools**: Tier 3-5
    * **Code Servers**: Tier 3-4
  </Accordion>

  <Accordion title="Content Management">
    * **Small CMS**: Tier 2-3
    * **Medium CMS**: Tier 3-4
    * **Enterprise CMS**: Tier 5+
  </Accordion>
</AccordionGroup>

### Traffic Patterns

Consider your expected traffic patterns:

* **Low Traffic** (\< 10,000 visits/month): Tier 1-2
* **Medium Traffic** (10,000-50,000 visits/month): Tier 3-4
* **High Traffic** (50,000-200,000 visits/month): Tier 5-6
* **Very High Traffic** (200,000+ visits/month): Tier 6-7

### Data Processing Needs

Different data workloads require different resources:

* **Basic Data Storage**: Tier 1-3
* **Data Analysis**: Tier 4-5
* **Large Datasets**: Tier 5-7
* **Real-time Processing**: Tier 5-7

## Moving Between Tiers

How your instance moves between tiers depends on the deployment type:

* **VPS Platform Apps** (Coolify, Dokploy, OpenClaw, Hermes Agent, Ubuntu) use fixed tiers exclusively. You can resize to a different tier from the management page. Disk downgrades are not supported.
* **Managed applications** with autoscaling move between tiers automatically based on demand—no action needed. Fixed-size managed instances can be scaled manually from the management page.

<Warning>
  If you're choosing a fixed tier, make sure your application can operate properly within its resources—an undersized tier may cause performance issues or application failures. VPS Platform Apps have enforced minimum tier requirements.
</Warning>

## Autoscaling vs. Fixed Tiers

RepoCloud offers two approaches to resource allocation:

### Fixed Tiers

* **Predictable Costs**: Fixed monthly pricing based on the selected tier
* **Guaranteed Resources**: Consistent resource allocation regardless of usage
* **Simplicity**: No need to monitor or manage scaling
* **Best For**: VPS Platform Apps and applications with consistent resource needs
* **IPv4 Included**: Every VPS instance includes a dedicated IPv4 address at no extra charge

### Elastic Autoscaling (Managed Apps Only)

* **Cost Efficiency**: Pay only for resources actually used
* **Dynamic Adjustment**: Resources scale up and down based on actual needs
* **Optimal Performance**: Automatically handles traffic spikes
* **Best For**: Managed applications with variable resource needs

<Tip>
  For managed application deployments, we recommend keeping autoscaling enabled (it's the default). VPS Platform Apps use fixed tiers only — select a tier that meets the application's minimum requirements.
</Tip>

## Additional Resources

Beyond the base resource tiers, you can also add:

* **Additional NVMe SSD storage**: \$0.10 per GB per month
* **Data Transfer In**: \$0 per GB (free)
* **Data Transfer Out**: \$0.10 per GB

## Next Steps

<CardGroup>
  <Card title="Price Comparison" icon="scale-balanced" href="/pricing/comparison">
    See how RepoCloud pricing compares to other cloud providers
  </Card>

  <Card title="Autoscaling" icon="chart-line" href="/pricing/autoscaling">
    Learn more about RepoCloud's elastic autoscaling
  </Card>
</CardGroup>


# Quickstart Guide
Source: https://docs.repocloud.io/quickstart

Get started with RepoCloud in just a few minutes

## Get Started with RepoCloud

This quickstart guide will walk you through the process of deploying your first application on RepoCloud.

### Create Your Account

<Steps>
  <Step title="Sign Up">
    Visit [RepoCloud.io](https://repocloud.io/register) and create your account. New customers receive free credit for their first 30 days to get started.
  </Step>

  <Step title="Verify Your Email">
    Check your inbox for a verification email from RepoCloud and click the verification link.
  </Step>

  <Step title="Log In">
    Return to [RepoCloud.io](https://repocloud.io/login) and log in with your credentials.
  </Step>

  <Step title="Secure Your Account (Optional)">
    In the **Settings** tab of your dashboard, you can enable two-factor authentication (2FA) using any TOTP app such as Google Authenticator, Authy, Microsoft Authenticator, 1Password, or Bitwarden.
  </Step>
</Steps>

### Deploy Your First Application

<Steps>
  <Step title="Browse the Marketplace">
    Explore our [marketplace](https://repocloud.io/results) of over 270 applications to find the one you want to deploy.
  </Step>

  <Step title="Select an Application">
    Click on an application to view its details, features, and links to the developer's website and documentation, then click "Deploy Now".
  </Step>

  <Step title="Configure Settings">
    Enter a project name, then either keep the "Autoscale compute and storage resources" toggle enabled (the default) or disable it to pick a fixed server size. Some applications also ask for application-specific settings such as an admin username and password.

    <Note>
      Our platform automatically configures the optimal settings for each application, but you can customize them according to your needs.
    </Note>
  </Step>

  <Step title="Launch Your Application">
    Click the "Deploy App" button to launch your application. The deployment process typically takes 3-7 minutes.
  </Step>
</Steps>

### Manage Your Deployment

Once your application is deployed, you can manage it through our intuitive dashboard:

<AccordionGroup>
  <Accordion icon="globe" title="Set Up a Custom Domain">
    You can easily add your own domain to your deployment:

    1. Go to your application's management page
    2. Click "Add Custom Domain"
    3. Enter your domain name
    4. Add the two CNAME records shown (one for your subdomain, one for the `_acme-challenge` verification record) at your domain registrar
    5. Click "Confirm and Check Status" once the records are in place (DNS propagation can take up to 24-48 hours, but is often much faster)
  </Accordion>

  <Accordion icon="sliders" title="Monitor and Adjust Resources">
    Instances deployed with autoscaling (the default) adjust their resources automatically:

    1. Go to your application's management page
    2. Click "View Usage Chart" to see which resource tier your application has been using hour by hour

    If you deployed with a fixed server size, you can manually change it to a different tier—or switch it over to autoscaling—from the management page. (Autoscaled instances can't be switched back to a fixed size.)
  </Accordion>

  <Accordion icon="arrows-rotate" title="Update Your Application">
    Keep your application up-to-date with the latest version:

    1. Go to your application's management page
    2. Click the "Rebuild / Update" button
    3. Confirm the update

    Your application will be updated to the latest stable version while preserving your data.
  </Accordion>

  <Accordion icon="gear" title="Manage Environment Variables">
    Customize your application's configuration:

    1. Go to your application's management page
    2. Click "Edit Env Vars"
    3. Add, edit, or remove environment variables
    4. Click "Save Changes" and confirm

    Your application will restart with the new configuration; the restart typically takes 3-7 minutes.
  </Accordion>
</AccordionGroup>

## Next Steps

Now that you've deployed your first application, explore these resources to make the most of RepoCloud:

<CardGroup>
  <Card title="Platform Overview" icon="server" href="/platform/how-it-works">
    Learn more about how RepoCloud works behind the scenes
  </Card>

  <Card title="Supported Applications" icon="box-archive" href="https://repocloud.io/results">
    Browse our catalog of 270+ applications available for deployment
  </Card>

  <Card title="Deployment Guide" icon="rocket" href="/user-guide/deployment-basics">
    Discover advanced deployment options and best practices
  </Card>

  <Card title="Instance Management" icon="sliders" href="/user-guide/managing-instances">
    Master the tools for managing your deployed applications
  </Card>

  <Card title="Pricing & Billing" icon="credit-card" href="/pricing/overview">
    Understand how our pricing works to optimize your costs
  </Card>
</CardGroup>


# Affiliate Program
Source: https://docs.repocloud.io/resources/affiliate-program

Earn recurring commissions by referring customers to RepoCloud

## RepoCloud Affiliate Program

The RepoCloud Affiliate Program allows you to earn substantial, recurring commissions by referring customers to our platform. With a generous 25% lifetime commission structure, you can create a steady stream of passive income while helping others discover the benefits of RepoCloud.

## Program Highlights

<CardGroup>
  <Card title="25% Lifetime Commission" icon="money-bill-wave">
    Earn 25% of what your referrals pay, for as long as they remain customers
  </Card>

  <Card title="30-Day Cookie Window" icon="cookie">
    Referrals are tracked for 30 days after clicking your link
  </Card>

  <Card title="Reliable Payouts" icon="calendar-check">
    Receive payments every 60 days, with a minimum payout of \$50
  </Card>

  <Card title="Easy Tracking" icon="chart-line">
    Monitor your referrals and earnings through a dedicated dashboard
  </Card>
</CardGroup>

## How It Works

The RepoCloud Affiliate Program operates with a straightforward process:

<Steps>
  <Step title="Open Your Referrals Dashboard">
    Every RepoCloud account includes the affiliate program. Log in and open the "Referrals" tab of your dashboard (or visit [repocloud.io/affiliate](https://repocloud.io/affiliate)).
  </Step>

  <Step title="Copy Your Referral Link">
    Your unique referral link (in the format `https://repocloud.io/?ref=yourcode`) is displayed with a one-click copy button
  </Step>

  <Step title="Promote RepoCloud">
    Share your referral link on your website, social media, or directly with potential customers
  </Step>

  <Step title="Track Performance">
    Monitor your affiliate balance, users referred, next payout date, and referral history in the Referrals tab—you can also download your referral history as a CSV
  </Step>

  <Step title="Request Payouts">
    Once you're eligible, submit a payout request directly from the Referrals tab with your contact and payment details
  </Step>
</Steps>

## Commission Structure

The RepoCloud Affiliate Program offers one of the most competitive commission structures in the industry:

* **Commission Rate**: 25% of customer payments
* **Commission Type**: Recurring for the lifetime of the customer
* **Cookie Duration**: 30 days
* **Payment Schedule**: Net 60 days
* **Minimum Payout**: \$50
* **Payment Methods**: PayPal (US), PayPal (International), Payoneer, or RepoCloud credit top-up

<Note>
  Commissions are calculated based on confirmed payments from your referrals. For example, if a customer you refer spends \$100 per month, you'll earn \$25 per month in commissions for as long as they remain a customer.
</Note>

## Payment Schedule

Commissions are processed according to the following schedule:

1. **Calculation Period**: Commissions are calculated based on confirmed referrals
2. **Payment Processing**: Payments are disbursed on a 60-day cycle, covering commissions accrued during prior periods
3. **Minimum Threshold**: A minimum of \$50 in earned commissions is required for payout
4. **Payment Methods**: PayPal (US), PayPal (International), Payoneer, or RepoCloud credit top-up

For example, commissions earned in January will be paid by March 31st, allowing time for payment validation and processing.

## Join the Affiliate Program

Ready to start earning recurring commissions by promoting RepoCloud? Join our affiliate program today!

<CardGroup>
  <Card title="Open Your Referrals Dashboard" icon="user-plus" href="https://repocloud.io/affiliate">
    Get your referral link from the Referrals tab of your RepoCloud dashboard
  </Card>

  <Card title="Contact Affiliate Support" icon="headset" href="mailto:team@repocloud.io">
    Get answers to your questions about the program
  </Card>
</CardGroup>


# Resource Center
Source: https://docs.repocloud.io/resources/introduction

Programs, tools, and information to help you get the most from RepoCloud

# Resource Center

Welcome to the RepoCloud Resource Center. This section provides access to programs, guidelines, and additional resources to help you maximize the value of the RepoCloud platform.

## Programs and Opportunities

RepoCloud offers various programs to engage with our community and ecosystem:

<CardGroup>
  <Card title="Affiliate Program" icon="handshake" href="/resources/affiliate-program">
    Earn recurring commissions by referring customers to RepoCloud
  </Card>

  <Card title="Submit Your App" icon="cloud" href="/resources/submit-app">
    Add your application to the RepoCloud marketplace
  </Card>
</CardGroup>

## Getting Involved

RepoCloud is more than just a platform—it's a community of developers, businesses, and technology enthusiasts. We encourage you to:

1. **Participate in our programs** - Become an affiliate or submit your application
2. **Provide feedback** - Help us improve by sharing your thoughts and suggestions
3. **Connect with us** - Follow us on social media and join our community discussions
4. **Stay updated** - Subscribe to our newsletter for the latest announcements and updates

## Contact Us

If you have questions about any of our resources or programs, please contact us at [team@repocloud.io](mailto:team@repocloud.io).


# Submit Your App
Source: https://docs.repocloud.io/resources/submit-app

Submit your application to the RepoCloud marketplace

## Add Your App to the RepoCloud Marketplace

RepoCloud welcomes developers and companies to submit their applications to our growing marketplace. By listing your application, you gain exposure to our expanding user base and provide value to cloud developers worldwide.

## Benefits of Listing Your App

<CardGroup>
  <Card title="Built-in User Base" icon="users">
    Immediate exposure to RepoCloud's growing community of developers
  </Card>

  <Card title="Simplified Distribution" icon="box">
    Your app becomes deployable in one click, with installation handled by the platform
  </Card>
</CardGroup>

## Types of Apps We Accept

RepoCloud accepts a wide variety of applications that enhance the cloud development experience:

<AccordionGroup>
  <Accordion title="Development Tools">
    IDEs, code editors, version control tools, testing frameworks, CI/CD solutions, and other tools that enhance the development workflow.
  </Accordion>

  <Accordion title="Deployment Platforms">
    Application platforms, PaaS solutions, container orchestration tools, and serverless frameworks that simplify deployment.
  </Accordion>

  <Accordion title="Databases & Storage">
    Database systems, object storage, caching solutions, and other data storage or management tools.
  </Accordion>

  <Accordion title="Monitoring & Observability">
    APM tools, log management solutions, metric collection systems, and dashboards for monitoring application performance.
  </Accordion>

  <Accordion title="Security Tools">
    Vulnerability scanners, security testing tools, compliance checkers, and identity management solutions.
  </Accordion>

  <Accordion title="Content Management Systems">
    Headless CMS platforms, traditional CMS solutions, and other content management tools.
  </Accordion>

  <Accordion title="E-commerce Platforms">
    Online store platforms, payment processing systems, and e-commerce enablement tools.
  </Accordion>

  <Accordion title="Analytics Solutions">
    Data analytics platforms, business intelligence tools, and reporting systems.
  </Accordion>
</AccordionGroup>

## Application Requirements

To ensure a quality experience for our users, all platform applications must meet certain requirements:

### Technical Requirements

1. **Docker Compatibility**: Applications must be containerized with Docker or compatible with our container platform
2. **Documentation**: Comprehensive documentation for installation, configuration, and usage
3. **Security**: Adherence to security best practices with no known critical vulnerabilities
4. **Performance**: Efficient resource usage and appropriate performance characteristics
5. **Scalability**: Support for horizontal or vertical scaling when applicable
6. **High Availability**: Support for redundancy configurations when applicable

## How to Submit Your App

Submitting an application takes just a few minutes:

<Steps>
  <Step title="Open the Submission Form">
    Log in to your RepoCloud account and go to [repocloud.io/submitapp](https://repocloud.io/submitapp) (also linked as "Submit" in the site footer)
  </Step>

  <Step title="Fill In the Details">
    Provide the project name, a link to the application's repository (e.g., `https://github.com/example/app`), and a description of the application
  </Step>

  <Step title="Accept the Terms">
    Read and agree to the Terms & Conditions
  </Step>

  <Step title="Submit">
    Click "Add App to Marketplace". Our team reviews submissions against the requirements above before publishing them to the marketplace.
  </Step>
</Steps>

## Questions?

If you have questions about submitting your application or want to discuss a partnership, contact us at [team@repocloud.io](mailto:team@repocloud.io).


# Custom Domains
Source: https://docs.repocloud.io/user-guide/custom-domains

Connect your own domain name to your RepoCloud applications

## Using Custom Domains

By default, every application deployed on RepoCloud receives a randomly assigned subdomain on one of our hosting domains, in the format `https://<your-app-id>.<hosting-domain>` (we use several different domains for auto-generated URLs). However, you can connect your own domain name to provide a professional, branded experience for your users.

<Note>
  Custom domains allow you to use your brand's domain name while hosting your application on RepoCloud, giving your application a professional appearance and better brand recognition.
</Note>

## Why Use a Custom Domain?

<CardGroup>
  <Card title="Professional Branding" icon="briefcase">
    Present a cohesive brand identity with your own domain
  </Card>

  <Card title="Better SEO" icon="magnifying-glass">
    Establish and maintain search engine optimization
  </Card>

  <Card title="Business Credibility" icon="handshake">
    Enhance trust with a professional domain name
  </Card>

  <Card title="Marketing Consistency" icon="bullhorn">
    Maintain consistent branding across all channels
  </Card>
</CardGroup>

## Setting Up a Custom Domain

Adding a custom domain to your RepoCloud application is a straightforward process:

<Steps>
  <Step title="Access Domain Settings">
    Navigate to your application's management page and click the "Add Custom Domain" button.
  </Step>

  <Step title="Add Your Domain">
    Enter your domain (e.g., `app.yourdomain.com`) in the input field and click "Submit".

    <Note>
      If you enter a root domain (e.g., `yourdomain.com` without a subdomain), RepoCloud will warn you that your DNS provider must support ANAME, ALIAS, or CNAME-flattening records, and will offer to use a `www` subdomain instead. See [Using Apex Domains](#using-apex-domains) below.
    </Note>
  </Step>

  <Step title="Configure DNS Records">
    RepoCloud displays the exact DNS records you need to add at your domain registrar. You'll add two CNAME records:

    * A CNAME for your subdomain pointing to your application's auto-generated address (e.g., `app` → `<your-app-id>.<hosting-domain>.`)
    * A CNAME for `_acme-challenge` pointing to the SSL verification target shown in the dashboard (used to issue your SSL certificate)

    Each record includes a copy button, and the dashboard shows a live status indicator for each record.
  </Step>

  <Step title="Wait for DNS Propagation">
    DNS changes can take up to 24-48 hours to propagate globally, though they often take effect much sooner.
  </Step>

  <Step title="Confirm and Check Status">
    Click the "Confirm and Check Status" button in the dashboard. Once both records verify, RepoCloud automatically issues an SSL certificate and routes your domain to your application.
  </Step>
</Steps>

<Tip>
  To remove a custom domain later, return to your application's management page and click "Remove Domain".
</Tip>

## DNS Record Types Explained

When setting up a custom domain, you may need to configure different DNS record types:

<AccordionGroup>
  <Accordion title="CNAME Record (Routing)">
    A CNAME (Canonical Name) record maps an alias domain to a true or canonical domain. For RepoCloud, this maps your domain to your application's auto-generated address.

    Example: `app.yourdomain.com` → `<your-app-id>.<hosting-domain>.`
  </Accordion>

  <Accordion title="CNAME Record (SSL Verification)">
    RepoCloud also asks you to add a CNAME record on the `_acme-challenge` name of your domain, pointing to the verification target shown in your dashboard. This record allows SSL certificates to be issued and renewed automatically for your domain.

    Example: `_acme-challenge.yourdomain.com` → `yourdomain.com.<unique-id>.dcv.cloudflare.com.`
  </Accordion>

  <Accordion title="ALIAS / ANAME Records (Apex Domains)">
    Apex (root) domains normally cannot use CNAME records. Some DNS providers offer ALIAS or ANAME records, or CNAME flattening, which provide CNAME-like behavior at the apex. These are required if you want to point a root domain (e.g., `yourdomain.com`) at RepoCloud.
  </Accordion>
</AccordionGroup>

## Using Apex Domains

An apex domain (also called a root domain or naked domain) is a domain without a subdomain prefix, like `example.com` instead of `www.example.com`.

To use an apex domain with RepoCloud, your DNS provider must support CNAME-like functionality for apex domains through features like:

* ALIAS records
* ANAME records
* CNAME flattening

Some DNS providers, such as GoDaddy, do not support these features. If yours doesn't, you can:

* Use a subdomain (like `www.yourdomain.com`) instead — RepoCloud offers this option automatically when you enter a root domain
* Point your nameservers to Cloudflare first, or switch to another DNS provider that supports ALIAS/ANAME records (such as Route 53 or DNSimple)

<Tip>
  Using `www.yourdomain.com` instead of just `yourdomain.com` often provides better flexibility and performance.
</Tip>

## SSL Certificates

RepoCloud automatically provisions and manages SSL certificates for your custom domains:

* **Automatic Provisioning**: SSL certificates are automatically issued once your DNS records are verified
* **Automatic Renewal**: Certificates are renewed automatically before they expire
* **HTTPS Enforcement**: All traffic to your application is served over HTTPS

<Note>
  SSL certificate issuance typically takes a few minutes after DNS verification is complete.
</Note>

## SSL Certificate Issuance Method

RepoCloud uses DNS-based domain validation for SSL certificate issuance:

### How DNS Validation Works

<Steps>
  <Step title="Record Generation">
    When you add a domain, RepoCloud generates a unique `_acme-challenge` CNAME target for it
  </Step>

  <Step title="Record Creation">
    You add the `_acme-challenge` CNAME record (shown in your dashboard) at your DNS provider, alongside the routing CNAME
  </Step>

  <Step title="Domain Validation">
    The certificate authority validates domain control by resolving the `_acme-challenge` record
  </Step>

  <Step title="Certificate Issuance">
    Once validated, the SSL certificate is issued and applied to your application, and renewals happen automatically as long as the record stays in place
  </Step>
</Steps>

<Warning>
  Do not delete the `_acme-challenge` CNAME record after setup—it is required for automatic certificate renewal.
</Warning>

### Multiple Subdomains on the Same Domain

If you're using multiple subdomains of the same domain (e.g., `app1.yourdomain.com` and `app2.yourdomain.com`) for different RepoCloud applications, there are some important considerations:

<Warning>
  Each subdomain must resolve to the correct application, and each application generates its own verification records. This can create complications when you have multiple applications using subdomains of the same root domain.
</Warning>

### Recommended Solution: Cloudflare

<CardGroup>
  <Card title="Use Cloudflare for Multiple Subdomains" icon="cloud">
    We strongly recommend using Cloudflare as your DNS provider when hosting multiple applications on different subdomains of the same domain. Cloudflare's proxy functionality helps resolve the ACME challenge validation issues.
  </Card>
</CardGroup>

#### Benefits of Using Cloudflare:

* **Proxy Mode**: Cloudflare's proxy capabilities help route SSL validation correctly
* **SSL Flexibility**: Better handling of multiple SSL certificates for different subdomains
* **Performance**: Additional CDN and caching benefits
* **Security**: Additional protection against DDoS and other attacks

<Tip>
  To set up Cloudflare for your domain, transfer your nameservers to Cloudflare and enable the proxy setting (orange cloud icon) for each subdomain record.
</Tip>

## Managing Multiple Domains

You can add multiple domains to a single application:

1. Follow the same process for each domain you want to add
2. All domains will point to the same application
3. Each domain will receive its own SSL certificate

This is useful for:

* Supporting multiple brands or regions
* Migrating from an old domain to a new one
* Creating specialized landing pages

## Troubleshooting Custom Domains

<AccordionGroup>
  <Accordion title="DNS Verification Failed">
    * Verify that you've added the correct DNS records at your domain registrar
    * Check for typos in the DNS record values
    * Allow sufficient time for DNS propagation (up to 48 hours)
    * Use a DNS lookup tool like [DNS Checker](https://dnschecker.org) to verify your records are visible
  </Accordion>

  <Accordion title="SSL Certificate Issues">
    * Ensure domain verification is complete
    * Check that your DNS records are correctly configured
    * Wait at least 30 minutes for the SSL certificate to be issued
    * If issues persist for more than 24 hours, contact support
  </Accordion>

  <Accordion title="Domain Shows 'Not Secure'">
    * This typically means the SSL certificate hasn't been issued yet
    * Verify that DNS configuration is correct
    * Wait for SSL certificate issuance to complete
    * Check that you're accessing the site via HTTPS, not HTTP
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="Environment Variables" icon="gear" href="/user-guide/environment-variables">
    Configure application-specific settings through environment variables
  </Card>

  <Card title="Scaling" icon="chart-line" href="/user-guide/scaling">
    Learn how to scale your application resources
  </Card>

  <Card title="Updates" icon="arrows-rotate" href="/user-guide/updates">
    Keep your application updated with the latest features and security patches
  </Card>
</CardGroup>


# Deployment Basics
Source: https://docs.repocloud.io/user-guide/deployment-basics

Learn the fundamentals of deploying applications on RepoCloud

## Understanding RepoCloud Deployments

Deploying applications on RepoCloud is designed to be straightforward and user-friendly. This guide will walk you through the core concepts and steps for successful deployments.

## Deployment Lifecycle

<Steps>
  <Step title="Select an Application">
    Browse our marketplace to find the application you want to deploy. We offer over 270 pre-configured applications across different categories.
  </Step>

  <Step title="Configure Resources">
    Keep the "Autoscale compute and storage resources" toggle enabled (the default) to let RepoCloud optimize resource allocation automatically, or disable it to select a fixed server size. You can also add extra SSD storage at this step.
  </Step>

  <Step title="Application-Specific Settings">
    Configure settings specific to your chosen application, such as admin username and password, or other customization options.
  </Step>

  <Step title="Deploy">
    Click the "Deploy App" button to initiate the deployment process. RepoCloud will provision the necessary resources, set up your application container, and configure the networking.
  </Step>

  <Step title="Access and Configure">
    Once deployment is complete, you'll receive a URL on one of our hosting domains (in the format `https://<your-app-id>.<hosting-domain>`) to access your application. Most applications will have a setup wizard or admin interface for further configuration.
  </Step>
</Steps>

## Key Deployment Concepts

### Resource Tiers

RepoCloud offers several resource tiers to accommodate different needs:

| Tier | RAM      | vCPU | Storage    | Best For                                            |
| ---- | -------- | ---- | ---------- | --------------------------------------------------- |
| 1    | 1 GB     | 1    | 20 GB      | Small blogs, simple tools, development environments |
| 2    | 2 GB     | 1    | 30 GB      | Personal websites, small team collaboration         |
| 3    | 2 GB     | 2    | 40 GB      | Production websites, small business applications    |
| 4    | 4 GB     | 2    | 40 GB      | Medium traffic sites, larger databases              |
| 5    | 8 GB     | 4    | 80 GB      | High-traffic websites, data-intensive applications  |
| 6+   | 16-32 GB | 8-16 | 160-320 GB | Enterprise applications, large databases            |

### Autoscaling vs. Fixed Resources

<CardGroup>
  <Card title="Autoscaling" icon="chart-line">
    **Benefits:**

    * Pay only for resources you actually use
    * Automatically handles traffic spikes
    * Scales down during low-activity periods
    * Cost-efficient for variable workloads
  </Card>

  <Card title="Fixed Resources" icon="lock">
    **Benefits:**

    * Predictable monthly costs
    * Guaranteed resources at all times
    * Simpler to budget and plan
    * Better for consistent workloads
  </Card>
</CardGroup>

<Note>
  Autoscaling monitors your application's resource usage and adjusts resources in real-time, charging on an hourly basis for what you actually use.
</Note>

## Application Persistence

Applications deployed on RepoCloud maintain data persistence across restarts and updates:

* **Persistent Storage**: Application data is stored on reliable NVMe SSD storage
* **Database Persistence**: Databases maintain data integrity across updates
* **Configuration Persistence**: Your application settings remain intact when updating or scaling

## Security Considerations

Every deployment on RepoCloud includes:

* **SSL Certificates**: Automatic SSL for secure HTTPS connections
* **Application Isolation**: Containerized deployments for security isolation
* **Regular Updates**: Latest security patches and application updates
* **Secure Networking**: Protected networking environment

## Common Deployment Questions

<AccordionGroup>
  <Accordion title="How long does deployment take?">
    Most applications deploy within 3-7 minutes. Larger applications with more complex setups might take longer.
  </Accordion>

  <Accordion title="Can I migrate my existing application?">
    Yes, most applications have built-in migration tools. For example, WordPress sites can be migrated using plugins, and databases can be imported through application-specific tools.
  </Accordion>

  <Accordion title="What happens if I need more resources?">
    If you deployed with autoscaling (the default), resources adjust automatically as demand changes—no action needed. If you deployed with a fixed server size, you can manually scale it to a different tier, or switch it over to autoscaling, from the management page. Note that autoscaled instances can't be switched back to a fixed size.
  </Accordion>

  <Accordion title="Can I use my own domain name?">
    Yes, you can connect your custom domain to any deployment with the "Add Custom Domain" button in the management dashboard.
  </Accordion>

  <Accordion title="How are applications updated?">
    RepoCloud maintains the latest stable versions of all applications. You can update your instance by clicking the "Rebuild / Update" button in the management dashboard.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="One-Click Deployment" icon="rocket" href="/user-guide/one-click-deployment">
    Learn about our one-click deployment process
  </Card>

  <Card title="Managing Instances" icon="sliders" href="/user-guide/managing-instances">
    Discover how to manage your deployed applications
  </Card>

  <Card title="Custom Domains" icon="globe" href="/user-guide/custom-domains">
    Set up custom domains for your applications
  </Card>

  <Card title="Environment Variables" icon="gear" href="/user-guide/environment-variables">
    Configure your applications with environment variables
  </Card>
</CardGroup>


# Environment Variables
Source: https://docs.repocloud.io/user-guide/environment-variables

Configure application behavior using environment variables on RepoCloud

## Using Environment Variables

Environment variables are a powerful way to configure your applications without modifying code. They allow you to customize your application's behavior, store configuration settings, and manage sensitive information like API keys and database credentials.

## What Are Environment Variables?

Environment variables are dynamic values that can affect the way running processes behave on a computer. In the context of containerized applications, they provide a way to:

* Configure application settings
* Store API keys and credentials
* Toggle features on and off
* Set configuration options
* Define connection parameters

## Managing Environment Variables on RepoCloud

RepoCloud makes it easy to set, update, and manage environment variables for your applications through a simple web interface.

### Accessing Environment Variables

<Steps>
  <Step title="Navigate to Instance Management">
    Go to your application's management page in the RepoCloud dashboard
  </Step>

  <Step title="Open Environment Variables">
    Click the "Edit Env Vars" button
  </Step>

  <Step title="View Current Variables">
    You'll see a list of all currently configured environment variables as key/value rows (values are masked)
  </Step>
</Steps>

### Adding Environment Variables

<Steps>
  <Step title="Navigate to Environment Variables">
    Access the Edit Env Vars section as described above
  </Step>

  <Step title="Add New Variable">
    Click the "+ Add New Variable" button
  </Step>

  <Step title="Enter Key and Value">
    Enter the variable name (key) and its value in the new row

    Example:

    * Key: `DATABASE_URL`
    * Value: `mysql://user:password@localhost:3306/mydatabase`
  </Step>

  <Step title="Save Changes">
    Click "Save Changes" and confirm. Your application will restart with the new variables applied.
  </Step>
</Steps>

### Editing and Deleting Variables

<Steps>
  <Step title="Navigate to Environment Variables">
    Access the Edit Env Vars section
  </Step>

  <Step title="Edit a Variable">
    Change the key or value directly in the row you want to modify
  </Step>

  <Step title="Delete a Variable">
    Click the trash icon next to the variable you want to remove
  </Step>

  <Step title="Save Changes">
    Click "Save Changes" and confirm to update your application's environment
  </Step>
</Steps>

<Note>
  Saving environment variable changes restarts your application so the new configuration takes effect. The restart typically takes 3-7 minutes.
</Note>

## Sensitive Information and Security

Environment variables are commonly used to store sensitive information like API keys, passwords, and tokens. RepoCloud protects this data in the dashboard:

* **Masked Display**: Values are masked in the interface (displayed as `••••••••`)
* **Access Control**: Only your account can view and modify your instances' environment variables

<Warning>
  Despite these precautions, you should never store extremely sensitive secrets (like private keys) as environment variables. For such cases, consider using a dedicated secrets management solution.
</Warning>

## Common Environment Variables

Different applications use different environment variables, but some common categories include:

<AccordionGroup>
  <Accordion title="Database Connection Strings">
    Variables that define how your application connects to a database:

    ```
    DATABASE_URL=postgresql://user:password@hostname:port/database
    DB_HOST=hostname
    DB_USER=username
    DB_PASSWORD=password
    DB_NAME=database
    ```
  </Accordion>

  <Accordion title="API Keys and Authentication">
    Variables for third-party service integration:

    ```
    API_KEY=your_api_key_here
    AWS_ACCESS_KEY_ID=your_access_key
    AWS_SECRET_ACCESS_KEY=your_secret_key
    STRIPE_API_KEY=sk_test_abcdefghijklmnopqrstuvwxyz
    ```
  </Accordion>

  <Accordion title="Application Settings">
    Variables that control application behavior:

    ```
    DEBUG=true
    LOG_LEVEL=info
    CACHE_TTL=3600
    FEATURE_X_ENABLED=true
    ```
  </Accordion>

  <Accordion title="Email Configuration">
    Variables for email service configuration:

    ```
    SMTP_HOST=smtp.example.com
    SMTP_PORT=587
    SMTP_USER=user@example.com
    SMTP_PASSWORD=password
    ```
  </Accordion>
</AccordionGroup>

## Application-Specific Variables

Each application has its own set of supported environment variables. Here are examples for some popular applications:

<AccordionGroup>
  <Accordion title="WordPress">
    Common WordPress configuration variables:

    ```
    WORDPRESS_DB_HOST=mysql_host
    WORDPRESS_DB_USER=db_user
    WORDPRESS_DB_PASSWORD=db_password
    WORDPRESS_DB_NAME=wordpress
    WORDPRESS_TABLE_PREFIX=wp_
    ```
  </Accordion>

  <Accordion title="Node.js Applications">
    Common Node.js application variables:

    ```
    NODE_ENV=production
    PORT=3000
    SESSION_SECRET=your_session_secret
    CORS_ORIGIN=https://example.com
    ```
  </Accordion>

  <Accordion title="PostgreSQL">
    PostgreSQL configuration variables:

    ```
    POSTGRES_USER=postgres
    POSTGRES_PASSWORD=password
    POSTGRES_DB=mydb
    PGDATA=/var/lib/postgresql/data
    ```
  </Accordion>
</AccordionGroup>

<Tip>
  Check your application's documentation to understand which environment variables are available and what they do. Many applications include a list of supported variables in their documentation.
</Tip>

## Best Practices

Follow these best practices when working with environment variables:

1. **Use descriptive names**: Choose clear, descriptive names for your variables
2. **Separate development and production**: Use different values for development and production environments
3. **Document your variables**: Keep a record of what each variable does and why it's needed
4. **Minimize sensitive data**: Only store sensitive information in environment variables when necessary
5. **Use standard formats**: Follow established formats for connection strings and other structured data
6. **Avoid hardcoding**: Never hardcode values that should be configurable in your application code

## Troubleshooting

<AccordionGroup>
  <Accordion title="Application Not Recognizing Variables">
    If your application doesn't recognize environment variables:

    * Verify the variable name is correct (including case)
    * Ensure the application has restarted after changes
    * Check application logs for environment-related errors
    * Verify the application is designed to use the variables you're setting
  </Accordion>

  <Accordion title="Syntax Errors">
    Some common syntax issues:

    * Avoid spaces around the equals sign (use `KEY=value`, not `KEY = value`)
    * Be careful with quotes (some values may need to be quoted)
    * Watch for special characters that might need escaping
  </Accordion>

  <Accordion title="Changes Not Taking Effect">
    If changes don't seem to apply:

    * Wait for the restart to finish—saving environment variables restarts your app, which takes 3-7 minutes
    * Check if the application caches configuration and needs a specific refresh
    * Verify you clicked "Save Changes" and confirmed in the dashboard
    * As a last resort, use "Rebuild / Update" to recreate the instance with the current configuration
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="Scaling" icon="chart-line" href="/user-guide/scaling">
    Learn how to scale your application resources
  </Card>

  <Card title="Updates" icon="arrows-rotate" href="/user-guide/updates">
    Keep your application updated with the latest features and security patches
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/user-guide/troubleshooting">
    Resolve common issues with your RepoCloud applications
  </Card>
</CardGroup>


# User Guide
Source: https://docs.repocloud.io/user-guide/introduction

Guide to using the RepoCloud platform effectively

Welcome to the RepoCloud User Guide. This section provides comprehensive instructions on how to deploy, manage, and optimize your applications on the RepoCloud platform.

## Overview

RepoCloud simplifies cloud deployment and management by providing an intuitive interface and powerful automation tools. Whether you're deploying a simple blog or a complex multi-tier application, this guide will help you make the most of the platform's capabilities.

## Key Topics

<CardGroup>
  <Card title="Deployment Basics" icon="rocket" href="/user-guide/deployment-basics">
    Learn the fundamentals of deploying applications on RepoCloud
  </Card>

  <Card title="One-Click Deployment" icon="bolt" href="/user-guide/one-click-deployment">
    Deploy applications with minimal configuration using our one-click templates
  </Card>

  <Card title="Managing Instances" icon="server" href="/user-guide/managing-instances">
    Monitor and manage your running application instances
  </Card>

  <Card title="Custom Domains" icon="globe" href="/user-guide/custom-domains">
    Configure custom domains for your applications
  </Card>

  <Card title="Scaling" icon="chart-line" href="/user-guide/scaling">
    Learn how to scale your applications to handle increased load
  </Card>

  <Card title="Updates" icon="arrows-rotate" href="/user-guide/updates">
    Keep your applications updated with the latest features and security patches
  </Card>

  <Card title="Environment Variables" icon="gear" href="/user-guide/environment-variables">
    Configure your applications through environment variables
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/user-guide/troubleshooting">
    Resolve common issues with your RepoCloud applications
  </Card>
</CardGroup>

## Getting Started

If you're new to RepoCloud, we recommend starting with the [Deployment Basics](/user-guide/deployment-basics) guide, which covers the fundamental concepts and steps for deploying your first application. Then, explore the [Managing Instances](/user-guide/managing-instances) section to learn how to monitor and manage your deployed applications.

For those looking to deploy specific applications quickly, check out the [One-Click Deployment](/user-guide/one-click-deployment) guide for our streamlined deployment templates.

## Need Help?

If you encounter any issues or have questions that aren't addressed in this guide, please contact our support team at [team@repocloud.io](mailto:team@repocloud.io).


# Managing Instances
Source: https://docs.repocloud.io/user-guide/managing-instances

Learn how to monitor, maintain, and manage your deployed applications

## Instance Management

Once you've deployed an application on RepoCloud, you'll need to monitor, maintain, and manage it effectively. This guide covers all the essential management tasks available through the RepoCloud dashboard.

<Note>
  The RepoCloud dashboard provides a comprehensive interface for managing all aspects of your deployed applications.
</Note>

## Dashboard Overview

Your dashboard lists all of your projects under the **Projects** tab, alongside **Settings** (profile and two-factor authentication), **Referrals** (affiliate program), and **Billing** (credit balance, auto recharge, and usage history). Clicking "Manage" on any project opens its management page, which provides these tools:

<CardGroup>
  <Card title="Status & Usage" icon="chart-simple">
    See the instance status (e.g., "Online") and, on autoscaling instances, view the usage chart showing which resource tier your app has used over time
  </Card>

  <Card title="Environment Variables" icon="gear">
    Edit your application's environment variables with the "Edit Env Vars" button
  </Card>

  <Card title="Updates" icon="arrows-rotate">
    Update to the latest version with "Rebuild / Update", or pin a specific version with "Edit Docker Image"
  </Card>

  <Card title="Custom Domains" icon="globe">
    Connect your own domain with the "Add Custom Domain" button
  </Card>

  <Card title="Logs" icon="file-lines">
    View application logs for troubleshooting with the "View Logs" button
  </Card>

  <Card title="Lifecycle Controls" icon="power-off">
    Rename your project, pause the server, or delete it entirely
  </Card>
</CardGroup>

### VPS Instance Management

VPS instances (Ubuntu, Coolify, Dokploy, OpenClaw, Hermes Agent) have a dedicated management page with additional controls:

<CardGroup>
  <Card title="Power Controls" icon="power-off">
    Power off, power on, and reboot your VPS directly from the dashboard
  </Card>

  <Card title="Serial Console" icon="terminal">
    Access a browser-based serial console for direct server interaction without SSH
  </Card>

  <Card title="SSH Keys" icon="key">
    Add and manage SSH keys for root access, shared across all your VPS instances
  </Card>

  <Card title="Root Password" icon="lock">
    View and reset the root SSH password at any time
  </Card>

  <Card title="Resize" icon="up-right-and-down-left-from-center">
    Change your server's CPU, RAM, and disk tier without redeploying
  </Card>

  <Card title="Snapshots" icon="camera">
    Create point-in-time backups (up to 5 per instance) at \$0.10/GB/month
  </Card>
</CardGroup>

## Common Management Tasks

### Monitoring Your Instance

RepoCloud provides several monitoring capabilities:

1. **Resource Tier Tracking**: On autoscaling instances, click "View Usage Chart" to see which resource tier your application has used hour by hour
2. **Status Checks**: The management page and dashboard show whether your instance is online
3. **Application Logs**: Click "View Logs" to inspect your application's output, with a "Refresh Logs" button to pull the latest entries
4. **Platform Status**: Check [status.repocloud.io](https://status.repocloud.io) for the health of all RepoCloud server clusters

<Note>
  Resource tier tracking is particularly useful when using autoscaling, as it helps you understand how resources are being allocated and billed on an hourly basis.
</Note>

### Pausing and Deleting Instances

You can control the state of your instance from the dashboard:

* **Pause Server**: Temporarily halt all operations (billing continues at 25% of the normal rate)
* **Resume**: Resume a paused instance to full functionality
* **Rebuild / Update**: Recreate the service from scratch by pulling the latest image and discarding cached data, while preserving your persistent data

<Warning>
  Pausing an instance reduces billing to 25% of the normal rate, as some resources remain allocated. To stop billing completely, you would need to delete the instance.
</Warning>

### Data Management

We recommend the following practices for managing your application data:

1. Use the application's built-in backup features if available
2. Regularly export important data from your application
3. Store backups externally or download them for safekeeping
4. Use version control systems for code and configurations
5. Document your setup for easy recreation if needed

For example:

* **n8n**: Export your workflows as JSON files from the n8n editor
* **WordPress**: Use a migration or backup plugin to download your entire site, or migrate it to another instance

<Warning>
  For container-based instances, backups are only available through the application's own built-in features, so you are responsible for exporting and safeguarding your own data. VPS instances support snapshots — point-in-time disk backups that can be created from the management page (up to 5 per instance, billed at \$0.10/GB/month). To restore a snapshot, click **Restore** next to it. If newer snapshots exist, the confirmation dialog warns which ones will be permanently destroyed by the rollback. The server restarts during restore (\~10–25 seconds) and the page refreshes automatically when complete.
</Warning>

### Deleting Instances

When you no longer need an instance:

<Steps>
  <Step title="Backup Important Data">
    Ensure you've backed up any important data from the application
  </Step>

  <Step title="Navigate to Instance Management">
    Go to the instance management page for the application you want to delete
  </Step>

  <Step title="Delete Instance">
    Click the "Delete Server" button and confirm the deletion. If you're deleting because of a problem with the application, you can optionally report the error details in the confirmation dialog to help us improve the template.
  </Step>
</Steps>

<Warning>
  Instance deletion is permanent and cannot be undone. All data associated with the instance will be permanently deleted.
</Warning>

## Application Management

Different applications offer different management interfaces within the application itself. You can access these through the application's web interface:

<AccordionGroup>
  <Accordion title="Content Management Systems">
    Most CMS platforms like WordPress provide admin dashboards for managing content, users, themes, and plugins.
  </Accordion>

  <Accordion title="Project Management Tools">
    Tools like Jira and Trello offer configuration options through their web interface for workflow customization.
  </Accordion>

  <Accordion title="E-commerce Platforms">
    Platforms like WooCommerce and Magento include store management, product catalog, and order processing interfaces.
  </Accordion>
</AccordionGroup>

## Troubleshooting

If you encounter issues with your instance:

1. Check the application logs ("View Logs") for error messages
2. On autoscaling instances, check the usage chart to see whether your instance is hitting its resource limits
3. Use "Rebuild / Update" to recreate the instance if it's unresponsive (your persistent data is preserved)
4. Check for recent changes or updates that might have caused the issue
5. Consult the [troubleshooting guide](/user-guide/troubleshooting) for common solutions

## Next Steps

<CardGroup>
  <Card title="Custom Domains" icon="globe" href="/user-guide/custom-domains">
    Learn how to set up custom domains for your applications
  </Card>

  <Card title="Scaling Resources" icon="chart-line" href="/user-guide/scaling">
    Discover how to scale your application resources
  </Card>

  <Card title="Application Updates" icon="arrows-rotate" href="/user-guide/updates">
    Keep your applications secure and up-to-date
  </Card>

  <Card title="Environment Variables" icon="gear" href="/user-guide/environment-variables">
    Configure your applications with environment variables
  </Card>
</CardGroup>


# One-Click Deployment
Source: https://docs.repocloud.io/user-guide/one-click-deployment

Deploy applications instantly with RepoCloud's one-click deployment feature

## One-Click Deployment

RepoCloud's one-click deployment feature allows you to launch fully-configured applications in minutes without complex setup or technical knowledge.

## How It Works

RepoCloud's one-click deployment process simplifies what would traditionally require hours or days of DevOps work into a streamlined, user-friendly experience:

<Steps>
  <Step title="Browse the Marketplace">
    Explore our [marketplace](https://repocloud.io/results) to find the application you want to deploy.
  </Step>

  <Step title="Select an Application">
    Click on an application to view its details, features, and available options, then click "Deploy Now".
  </Step>

  <Step title="Configure Settings">
    Enter a project name, keep autoscaling enabled or choose a fixed server size, and fill in any application-specific settings. For most applications, the default settings work well for getting started.

    <Note>
      Our platform automatically configures the optimal settings for each application, but you can customize them according to your needs.
    </Note>
  </Step>

  <Step title="Launch Your Application">
    Click the "Deploy App" button to launch your application. The deployment process typically takes 3-7 minutes.
  </Step>
</Steps>

## Benefits of One-Click Deployment

<CardGroup>
  <Card title="Time Savings" icon="clock">
    Deploy in minutes instead of hours or days of manual setup
  </Card>

  <Card title="Reduced Complexity" icon="wand-magic-sparkles">
    No need to understand containerization, networking, or server administration
  </Card>

  <Card title="Optimized Configurations" icon="sliders">
    Pre-configured for optimal performance and security
  </Card>

  <Card title="Instant Productivity" icon="bolt">
    Start using your application immediately after deployment
  </Card>
</CardGroup>

## Deployment Examples

### WordPress Deployment

<Steps>
  <Step title="Select WordPress">
    Find WordPress in our marketplace and click on it to view details.
  </Step>

  <Step title="Choose Resources">
    Keep autoscaling enabled, or disable it and select a resource tier (we recommend at least 1GB RAM for WordPress).
  </Step>

  <Step title="Enter Project Name and Deploy">
    Enter a name for your project and click "Deploy App" to start the deployment process (typically 3-7 minutes).
  </Step>

  <Step title="Complete Setup Wizard">
    Once deployment is complete, use the provided URL to access your WordPress installation and follow the setup wizard to configure your site.
  </Step>
</Steps>

## After Deployment

Once your application is deployed, you can:

1. **Add a custom domain**: Connect your own domain name to your application
2. **Configure settings**: Adjust application settings through the application's admin interface or the "Edit Env Vars" button
3. **Monitor usage**: Track your instance's resource tier usage with the "View Usage Chart" button (available on autoscaling instances)
4. **Update**: Keep your application up-to-date with the one-click "Rebuild / Update" button
5. **Pause when idle**: Pause an instance you're not using to reduce its billing to 25% of the normal rate

## Limitations

While one-click deployments are powerful, there are some limitations to be aware of:

* **Customization**: Some advanced customizations may not be available through the interface
* **Shell Access**: Direct shell access is not provided for standard applications
* **Custom Software**: Only applications in our marketplace can be deployed with one click

<Note>
  For use cases requiring more control, consider our platform apps like [Coolify](/platforms/coolify) or [Dokploy](/platforms/dokploy), which provide advanced capabilities including root access and custom application deployment.
</Note>

## FAQ

<AccordionGroup>
  <Accordion title="Can I deploy multiple applications at once?">
    Each application requires a separate deployment. However, you can deploy as many different applications as needed for your projects.
  </Accordion>

  <Accordion title="How are my applications isolated?">
    Each application runs in its own isolated container, ensuring that one application cannot affect the performance or security of another.
  </Accordion>

  <Accordion title="Can I migrate existing data to my deployment?">
    Yes, most applications provide ways to import existing data. For example, WordPress has import/export plugins, and databases have import tools.
  </Accordion>

  <Accordion title="What happens if deployment fails?">
    If a deployment fails, you won't be charged. Our system will provide information about the failure, and you can try again with adjusted settings if needed.
  </Accordion>

  <Accordion title="Can I change settings after deployment?">
    Yes, many settings can be changed through the application's admin interface or through environment variables in the RepoCloud dashboard.
  </Accordion>
</AccordionGroup>


# Scaling Resources
Source: https://docs.repocloud.io/user-guide/scaling

Learn how RepoCloud matches resources to your application's demand

## Scaling on RepoCloud

As your application's needs evolve, its resource allocation should keep up. RepoCloud's approach to scaling is chosen when you deploy: you either enable elastic autoscaling (the default) and let the platform adjust resources for you, or you pick a fixed server size that you can scale manually later.

<Tip>
  For most applications we recommend keeping autoscaling enabled. It matches your resource allocation to actual usage automatically, with no manual intervention required.
</Tip>

## Scaling Options

RepoCloud provides two resource allocation modes, selected on the deployment page:

<CardGroup>
  <Card title="Elastic Autoscaling" icon="chart-line">
    The default. Automatically adjusts compute and storage resources based on actual usage, with hourly billing
  </Card>

  <Card title="Fixed Server Size" icon="lock">
    Disable the autoscale toggle at deployment to select a specific resource tier with a predictable monthly maximum
  </Card>
</CardGroup>

## Elastic Autoscaling

Elastic Autoscaling is RepoCloud's intelligent resource management system that continuously monitors your application's resource utilization and automatically adjusts resources as needed.

### How Autoscaling Works

<Steps>
  <Step title="Resource Monitoring">
    Our system continuously monitors the CPU, RAM, and storage utilization of your application.
  </Step>

  <Step title="Automatic Adjustment">
    When resource usage increases, your instance is moved to a larger resource tier to maintain performance.
  </Step>

  <Step title="Scaling Down">
    During periods of lower activity, resources scale down automatically to reduce costs.
  </Step>

  <Step title="Hourly Billing">
    You're billed on an hourly basis for the resource tier your instance actually used each hour, rather than a fixed monthly amount.
  </Step>
</Steps>

### Benefits of Autoscaling

* **Cost Efficiency**: Pay only for the resources you actually use
* **Performance Optimization**: Automatically handle traffic spikes without manual intervention
* **Resource Efficiency**: Reduce waste during low-traffic periods
* **Simplicity**: No need to predict exact resource requirements

### Enabling Autoscaling

Autoscaling is enabled with the "Autoscale compute and storage resources" toggle on the deployment page, and it's switched on by default:

<Steps>
  <Step title="Choose Your Application">
    Select an application from the marketplace and click "Deploy Now".
  </Step>

  <Step title="Keep the Autoscale Toggle Enabled">
    Leave the "Autoscale compute and storage resources" toggle switched on.
  </Step>

  <Step title="Deploy">
    Click "Deploy App". Your instance will scale between resource tiers automatically from then on.
  </Step>
</Steps>

### Tracking Autoscaling Activity

To see how your instance has been scaling:

<Steps>
  <Step title="Open Instance Management">
    Go to your application's management page in the RepoCloud dashboard. The "Server Size" field will show "Autoscaling".
  </Step>

  <Step title="View Usage Chart">
    Click "View Usage Chart" to see which resource tier your application occupied hour by hour. This is exactly what your hourly billing is based on.
  </Step>
</Steps>

## Fixed Server Sizes

If you prefer predictable, fixed resources, disable the autoscale toggle on the deployment page and select a specific server size.

### Available Server Sizes

| Tier | RAM   | vCPU | SSD Storage | Hourly Price | Monthly Price |
| ---- | ----- | ---- | ----------- | ------------ | ------------- |
| 1    | 1 GB  | 1    | 20 GB       | \$0.0042     | \$3.00        |
| 2    | 2 GB  | 1    | 30 GB       | \$0.0083     | \$6.00        |
| 3    | 2 GB  | 2    | 40 GB       | \$0.0125     | \$9.00        |
| 4    | 4 GB  | 2    | 40 GB       | \$0.0167     | \$12.00       |
| 5    | 8 GB  | 4    | 80 GB       | \$0.0333     | \$24.00       |
| 6    | 16 GB | 8    | 160 GB      | \$0.0667     | \$48.00       |
| 7    | 32 GB | 16   | 320 GB      | \$0.1333     | \$96.00       |

<Note>
  Some applications have minimum resource requirements, so the smallest tiers may be unavailable for them on the deployment page. Platform apps such as Coolify and Dokploy, for example, require at least Tier 4 (4 GB RAM / 2 vCPU).
</Note>

### Adding Extra Storage

If you need more storage than your tier includes, use the "Add Extra SSD" option on the deployment page. Additional NVMe SSD storage costs \$0.10 per GB per month.

### Changing a Fixed Server Size

Instances deployed with a fixed server size can be scaled manually: open your application's management page and change the server size to a different tier. You can also switch a fixed-size instance over to autoscaling at any time.

<Warning>
  Switching modes is one-directional: a fixed-size (manual scaling) instance can be moved to autoscaling, but an autoscaled instance cannot be switched back to a fixed server size. If you may want manual control later, deploy with a fixed size.
</Warning>

## Choosing the Right Scaling Method

<AccordionGroup>
  <Accordion title="When to Choose Autoscaling">
    Autoscaling is ideal for:

    * Applications with variable traffic patterns
    * Websites with occasional traffic spikes
    * Cost-sensitive deployments
    * Development and testing environments
    * When you're unsure about exact resource requirements
  </Accordion>

  <Accordion title="When to Choose a Fixed Size">
    A fixed server size works best for:

    * Applications with predictable, consistent traffic
    * Workloads requiring guaranteed resources at all times
    * Situations where budget predictability is important
    * Applications with specific performance requirements
  </Accordion>
</AccordionGroup>

## Scaling Limitations

Be aware of these scaling limitations:

* **Minimum Resources**: Each application type has minimum resource requirements, which may disable the smallest tiers at deployment
* **Maximum Tier**: Resources cannot exceed the highest available tier (32 GB RAM, 16 vCPU)
* **Platform Apps**: [Platform Apps](/platforms/introduction) (Coolify and Dokploy) cannot use autoscaling, because autoscaling is not available for backends that require a dedicated IPv4 address and root access

## Next Steps

<CardGroup>
  <Card title="Environment Variables" icon="gear" href="/user-guide/environment-variables">
    Learn how to configure your application through environment variables
  </Card>

  <Card title="Updates" icon="arrows-rotate" href="/user-guide/updates">
    Keep your application updated with the latest features and security patches
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/user-guide/troubleshooting">
    Resolve common issues with your RepoCloud applications
  </Card>
</CardGroup>


# Troubleshooting
Source: https://docs.repocloud.io/user-guide/troubleshooting

Resolve common issues and problems with your RepoCloud applications

## Troubleshooting Guide

Even with RepoCloud's streamlined deployment and management experience, you may occasionally encounter issues with your applications. This guide will help you diagnose and resolve common problems.

## General Troubleshooting Process

When facing any issue with your RepoCloud application, follow this general process:

<Steps>
  <Step title="Check Application Status">
    Verify if your application is showing as "Online" in the dashboard
  </Step>

  <Step title="Review Logs">
    Check application logs for error messages or warnings
  </Step>

  <Step title="Monitor Resources">
    Ensure your application has sufficient resources (CPU, RAM, storage)
  </Step>

  <Step title="Verify Configuration">
    Check that environment variables and settings are properly configured
  </Step>

  <Step title="Rebuild the Application">
    Use the "Rebuild / Update" button to recreate the instance from a fresh image (your persistent data is preserved)
  </Step>

  <Step title="Contact Support">
    If the issue persists, contact RepoCloud support at [team@repocloud.io](mailto:team@repocloud.io)
  </Step>
</Steps>

## Common Issues and Solutions

### Application Access Issues

<AccordionGroup>
  <Accordion title="Application Not Loading">
    If your application URL returns an error or doesn't load:

    **Possible Causes:**

    * Application is still deploying
    * Application has crashed
    * Resource limitations

    **Solutions:**

    1. Wait a few minutes if the application was recently deployed
    2. Check application logs for errors
    3. Ensure the application has sufficient resources
    4. Rebuild the application from the dashboard ("Rebuild / Update")
    5. Verify that all required environment variables are set correctly
  </Accordion>

  <Accordion title="SSL Certificate Errors">
    If your browser shows SSL/certificate warnings:

    **Possible Causes:**

    * New custom domain hasn't completed verification
    * SSL certificate is still being issued
    * DNS configuration issues

    **Solutions:**

    1. Verify your DNS settings are correctly configured
    2. Allow up to 24 hours for SSL certificate issuance and propagation
    3. Ensure you're using https\:// in the URL
    4. Check the domain verification status in the dashboard
  </Accordion>

  <Accordion title="Slow Application Performance">
    If your application is loading slowly:

    **Possible Causes:**

    * Insufficient resources
    * High database load
    * Inefficient application code
    * Network latency

    **Solutions:**

    1. On autoscaling instances, check the usage chart to see if your instance is at its resource ceiling; autoscaled instances add resources automatically as load grows
    2. Enable caching if your application supports it
    3. Optimize database queries and indexes
    4. If you're on a small fixed tier, scale it up manually or switch it to autoscaling from the management page
  </Accordion>
</AccordionGroup>

### Deployment Issues

<AccordionGroup>
  <Accordion title="Deployment Fails">
    If your application fails to deploy:

    **Possible Causes:**

    * Invalid configuration
    * Resource constraints
    * Temporary platform issues

    **Solutions:**

    1. Check the deployment logs for specific error messages
    2. Verify that all required environment variables are correctly set
    3. Ensure your resource tier is sufficient for the application
    4. Try deploying again after a few minutes
  </Accordion>

  <Accordion title="Deployment Stuck">
    If your deployment seems stuck for a long time:

    **Possible Causes:**

    * Large application data
    * Network issues
    * Platform resource constraints

    **Solutions:**

    1. For initial deployments, large applications may take up to 10 minutes
    2. Check the [platform status page](https://status.repocloud.io) for any ongoing incidents
    3. Contact support if the issue persists
  </Accordion>

  <Accordion title="Application Crashes After Deployment">
    If your application deploys successfully but crashes shortly after:

    **Possible Causes:**

    * Missing or incorrect environment variables
    * Application bugs
    * Incompatible dependencies
    * Resource limitations

    **Solutions:**

    1. Check application logs for error messages
    2. Verify all required environment variables are set properly
    3. Ensure your application has sufficient resources
    4. For custom applications, verify compatibility with the container environment
  </Accordion>
</AccordionGroup>

### Database Issues

<AccordionGroup>
  <Accordion title="Database Connection Errors">
    If your application can't connect to its database:

    **Possible Causes:**

    * Incorrect connection string
    * Database service is not running
    * Authentication issues

    **Solutions:**

    1. Verify database environment variables (host, user, password, database name)
    2. Check the application logs for database-related errors
    3. Rebuild the instance to restart the application and its bundled database service
    4. Ensure the database has not reached its connection limit
  </Accordion>

  <Accordion title="Database Performance Issues">
    If database operations are slow:

    **Possible Causes:**

    * Insufficient resources
    * Missing indexes
    * Inefficient queries
    * Database size issues

    **Solutions:**

    1. Ensure your instance has sufficient resources (autoscaled instances add resources automatically under load)
    2. Optimize database indexes
    3. Review and optimize queries
    4. Consider implementing caching
    5. Purge unnecessary data or logs
  </Accordion>

  <Accordion title="Data Loss or Corruption">
    If you experience data loss or corruption:

    **Possible Causes:**

    * Application bugs
    * Disk space issues
    * Unexpected shutdowns

    **Solutions:**

    1. Restore from a backup if available
    2. Check for disk space issues
    3. Verify application logs for errors during write operations
    4. Contact support for assistance with data recovery
  </Accordion>
</AccordionGroup>

### Update and Scaling Issues

<AccordionGroup>
  <Accordion title="Update Fails">
    If an application update (rebuild) fails:

    **Possible Causes:**

    * Incompatible configuration
    * Resource constraints
    * Application data migration issues

    **Solutions:**

    1. Check logs for specific error messages
    2. Verify that your configuration is compatible with the new version
    3. Ensure sufficient resources for the update process
    4. Try updating again after a few minutes
    5. Contact support if the issue persists
  </Accordion>

  <Accordion title="Scaling Problems">
    If your application struggles under load despite autoscaling:

    **Possible Causes:**

    * Application not designed to utilize additional resources
    * Application-level bottlenecks (e.g., database locks, single-threaded workloads)
    * Configuration issues

    **Solutions:**

    1. Check application logs during periods of high load
    2. Check the usage chart to confirm the instance is actually scaling up
    3. Verify the application can utilize additional resources
    4. Ensure database connections can handle increased load
    5. Consider application-specific optimizations for scaling
  </Accordion>
</AccordionGroup>

### Custom Domain Issues

<AccordionGroup>
  <Accordion title="Custom Domain Not Working">
    If your custom domain doesn't connect to your application:

    **Possible Causes:**

    * Incorrect DNS configuration
    * Domain verification pending
    * DNS propagation delay

    **Solutions:**

    1. Verify your DNS records match the ones provided in the dashboard
    2. Check domain verification status in the dashboard
    3. Allow up to 24-48 hours for DNS propagation
    4. Test your DNS configuration using a tool like [DNSChecker](https://dnschecker.org)
  </Accordion>

  <Accordion title="Mixed Content Warnings">
    If your site shows mixed content warnings:

    **Possible Causes:**

    * Resources loaded over HTTP instead of HTTPS
    * Hardcoded URLs in application code

    **Solutions:**

    1. Update your application to use relative URLs or HTTPS URLs
    2. Configure proper HTTP to HTTPS redirects
    3. Check for hardcoded HTTP URLs in your application settings
  </Accordion>
</AccordionGroup>

## Accessing and Understanding Logs

Logs are a crucial tool for troubleshooting. RepoCloud provides access to application logs through the dashboard:

<Steps>
  <Step title="Navigate to Instance Management">
    Go to your application's management page
  </Step>

  <Step title="Open the Logs View">
    Click the "View Logs" button
  </Step>

  <Step title="Browse the Logs">
    Browse the log output for error messages, warnings, or other relevant information. Use your browser's search (Ctrl/Cmd+F) to find specific entries.
  </Step>

  <Step title="Refresh When Needed">
    Click "Refresh Logs" to pull the latest entries
  </Step>
</Steps>

<Tip>
  Look for error messages that include terms like "Error", "Exception", "Failed", or "Fatal" in the logs. These often provide valuable clues about what's going wrong.
</Tip>

## Contact Support

If you've tried the troubleshooting steps and still can't resolve your issue, don't hesitate to contact RepoCloud support:

* **Email**: [team@repocloud.io](mailto:team@repocloud.io)
* **Contact Form**: [https://repocloud.io/contact](https://repocloud.io/contact)

When contacting support, please include:

1. Your account information
2. The application name and URL
3. A detailed description of the issue
4. Steps you've taken to troubleshoot
5. Any relevant error messages or screenshots
6. When the issue started occurring

## Platform Status

Check the RepoCloud status page to see if there are any ongoing platform issues or maintenance that might be affecting your applications:

[https://status.repocloud.io](https://status.repocloud.io)

## Application-Specific Troubleshooting

Different applications have their own common issues and troubleshooting approaches. Here are some application-specific resources:

<CardGroup>
  <Card title="WordPress Troubleshooting" icon="wordpress">
    [WordPress Support](https://wordpress.org/support/)
  </Card>

  <Card title="MySQL Troubleshooting" icon="database">
    [MySQL Documentation](https://dev.mysql.com/doc/refman/8.0/en/troubleshooting.html)
  </Card>

  <Card title="Node.js Troubleshooting" icon="node">
    [Node.js Debugging Guide](https://nodejs.org/en/docs/guides/debugging-getting-started)
  </Card>

  <Card title="Nginx Troubleshooting" icon="server">
    [Nginx Debugging](https://docs.nginx.com/nginx/admin-guide/monitoring/debugging/)
  </Card>
</CardGroup>

## Preventative Measures

Prevent issues before they happen with these best practices:

1. **Regular Backups**: Ensure you have recent backups of critical data
2. **Monitoring**: Regularly check your application's health and performance
3. **Updates**: Keep your application updated with the latest version
4. **Resource Planning**: Monitor usage and scale before you hit resource limits
5. **Documentation**: Maintain documentation about your application's configuration and customizations


# Application Updates
Source: https://docs.repocloud.io/user-guide/updates

Keep your applications secure and up-to-date with RepoCloud's update system

## Keeping Applications Updated

Maintaining up-to-date applications is crucial for security, performance, and accessing the latest features. RepoCloud simplifies this process with a one-click update system that allows you to easily keep your applications current while preserving your data and configurations.

<Tip>
  Regular updates are essential for maintaining the security, performance, and functionality of your applications. RepoCloud's one-click update system makes this process simple and reliable.
</Tip>

## RepoCloud's Update Philosophy

RepoCloud maintains a repository of application templates that are regularly updated to include the latest stable versions of all applications in our marketplace. Our approach to updates prioritizes:

<CardGroup>
  <Card title="Security" icon="shield-halved">
    Security patches and fixes are prioritized in our update workflow
  </Card>

  <Card title="Stability" icon="check-double">
    We deploy stable, tested versions rather than bleeding-edge releases
  </Card>

  <Card title="Data Preservation" icon="database">
    Updates are designed to preserve existing data and configurations
  </Card>

  <Card title="Simplicity" icon="wand-magic-sparkles">
    The update process is user-friendly and requires minimal effort
  </Card>
</CardGroup>

## The "Rebuild / Update" Feature

The primary method for updating your applications on RepoCloud is the "Rebuild / Update" button on your instance's management page. Rebuilding recreates the service from scratch by pulling the latest image and discarding any cached data, ensuring a fresh setup while preserving your persistent data.

### How Rebuilding Works

<Steps>
  <Step title="Initiate Rebuild">
    RepoCloud pulls the latest version of your application's Docker image
  </Step>

  <Step title="Preserve Data">
    Your application data stored in persistent volumes is preserved
  </Step>

  <Step title="Apply Configuration">
    Your custom configurations and environment variables are maintained
  </Step>

  <Step title="Restart Application">
    The application restarts with the updated image
  </Step>
</Steps>

<Note>
  The rebuild process typically takes 3-7 minutes, with downtime limited to the restart.
</Note>

## Performing an Update

Updating your application is straightforward:

<Steps>
  <Step title="Access Instance Management">
    Navigate to your application's management page in the RepoCloud dashboard
  </Step>

  <Step title="Initiate Rebuild">
    Click the "Rebuild / Update" button
  </Step>

  <Step title="Confirm Action">
    Confirm the rebuild when prompted
  </Step>

  <Step title="Wait for the Rebuild to Complete">
    Your application will come back online within a few minutes; you can check its logs with "View Logs" if you want to follow along
  </Step>
</Steps>

## Pinning a Specific Version

By default, rebuilding pulls the latest stable image. If you need a specific version of your application instead, use the "Edit Docker Image" button on the management page:

<Steps>
  <Step title="Open Edit Docker Image">
    Click "Edit Docker Image" on your instance's management page
  </Step>

  <Step title="Enter the Version Tag">
    The base image is fixed (e.g., `flowiseai/flowise:`); enter the version tag you want to run
  </Step>

  <Step title="Save Changes">
    Click "Save Changes" and confirm. Your app will restart with the specified version, which typically takes 3-7 minutes.
  </Step>
</Steps>

<Tip>
  Version pinning is also the way to roll back if a new release causes problems: enter the previous version's tag and save. Note that rolling back does not undo database schema migrations the newer version may have already applied.
</Tip>

## Update Frequency

RepoCloud regularly refreshes application templates so that rebuilds pull current stable releases. Because rebuilds pull the latest published image directly, you receive the newest stable version of your application whenever you rebuild.

<Warning>
  While the rebuild process is designed to be safe, it's always good practice to create a backup of critical data before performing any update.
</Warning>

## What Gets Updated

When you rebuild an application, the following components are updated:

* **Application Code**: The core application is updated to the latest stable version
* **Dependencies**: Associated libraries and dependencies are updated
* **Base System**: The underlying container system may be updated for security and performance
* **Configuration**: Default configurations may be updated to reflect best practices

The following elements are preserved during updates:

* **User Data**: All user-generated content and database information
* **Custom Configurations**: Your environment variables and custom settings
* **Domains**: Any custom domains and SSL certificates remain configured
* **User Accounts**: Application user accounts and permissions

## Major Version Updates

Sometimes, applications undergo significant changes between major versions that require special attention:

<AccordionGroup>
  <Accordion title="Data Migration">
    Major version updates may include database schema changes that require data migration. RepoCloud attempts to handle these automatically, but some applications may require manual intervention.
  </Accordion>

  <Accordion title="Breaking Changes">
    Major updates can introduce breaking changes to APIs or features. Review the update notes carefully before proceeding with major version updates.
  </Accordion>

  <Accordion title="Plugin Compatibility">
    For applications that support plugins or extensions, major updates may affect compatibility. You may need to update or replace incompatible plugins after updating.
  </Accordion>
</AccordionGroup>

<Tip>
  For applications with extensive customizations or critical business functions, consider testing the update in a separate instance before updating your production environment.
</Tip>

## Troubleshooting Updates

If you encounter issues during or after an update:

<AccordionGroup>
  <Accordion title="Failed Update">
    If an update fails to complete:

    * Check the error message in the update logs
    * Verify that your application has sufficient resources
    * Attempt the rebuild again after a few minutes
    * Contact support if the issue persists
  </Accordion>

  <Accordion title="Post-Update Issues">
    If your application behaves unexpectedly after an update:

    * Check application-specific logs for errors
    * Verify that your custom configurations are still correctly applied
    * Consider restoring from a backup if available
    * For complex issues, consult the application's documentation or contact support
  </Accordion>

  <Accordion title="Reverting Updates">
    If you need to revert to a previous version:

    * Use "Edit Docker Image" to pin the previous version's tag (see [Pinning a Specific Version](#pinning-a-specific-version) above)
    * Restore from a backup if the newer version already migrated your data
    * Contact support for assistance with complex cases
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="Environment Variables" icon="gear" href="/user-guide/environment-variables">
    Learn how to configure your applications with custom settings
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/user-guide/troubleshooting">
    Resolve common issues with your applications
  </Card>

  <Card title="Platform Apps" icon="server" href="/platforms/introduction">
    Explore our platform apps for advanced control and customization
  </Card>
</CardGroup>