KeilerHirsch · Independent developer & founder
Simple products. Serious engineering underneath.
Independent software engineering · deterministic systems · security research · reproducible evidence
About · Live activity · Engineering · Community
I build practical software, automation and technical research systems. My work spans software and systems engineering, security research, digital forensics, OSINT and AI-assisted development, with a strong focus on reproducible evidence and engineering that survives contact with reality.
My foundation is hands-on engineering: precision mechanics, industrial electronics, applied systems work and independent technical experimentation. I look for failure modes, tolerances, root causes, clear boundaries and measurable results rather than impressive terminology.
KeilerHirsch is my developer identity; KeilerHirsch Labs is the home for products and research. See GitHub's pinned repositories and the live KHL repository list for current projects. Each project's README, releases and license are the source of truth — no manually maintained product catalogue here.
Automatically refreshed from GitHub (scheduled every six hours), covering public original projects under both KeilerHirsch and KeilerHirschLabs. Forks, profile metadata and archived projects are excluded from source-language percentages. The separate list of 13 working languages is owner-confirmed, not an inference from code size. Activity metrics are not a measure of proficiency or product maturity. The UTC timestamp shows when displayed metrics last changed, not the latest fetch; unchanged data is checked without generating new commits.
- Evidence before claims. Reproducible tests, provenance and observable outcomes matter more than impressive status labels.
- KISS at the surface. The user experience should stay simple; stronger assurance belongs at boundaries where it pays off.
- Determinism where it matters. Prefer explicit state, rules and verifiable sources over unexplained decisions.
- Engineering over theatre. Use the language, architecture and checks the actual problem warrants.
- Autonomy with verification. Automate the repetitive parts, preserve safeguards, and check the real result.
My background combines precision mechanics, industrial electronics and applied systems work with largely self-taught software engineering. I choose languages and tools for the problem, not to decorate a technology stack. The live activity panel shows both code composition and my separately confirmed working languages.
Background & qualifications
- Precision Mechanic (
Feinwerkmechaniker) — completed German vocational qualification. - Electronics Technician for Industrial Engineering (
Elektroniker für Betriebstechnik) — completed German IHK vocational qualification. - State-Certified Technician program in Mechanical Engineering — Aircraft Technology specialization — Technische Fachschule Heinze, Hamburg; 13 of 24 full-time months completed; no qualification awarded.
- 23 months of voluntary military service in the German Armed Forces (
Bundeswehr). - Autodidact by habit — software/systems engineering, cybersecurity research, digital forensics, OSINT and AI-assisted development.
- Languages: Polish · German · English.
That background shaped a simple habit: look for tolerances, failure modes, measurable behavior and maintainability before celebrating an elegant abstraction.
Security research, OSINT and digital forensics follow the same discipline as engineering: preserve evidence, separate observations from interpretations, and make claims traceable. Research repositories are not claims that findings or vulnerabilities have been independently verified or remediated.
I founded and moderate r/MAYHEMClub, a space for independent developers, modders and open-source builders to share work and get practical feedback. A central KeilerHirsch Labs Discord community hub is also being developed.
Build cool shit. Share it. Get real feedback.
Repository-controlled automation software — including tools/, tests/ and project-controlled workflow logic — is available under the PolyForm Noncommercial License 1.0.0.
Profile prose, personal branding and visual assets are not covered by that software licence unless explicitly stated otherwise. Third-party projects and linked content retain their own rights.
If the UI looks simple, someone probably suffered in the architecture first.