End-to-end validation of the per-app container update and the Furtka self-update ran green on VM 192.168.178.128 this afternoon (26.0-alpha → 26.3-alpha → rollback → reboot). Both flows are real — promote the drafted HTML-comment bullets from _index.md and _index.de.md into the visible "What works today" list. The "plain-English Wi-Fi story" was the only one the copy was missing a truthful on-box outcome for, and it still is (for a moment here a-few-days-ago, but the update story moved past that). Matches the commitment in feedback_no_invented_content.md — we only publish after confirmation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.3 KiB
1.3 KiB
| title | description | status |
|---|---|---|
| Furtka | Open-source home server OS — simple enough for everyone. | <span class="mono">26.0-alpha</span> — work in progress |
Furtka is an open-source home server OS. Boot from USB, click through a wizard, and any old computer turns into a private cloud for your household — with your own apps, your own name on the network, your own data.
The goal is simple: your dad should be able to set this up.
What's coming next
- Apps for photos, files, smart home, game streaming and media
- Plainer language in the setup wizard
- Secure connection on your home network (no browser warning)
- Linking several servers together
What works today
- Boot from USB stick and install Furtka onto the hard drive
- A wizard asks for name, user and network — done
- Then: open the control page in your browser
- First app: file sharing on the home network (everyone on Wi-Fi sees the folder)
- Install and remove apps with one click
- Update an installed app with one click (pulls the newest container image)
- Update Furtka itself with one click — no reinstalling for new features
We're two people building it in public on evenings and weekends. It's early.
Want to follow along? Write to hallo@furtka.org.