App Store template
Rclone icon

Rclone

Rclone is a command-line program to manage, sync, and serve files across cloud storage providers.

Launch in your Sealos workspace.

Rclone template preview
Template previewFull screenshot
Template deployments
15 on Sealos
Deployment
Your own instance
Category
Storage

About this template

Overview

Rclone is a storage management tool for syncing, copying, mounting, and serving files across cloud storage providers. This template deploys Rclone in rcd mode with the Web GUI and RC API exposed through HTTPS on Sealos Cloud.

From the documentation

Rclone runs as a single StatefulSet using the official rclone/rclone image. The template starts rclone rcd with --rc-web-gui, HTTP Basic Auth credentials from the deployment form, and persistent volumes for /config and /data.

How to deploy Rclone

  1. Choose Deploy now to start Rclone in your Sealos workspace.
  2. Review rc_user, rc_password in the deployment form.
  3. Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the Rclone template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.

Template configuration and setup

Access after deployment

Use the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.

Hosting and billing

Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.

Compare Sealos resource plans
Read full documentationCollapse documentation

For current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.

Deploy and Host Rclone on Sealos

Rclone is a storage management tool for syncing, copying, mounting, and serving files across cloud storage providers. This template deploys Rclone in rcd mode with the Web GUI and RC API exposed through HTTPS on Sealos Cloud.

Rclone Screenshot

About Hosting Rclone

Rclone runs as a single StatefulSet using the official rclone/rclone image. The template starts rclone rcd with --rc-web-gui, HTTP Basic Auth credentials from the deployment form, and persistent volumes for /config and /data.

The Web GUI and RC API share the same public URL. Use the configured username and password to access both the browser UI and API endpoints.

Common Use Cases

  • Cloud storage administration: Configure and inspect remotes from a browser.
  • Transfer automation: Use the RC API to trigger copy, sync, and list operations.
  • Storage migration: Move files between supported providers.
  • Backup operations: Store Rclone configuration and cache on persistent Sealos volumes.

Dependencies for Rclone Hosting

The Sealos template includes the official Rclone container image, persistent configuration storage, persistent cache/data storage, public HTTPS ingress, and Basic Auth inputs.

Deployment Dependencies

Implementation Details

Architecture Components:

  • Rclone rcd: Remote control daemon with Web GUI enabled.
  • Persistent Config: /config/rclone/rclone.conf stores remotes and credentials.
  • Persistent Data: /data stores cache and working files.

Configuration:

  • rc_user and rc_password protect the Web GUI and RC API.
  • The daemon listens on port 5572 inside the cluster and is exposed through HTTPS ingress.
  • Remotes are configured after login through the Web GUI or RC API.

License Information:

Rclone is licensed under the MIT License.

Why Deploy Rclone on Sealos?

Sealos provides automatic HTTPS, persistent storage, and one-click deployment for a browser-accessible Rclone control plane. It is useful for cloud storage operations that need a stable URL and persistent configuration.

Deployment Guide

  1. Open the Rclone template and click Deploy Now.
  2. Configure the RC username and password in the popup dialog.
  3. Wait for deployment to complete, typically 1-2 minutes. After deployment, you will be redirected to the Canvas.
  4. Open the generated application URL and sign in with the configured Basic Auth credentials.

Configuration

After login, create remotes from the Web GUI. You can also call RC API endpoints with the same credentials, for example POST /core/version and POST /config/listremotes.

Additional Resources

License

This template follows the upstream Rclone MIT License.

From launch to everyday operations

Why deploy
on Sealos

A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.

  1. One-click deployment

    Start with a ready-made template. Review its configuration and launch from the Sealos console.

  2. Managed Kubernetes

    Run on managed infrastructure with built-in workload scheduling and recovery.

  3. Automatic HTTPS

    Give your application a public HTTPS endpoint with certificates managed for you.

  4. Persistent storage

    Keep application data on persistent volumes across container restarts.

  5. Room to grow

    Adjust CPU, memory, and replicas from the console as your workload changes.

One template. Connected resources.

You Get the Whole Stack

Sealos provisions the resources defined by your template and brings them together in your workspace.

  • App Service

    Container workloads with configurable CPU, memory, and replicas.

  • Public HTTPS URL

    An address for your app, with managed TLS certificates.

  • Database

    A database provisioned alongside your app when the template calls for one.

  • Persistent Volume

    Storage for the files and data your application needs to keep.

  • Environment Variables

    Application settings and secrets configured in one place.

  • Logs & Metrics

    Inspect container logs and resource usage from the console.

Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.

Explore more production-ready templates.

More