TinyDeployGitHub
Early development · Self-hosted

Built for projects that fit on a tiny server.

A simple way to run your Docker apps on your own server.

Explore on GitHub Get started
curl -fsSL https://download.tinydeploy.site/install.sh | sudo bash

Just the useful parts

Self-hosting, without the sprawl.

Local-first by design
Applications run in local Docker containers. Caddy is the web entry point when you choose to expose a service.
Small and modular
Start with the essentials and enable optional capabilities through independent feature flags.
You stay in control
Your server, repositories, Docker setup, and configuration remain understandable and under your control.
Cloudflare is optional
Use a local-only or LAN setup, public routing, or an outbound Cloudflare Tunnel when it suits your needs.
Safe-mode recovery
Recover from a broken module or theme by starting the panel in safe mode and disabling it.
Privacy first
The website has no trackers. Product telemetry is planned to be anonymous and opt-in.

From server to running app

How it works

  1. 01

    Install TinyDeploy and create your admin account.

  2. 02

    Add an application from Git or uploaded source.

  3. 03

    TinyDeploy builds and runs it in a local container.

  4. 04

    Choose a local hostname or configure public access when needed.

Try it when you're ready

One command to get started.

For supported Linux servers. Review the installer and project status before running it.

Early development: a stable release is not available yet, and features described in the roadmap may not be implemented. Check the documentation for current installation status.

curl -fsSL https://download.tinydeploy.site/install.sh | sudo bash
Read the documentation

Small by design

A focused path, not a feature race.

For one developer, one server, and a few personal apps. This plan stays focused on practical self-hosting—not enterprise teams, multi-server fleets, or feature count.

  1. Phase 01In progress
    Barebones core
    Establish the installer, platform detection, authentication, feature and module systems, and the core dashboard.
    • Core platform
    • Dashboard shell
    • Module system
    • Core recovery
    • Telemetry and privacy

  2. Phase 02Not started
    Application deployment
    Create applications from uploaded source or container images and run them as local-only containers.
    • app_deployment
    • manual_upload
    • container_image_deploy

  3. Phase 03Not started
    Local routing
    Route applications through Caddy using local hostnames, without requiring public exposure.
    • local_hostnames

  4. Phase 04Not started
    Firewall
    Configure a supported firewall and make network exposure visible and safer by default.
    • firewall

  5. Phase 05Not started
    File management
    Add safe file management for deployed application content.
    • file_editor

  6. Phase 06Not started
    Git deployment
    Deploy directly from Git repositories, with additional GitHub integration as an optional capability.
    • git_integration
    • github_integration

  7. Phase 07Not started
    Public exposure
    Allow selected applications to be exposed publicly through Caddy.
    • public_http

  8. Phase 08Not started
    Cloudflare Tunnel
    Offer Cloudflare Tunnel as an optional way to reach services without opening inbound ports.
    • cloudflare_tunnel

  9. Phase 09Not started
    Updates and operations
    Add automatic updates alongside backup, restore, audit, upgrade, and rollback operations.
    • automatic_updates
    • backup and restore
    • audit log
    • upgrade and rollback

  10. Phase 10Not started
    Custom themes
    Support exporting, editing, uploading, and applying custom dashboard themes.
    • custom_themes

  11. Phase 11Not started
    Advanced and optional
    Consider advanced Caddy configuration, two-factor authentication, metrics, and ratings after the core is stable.
    • custom_caddy_snippets
    • totp_mfa
    • metrics
    • ratings

Good to know

Frequently asked questions