App Store template

Syncthing

Continuous peer-to-peer file synchronization with a browser-based administration interface.

Launch in your Sealos workspace.

Source Deploy guide Website

Syncthing template preview — Template previewFull screenshot

Template deployments: 15 on Sealos
Deployment: Your own instance
Category: Storage

About this template

Overview

Syncthing is a continuous peer-to-peer file synchronization system with a browser-based administration interface. This template deploys Syncthing with persistent /var/syncthing storage and public HTTPS access on Sealos Cloud.

From the documentation

Syncthing synchronizes files directly between devices and keeps device identity, configuration, and synchronized data in its local data directory. The Sealos template runs Syncthing as a StatefulSet so that /var/syncthing persists across restarts.

How to deploy Syncthing

Choose Deploy now to start Syncthing in your Sealos workspace.
Review device_name, gui_username, gui_password in the deployment form.
Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the Syncthing 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 Syncthing on Sealos

Syncthing Screenshot

About Hosting Syncthing

The web GUI is exposed through Sealos HTTPS ingress on port 8384. Sync ports are also defined on the internal Service, and remote devices can be added from the Syncthing GUI after deployment.

Common Use Cases

Private file synchronization: Sync folders between trusted devices without a central SaaS account.
Self-hosted backup workflows: Keep copies of important folders in a Sealos workspace.
Cross-device sharing: Pair desktops, servers, and edge devices through Syncthing device IDs.
Persistent sync node: Run a stable always-on node for personal or team synchronization.

Dependencies for Syncthing Hosting

The Sealos template includes the Syncthing container, StatefulSet, persistent volume, Service ports for GUI and sync traffic, HTTPS Ingress, and App resources.

Deployment Dependencies

Syncthing Website - Product overview
Syncthing Documentation - User and administration docs
Syncthing Docker README - Official Docker guidance
Syncthing GitHub Repository - Source code and issues

Implementation Details

Architecture Components:

Syncthing StatefulSet: Runs syncthing/syncthing:2.1.1.
Persistent Volume: Stores /var/syncthing, including configuration, identity, and synced data.
Service: Exposes GUI traffic on 8384 and sync traffic on 22000.
Ingress and App Entry: Exposes the GUI through the generated Sealos HTTPS URL.

Configuration:

device_name sets the visible device name.
STGUIADDRESS=0.0.0.0:8384 makes the web GUI reachable through Sealos Ingress.
STNODEFAULTFOLDER=true starts without an automatic default sync folder.

License Information:

Syncthing is licensed under the MPL-2.0 License. This Sealos template provides deployment configuration for running Syncthing on Sealos Cloud.

Why Deploy Syncthing on Sealos?

Sealos is an AI-assisted Cloud Operating System built on Kubernetes that unifies deployment and operations. By deploying Syncthing on Sealos, you get one-click deployment, automatic HTTPS, persistent storage, resource controls, and Canvas-based updates for an always-on sync node.

Deployment Guide

Open the Syncthing template and click Deploy Now.
Configure device_name if you want a custom visible device name.
Wait for deployment to complete, typically 2-3 minutes. After deployment, you will be redirected to the Canvas. For later changes, describe your requirements in the AI dialog, or click the relevant resource cards to modify settings.
Open the generated public URL.
In the Syncthing GUI, set a GUI username and password when prompted by Syncthing.
Add remote devices and folders from the Syncthing web interface.

Configuration

After deployment, configure Syncthing through:

Syncthing GUI: Add devices, folders, credentials, and sync preferences.
AI Dialog: Update environment variables or resource settings.
Resource Cards: Adjust CPU, memory, and persistent storage from the Canvas.
Persistent Volume: Keep /var/syncthing to preserve the device ID.

Scaling

Syncthing usually runs as a single stable node because its device identity lives in persistent storage. Increase CPU, memory, or storage when synchronizing larger folders or more devices.

Troubleshooting

GUI asks for credentials

Cause: Syncthing recommends protecting the externally reachable GUI.
Solution: Set a GUI username and password from the Syncthing web interface.

Remote devices cannot connect

Cause: Public peer-to-peer connectivity may require explicit device addresses or relay configuration.
Solution: Add remote device addresses manually in the Syncthing GUI if automatic discovery is insufficient.

Device identity changes

Cause: The persistent volume was removed or replaced.
Solution: Keep the /var/syncthing volume when updating the workload.

Additional Resources

License

This Sealos template is provided as deployment configuration for Sealos users. Syncthing itself is licensed under the MPL-2.0 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.

One-click deployment
Start with a ready-made template. Review its configuration and launch from the Sealos console.
Managed Kubernetes
Run on managed infrastructure with built-in workload scheduling and recovery.
Automatic HTTPS
Give your application a public HTTPS endpoint with certificates managed for you.
Persistent storage
Keep application data on persistent volumes across container restarts.
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.