GhostProvider is source-available, not OSI open-source software. The full text is in LICENSE. What this means:
- Allowed: reading and studying the source, using, modifying, and running the program for personal non-commercial purposes.
- What about forks?: you can create a fork thanks to GitHub rules, but this rule grants no additional rights.
- Not allowed without the author's written permission: redistributing the source or builds, opening a pull request with changes, using it commercially (selling, offering as a service, bundling into a paid product).
- Any permitted modification must retain the copyright notice and the license text.
In short: forking for yourself is fine; opening a pull request or making money with it requires asking first. To request permission, open an issue (github.com/nethoster/demo-ghostprovider/issues).
GhostProvider — a source-available platform that makes self-hosting simple
Paste a GitHub URL or a path to service.yaml — deploy it as a systemd service.
Private, local, no third parties.
The service.yaml format is documented in docs/MANIFEST.md.
Nine screens, one menu:
| # | Screen | What it does |
|---|---|---|
| 1 | System Scan | shows interfaces, occupied ports and installed tools |
| 2 | Self-Hosting | every deployed unit: start, stop, restart, status |
| 3 | Deploy Service | deploy from a GitHub URL or a service.yaml |
| 4 | Add Service | import a service.yaml into your library |
| 5 | My Services | your added services with their deploy status |
| 6 | Edit Service | change a deployed service — name, port, commit, limits |
| 7 | Egress | what each service may reach outside, verified live |
| 8 | Networks | publish one already-deployed service at a temporary https://*.trycloudflare.com URL; opt-in, local service stays loopback |
| 9 | Logs | three tabs: deploy, software and crash logs |
- SystemD (user-level)
- Git
- Linux
- Rust / ratatui (TUI framework)
- ureq + rustls — HTTPS client locked to a compile-time host allowlist
- systemd (user-level service management)
GhostProvider runs every service as a systemd user unit:
- No root — you manage only your own services; nothing is installed system-wide.
- Starts with login — services survive reboots without extra setup.
- Clean removal — disable the unit and GhostProvider also wipes the clone, the secrets file and the port it announced.
- Sandboxing — every unit ships with NoNewPrivileges, ProtectHome and ProtectSystem enabled.
User units are the standard on Arch, Ubuntu, Fedora, Debian and most modern Linux distributions.
GhostProvider removes the unit, the secrets file, the cloned repo (build caches included) and the announced port whenever a deploy did not finish cleanly:
- Explicit delete — removing a service from My Services.
- Failed deploy — rolled back and wiped immediately.
- Panel closed mid-deploy (Ctrl+C,
q, SIGTERM/SIGHUP) — cleaned as the panel exits. - Shutdown or
SIGKILLmid-deploy — recorded in an on-disk journal and removed on the next panel start. - Panel never launched again — the shipped
demo-ghostprovider-cleanuptimer sweeps leftovers in the background.
-
All data stays local — every request goes through an HTTPS client locked to a compile-time host allowlist, is recorded in net.log, and credentials never leave api.github.com. Nothing is sent to third parties.
-
Outbound traffic is controlled per service — two modes:
- Allowlist — the unit gets
IPAddressDeny=anyplus the hosts you approved; the panel verifies the filter live and says honestly when the kernel cannot enforce it (best-effort warning, never silent). - Deny-all — the unit runs with
PrivateNetwork=yesand a socket-activated__egress-shim: the service gets a real network namespace with loopback only, so its entire network is the localhost tunnel and nothing else routes. Hosts are detected from the manifest (auto: true) and you review the list before deploying.
- Allowlist — the unit gets
-
Optional public sharing uses Cloudflare Quick Tunnel, never a reverse proxy on the service:
cloudflaredis an external agent, is NOT in the compiled-inALLOWED_ENDPOINTS, and is shown by--show-endpointsonly as “opt-in external agent”. A tunnel only runs after an explicit per-session consent, publishes a systemd unit that stays bound to127.0.0.1, stops automatically when the panel exits, and never rewritesservice.yaml, its ports or its resources. Check the current set withdemo-ghostprovider --show-endpoints. -
DNS that survives broken VPN/TUN setups — system
getaddrinfofirst; if that fails, a pinned DNS-over-HTTPS fallback atcloudflare-dns.com(pinned anycast IPs, Mozilla roots). Retries never fail closed on a transient network blip. -
No root required — ordinary systemd user units; nothing installed system-wide.
-
Explicit confirmation before deploy — nothing is built or installed on its own.
-
Sandbox — builds run in an isolated environment (sandboxed home, locked-down network, resource caps). A deploy proceeds only when the sandbox verifies as FULL.
-
Pinned build tools, provisioned into the project cache —
bun,pnpm,goand pip wheels are downloaded through the same allowlisted client, SHA-256-verified against compiled-in checksums and unpacked into the project's.ghost-cache(never system-wide). Python installs then run offline from that wheelhouse.python3itself remains a hard system requirement.
Before deploying, GhostProvider checks what is already on your machine:
- Prerequisites — python3, cargo, git, systemd.
- Listening ports — which ports are taken and by which process.
That avoids port conflicts and helps pick the right deploy strategy. The scan stays useless to anyone but you: no VPN login state, no service fingerprinting; reachability is measured with the same allowlisted, net.log-recorded HTTPS GET to github.com — never an ICMP ping.
A full dashboard for everything that runs: start, stop, restart or remove — one removal cleans the service, unit file, cloned repo, secrets file and lingering ports. GhostProvider cleans the resources it manages; applications may still leave their own state (databases, caches, external sockets) elsewhere.
- Egress screen — each service's outbound policy with live verification,
including an explicit
deny-all: REAL (private netns)row while the loopback-only tunnel is active. - Logs screen — three tabs: Deploy, Software and Crash.
One command:
curl -fsSL https://raw.githubusercontent.com/nethoster/demo-ghostprovider/main/install.sh | shinstall.sh fails closed by default: it downloads the release and its minisign
signature, verifies the signature (with system minisign/rsign, or a pinned
static minisign it fetches on demand from jedisct1/minisign) and only then
installs. A missing signature, a missing verifier, or any verification failure
aborts unless you explicitly opt out with --allow-checksum-only.
If you want to verify the installer script itself before executing it, the
installed script is also signed (install.sh.minisig) — see
docs/DISTRIBUTION.md.
demo-ghostprovider # launch the interactive panel
demo-ghostprovider --show-endpoints # allowlist + session request counters
demo-ghostprovider --selftest # E2E check against live systemd (loopback only)
demo-ghostprovider --verify-sandbox # audit the build sandbox under strace (needs strace)
demo-ghostprovider __check-manifest PATH # validate a service.yaml and print the plan
demo-ghostprovider __deploy --manifest PATH # deploy one service.yaml
demo-ghostprovider __deploy GITHUB_URL # detect the stack, print service.yaml to stdout
demo-ghostprovider __cleanup # manual leftover sweep (runs automatically via a timer)
demo-ghostprovider --version # print versioninstall.sh is the single installer and uninstaller — the same signature verifier
from above covers --uninstall, which fully removes the binary, the cleanup
timer (demo-ghostprovider-cleanup.timer/.service), all demo-* systemd user
units, the deploy registry/secrets state and installed service data:
curl -fsSL https://raw.githubusercontent.com/nethoster/demo-ghostprovider/main/install.sh | sh -s -- --uninstall