│ │ ┃ What is Hop3? ┃ │ │ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ │ │ │ │ │ │ The push-to-deploy experience of Heroku — on infrastructure you own. │ │ │ │ │ │ • Push to deploy — git push or hop3 deploy and your app is live: built, reverse-proxied, TLS, │ │ backups. No DevOps team, no YAML. │ │ • Your server, your data — no hyperscaler lock-in, no per-seat SaaS tax, nothing phones home. │ │ • Any app, one command — your own code, or one-click installs from an open catalogue (in │ │ progress). │ │ • No Kubernetes. No mandatory Docker. No cluster (yet?). │ │ │ │ │ │ Why now: rising SaaS bills, vendor lock-in and digital-sovereignty rules are pushing workloads │ │ back on-prem. │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ██░░░░░░░░░░░░░░░░░░ 2/14
│ │ ┃ Testing — how the platform earns trust ┃ │ │ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ │ │ │ │ A platform makes a promise on every deploy. Making good on that promise was one of the two │ │ largest sustained efforts of the grant — alongside Nix reproducibility — and it runs at two │ │ altitudes. │ │ │ │ ╭──── Code-level pyramid · ~2,000 tests ─────╮ ╭────────── System-level harnesses ──────────╮ │ │ │ • Unit — functions & classes, deps mocked │ │ • `hop3-test` — deploy real apps to Docker │ │ │ │ • Integration — real in-memory DB, HTTP │ │ / SSH / Hetzner, verify HTTP + logs │ │ │ │ client │ │ • App corpus — 169 apps × {native · docker │ │ │ │ • System — full server + CLI in Docker │ │ · nix · nix-gen}, +12 negative cases │ │ │ │ • E2E — complete deploy workflows │ │ • Docs-as-tests — 10 tutorials run via │ │ │ ╰────────────────────────────────────────────╯ │ Validoc · 58 demos │ │ │ ╰────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ Fast (?) tests on CI · E2E + multi-distro nightly (hours). │ │ │ │ Packaging an app is a test — each real one finds an edge the synthetic fixtures never hit. │ │ │ │ │ │ │ │ │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ███████████░░░░░░░░░ 8/14
│ │ ┃ What works — and what's next ┃ │ │ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ │ │ │ │ │ │ ╭───── What works (by the close of NGI) ─────╮ ╭─────────────── What's next ────────────────╮ │ │ │ • It's real and in use - we run our own │ │ • Branding · marketing · communication - │ │ │ │ production apps on Hop3. │ │ we built it; now we have to make it │ │ │ │ • The method: package real software → it │ │ known. │ │ │ │ surfaces the gaps → fix the platform. │ │ • Adoption - the first external users │ │ │ │ • A usable, trustworthy platform - not │ │ (today, we're user zero). │ │ │ │ just a prototype. │ │ • Revenue - service, subscription, or a │ │ │ │ • Tens of applications │ │ branded SaaS marketplace (prior slide) - │ │ │ ╰────────────────────────────────────────────╯ │ once there are users. │ │ │ │ • Federation - the longer, research │ │ │ │ horizon. │ │ │ ╰────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ Hop3 is real and runs today. The open question was never the idea — it's adoption, then │ │ revenue. │ │ │ │ │ │ │ │ │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ██████████████████░░ 13/14