Who I am, and how I work
I provide long-term Linux infrastructure management for organizations that value stability, clarity, and responsible systems administration.
My work focuses on fully understood systems,
continuous operational stewardship,
and reducing risk across Linux, BSD, macOS, and traditional Unix environments.
Ad hoc firefighting is avoided by design.
Based in Strasbourg, France. Working remotely worldwide.
Get in Touch →Who I Am
My name is Valentin Beck. I work independently as a Linux systems administrator under the name Permalink.
Background
I have more than two decades of experience operating Linux systems, networks, and internet-facing services.
My work spans ISPs, hosting providers, and production environments expected to run continuously under significant load.
I have hands-on expertise in routing, redundancy, full-stack service operation, and the practical realities of running platforms that architecture diagrams often overlook.
My early Linux experience dates back to the era of make menuconfig; make bzImage
and the occasional encounter with sendmail.cf and the dreaded LI
Linux is my primary focus, though I've worked with other Unix systems in legacy or mixed environments, including long-lived systems such as Solaris (SunOS). I take operational responsibility only for platforms that can be understood, documented, and safely stewarded over time.
How I Think About Infrastructure
Hardware fails.
Software fails.
People make mistakes.
Reliable operations come from acknowledging this. And from designing systems that fail in controlled, understandable ways.
I call this approach calm infrastructure: prioritizing understanding over urgency, deliberate change over constant activity, and predictable system behavior under stress.
It is not a framework, but a practical stance toward responsibility, failure, and long-term operation.
What I Optimize For
Long-term operational stability comes first. Speed, novelty, and short-term gains come after.
Reduce unnecessary complexity
Make failure modes visible
Preserve institutional knowledge
Design systems that reduce tension
Support informed decisions
Preserve clarity under stress
Some clients call this feng shui for infrastructure. Remove unnecessary pressure, respect constraints, and let systems operate within natural limits. Read more →
Working Relationship with a Linux Systems Administrator
I work with a limited number of clients at a time. Working solo allows me to take direct, uninterrupted responsibility as the steward of the systems I manage.
Engagements are ongoing rather than transactional. Work is scoped in writing, responsibilities are explicit, and expectations are set before changes occur.
This model assumes a few things in practice:
- One clearly identified caretaker is responsible for the system.
- Infrastructure changes are made deliberately, not continuously.
- Documentation and operational history are maintained over time.
- Ownership and boundaries are defined before incidents occur.
- Long-term stability is prioritized over short-term speed.
Environments built around rapid feature delivery, constant change, or distributed responsibility tend to require a different operating model.
Continuity
I aim to remain responsible for systems for their full operational life while they are under my stewardship.
Not only during changes. Not only during crises.
Many failures stem not from mistakes, but from lost history and fragmented responsibility.
Next Step
If your organization needs Linux infrastructure with clear, long-term operational stewardship, the next step is a short introductory conversation to understand your environment.
Before sharing detailed information about your systems, please review our Mutual Non-Disclosure Agreement (NDA).
Contact →