furtka/README.md

Homebase

Open-source home server OS — simple enough for everyone.

Working title: Homebase. Robert's internal codename: Furtka (Polish for "gate" — plays on the gateway concept). FurtkaOS is also in the running.

Turn any x86 PC into a powerful, self-hosted home server with an app-store experience. No terminal skills required.

Vision

People are tired of big companies knowing everything about them. Synology NAS comes close to solving this, but it's expensive and still too complicated for most people.

Homebase aims to be:

• As easy to install as Windows — boot from USB, click through a wizard, done
• As easy to use as an app store — want Nextcloud? Click install, pick a name, wait a few minutes, and you have nextcloud.yourdomain.de
• Container-based — everything runs in Docker, with sensible default configs
• Built for normal people — your dad should be able to run his own cloud server
• Fully open source — with an optional support/infrastructure subscription (Proxmox model)

Principles

• Everything already exists — We're not inventing, we're connecting. Docker, reverse proxies, Let's Encrypt — it all works. We just wire it together with default configs and a simple wrapper.
• Dogfooding — We build what we use ourselves. If we wouldn't run it at home, we don't ship it.
• Two-tier UX — Dead simple for beginners (click Install, done), full control for advanced users (SSH in, edit configs, do whatever you want).

Architecture

+------------------+
|   Web UI         |  <- Simple admin panel / app store
+------------------+
|   Settings       |  <- UI/API wrapper that generates Docker configs
|   Wrapper        |     from simple user choices
+------------------+
|   Docker         |  <- Containers with sensible default configs
+------------------+
|   Gateway        |  <- Reverse proxy, SSL, DNS (self-hosted or managed)
+------------------+
|   Base OS        |  <- Minimal Linux (leaning Arch, Debian as fallback)
+------------------+
|   Any x86 HW     |  <- Old PC, mini PC, NUC, whatever
+------------------+

Key Decisions

Decision	Status	Notes
Base OS	Leaning Arch	Robert already has Arch running on Proxmox and is building custom images. Debian remains fallback (FAI, Proxmox ecosystem).
Containers	Docker	Lower overhead than VMs, easier default configs
Installation	Web-based wizard	Robert's webapp prototype (device reader + form → JSON) is working
Gateway	Flexible	Own reverse proxy OR managed through our infrastructure
UI approach	UI-first	Design the simplest possible UI, then build everything to match

Landscape (Existing Projects)

Project	Type	Apps	Key Trait
CasaOS	Layer on existing Linux	~100	Simplest install, runs on any distro
Umbrel	Debian-based full OS	~300	Slick UI, crypto/privacy focus
Runtipi	Docker-based, GPL-3.0	200+	Largest default app catalog
HomeDock OS	Pseudo-OS layer	Hundreds	Desktop-style UX with window manager
Cosmos Server	All-in-one platform	Docker	Built-in 2FA, anti-DDoS, security focus
YunoHost	Debian-based OS (since 2012)	400+	Most mature, biggest catalog
TurnKey Linux	Pre-built system images	Hundreds	One image per use case

Where we differentiate

1. Full OS + device-aware installer wizard — Boot USB, open http://proksi.local, wizard detects hardware and configures everything. No existing project does this — CasaOS/HomeDock are layers on existing Linux, Umbrel/YunoHost have basic installers without device detection.
2. Auto setup intelligence — Tests drive speeds, auto-assigns boot/LVM storage. Competitors just ask you to pick a drive.
3. Gateway-as-a-service — No competitor offers managed reverse proxy/DNS as a service. Cosmos has built-in reverse proxy but self-managed only.
4. Arch base (rolling release) — Everyone else is Debian. Rolling releases mean faster updates, more control.

Gap we're targeting

None of these nail the "your dad can set this up" experience. The installer wizard + managed gateway is the strongest angle.

Resources

• awesome-docker-compose.com — Ready-made Docker Compose configs (useful later for app store defaults)

Inspiration

• Azure Local — cluster management for enterprises, we want this for home users
• Proxmox community-scripts — great base, but VM-focused (more overhead)
• Synology DSM — closest to our UX goal, but proprietary and expensive
• Home Assistant — app-store model for smart home, we want this for all services

Roadmap

• Installer webapp prototype — device reader + form → JSON (Robert)
• Arch running on Proxmox, custom image builds in progress (Robert)
• Competitor testing — Daniel tests CasaOS, Umbrel, YunoHost on Proxmox, documents UX findings
• Base OS bootable image — Robert gets a minimal Arch image that boots, runs Docker, serves the installer webapp
• UI mockups / drafts (Robert)
• Base OS finalized (Arch vs Debian)
• First containerized service (Nextcloud?)
• Gateway / reverse proxy setup
• Settings wrapper — generate Docker configs from user choices

Business Model

Homebase starts as a private/personal project. The long-term model follows Proxmox:

• Free & open source — anyone can download, install, and use it
• Paid support & managed infrastructure — for users who want hassle-free setup
• Managed gateway option — the gateway (reverse proxy, SSL, DNS) can be self-hosted or run through our managed infrastructure (potential subscription revenue)

Team

• Robert — Architecture, UI design, webapp installer prototype
• Daniel — Infrastructure, testing, DevOps

License

AGPL-3.0 — open source, community-driven.