We build systems that stay simple.
Not lighter. Not trendier.
Just clearer, more durable, and actually usable.
Full Front-End is a personal organization.
Not an agency.
Not a startup.
It’s a space to design, test and refine:
- automation systems
- self-hosted tools
- simple architectures
- real-world workflows
Everything here follows the same rule:
If it becomes complex, it’s broken.
A central project focused on structuring information and building systems that stay usable over time.
The current server architecture behind Full Front-End.
Self-hosted infrastructure using OpenTofu, Kubernetes and Helm.
Reverse proxy setup from a previous production architecture.
Docker container for generating valid local SSL certificates.
Reusable building blocks for self-hosted environments.
Plain-text project management for Obsidian.
These repositories reflect previous work and experiments.
They remain available but are no longer actively maintained.
Some parts of the system are still being extracted and open-sourced:
- auto-deployment systems
- infrastructure workflows
- automation setups
You don’t need more tools.
You need something that holds.
Full Front-End is run by one person.
Builder, developer, and coach.
I build systems that stay simple, usable, and under control.
No layers for the sake of it.
No tools you don’t understand.
Just something that holds.