Creating tools for myself, for myself first — it's become a habit.
With InfraLens, I wanted an open source tool that I use every day to improve my apps, without depending on external sites I don't control.
A Useful Tool, Designed from Real Need
I wanted a tool I could use right away, without friction: no API keys, no complicated configuration, no account to create. Just a clear, measurable tool, simple to get started with.
There are already plenty of services that do more complete, more exhaustive, more "power user" analyses.
But I wanted something fast, readable, and easily integrable into my daily workflow.
That's how InfraLens was born.
For Developers, Not for Show
InfraLens wasn't designed for a vague audience or to impress.
It was designed for developers, those who want to see specific things without going through a heavy interface or a registration tunnel.
The setup is deliberately minimal:
- no key to generate
- no authentication
- nothing to remember
Just a URL, an analysis, and a clear reading of what matters.
Choosing Simple Over Perfect
I never sought to make something perfect or 100% complete.
It's neither a universal scanner, nor a complete audit platform.
What doesn't exist in InfraLens isn't missing — because it was never necessary for my daily use.
Going for the simplest:
- makes the tool faster
- reduces bug surfaces
- makes results easy to read and understand
A Tool Used Daily
Personally, I often use InfraLens to:
- check the performance status of my sites
- quickly spot optimization points
- get an immediate reading of metrics that matter
It's not a complete analysis, but it's a reliable, fast, and accessible reading.
If InfraLens disappeared tomorrow, what I would really miss would be the ability to see the essential points without navigating through heavier interfaces or complex dashboards.
What This Project Says About My Way of Working
InfraLens is consistent with:
- my pragmatic approach
- my taste for useful simplicity
- my desire to master my tools
Like with Liflow, the idea isn't to make "a product for everyone", but to create something that truly responds to a concrete need I experience daily.
That's probably why I prefer tools that:
- don't require heavy configuration
- produce quickly readable results
- remain simple to maintain
InfraLens isn't a jewel of complexity — it's an effective, simple tool, made to last in my workflow.
Conclusion
InfraLens was designed to serve me first, and only then to be shared and used by other developers.
It illustrates a philosophy dear to me: useful simplicity rather than unnecessary sophistication.
For me, a good tool is one you use without friction, that gives clarity without noise, and that you instinctively find in your toolbox.