MaSiFrom Digital Neofeudalism to Sovereignty: How I Built My Own Knowledge Operating System
Most of us live today in a state of digital neofeudalism. We have become digital sharecroppers: our notes, thoughts, and technical documentation are "leased" from large SaaS corporations. If Notion goes down, your knowledge disappears. If Evernote changes its terms and conditions, your data becomes hostage.[cite: 1]
I decided to say "enough." I built a system that is 100% mine, self-documenting code, and works the way I think: nonlinear. [cite: 1]
🧠 Knowledge Architecture: A Network Instead of a List
A traditional blog is a list. My knowledge base is a graph. I use Markdown and the Zettelkasten approach to create a network of connections. Thanks to Hugo, each note knows who links to it.[cite: 1]
How does it work?
One article contains reasons, which are the titles of separate publications. These, in turn, have backlinks like "this motivated me to...".[cite: 1]
graph TD
A[homelab.md] -->|why?| B[digital-neofeudalism.md]
A -->|business model| C[digital-sharecroppers.md]
B -->|solution| A
C -->|motivation| A
I use transclusion (include) to inject fragments of technical documentation where they're needed. No more "copy-paste."[cite: 1]
🏗️ Hardware: Division of roles in the ecosystem
My homelab isn't one big server. It's specialized units:[cite: 1]
| Machine | Role | Characteristics |
| --- | --- | --- |
| R3930 | Workhorse | heavy containers, databases. |
| Wyse 5070 | Guardian | DNS (Pi-hole), Proxy, SSO (Authelia). |
| DELL GB10 | AI Accelerator Cluster | LLM. |
| Laptop | Command Center | This is where the code is written, and this is where Ansible runs. |
Why is the Gateway (Proxy/SSO) on a small Wyse? Because it's quiet, energy-efficient, and supposed to run 24/7, even when the "workhorse" is resting.[cite: 1]
🛠️ Infrastructure as Code (Ansible)
I don't configure servers manually. Everything is defined by SSoT (Single Source of Truth) in YAML. One file describes the entire lab:[cite: 1]
services:
- id: "technical-docs"
name: "Wiki"
fqdn: "docs.lab.arpa"
target_host: "R3930"
is_private: false
category: "Knowledge"
Ansible takes this list and:
nginx-proxy on the Wyse to route traffic to R3930.[cite: 1]🔒 Security: SSO and Custom CA
Let's Encrypt has no place on the .arpa network. I built my own Certificate Authority (Own CA) based on Smallstep.[cite: 1]
- Authelia (SSO): One login and password (plus 2FA) to access all private services.[cite: 1]
- Smallstep SSL: Every service in the
*.lab.arpadomain has a "green padlock." Ansible ensures that my laptop and all servers trust my Root CA.[cite: 1]
Development Challenge: Automating SSL via the ACME protocol on my own network is pure magic. Nginx automatically requests a certificate from the local CA server. Without accessing the internet.
📊 Result: Dashboard
The end result is the Homepage – a dashboard that generates automatically. I can see every service, its status, and information about which physical hardware it currently resides on.[cite: 1]
🚩 What's next?
My knowledge operating system is growing, but it has one weak point. If the Wyse DNS server goes down, I'm out. So in the next post, we'll cover DNS2 redundancy and data synchronization using Gravity Sync.[cite: 1]
Homelab isn't a goal, it's a process. And you? Are you still working your tail off in the cloud?
#DigitalIndependence #OpenSource #SelfHosting #DataPrivacy #TechFreedom #BuildingTheFuture
#DigitalNeofeudalism #DigitalSharecroppers #KnowledgeOperatingSystem #Ansible #Homelab
Article generated and deployed automatically by Ansible.[cite: 1]
