About libnode: End-to-End Digital Solutions that help people build digital projects that stay secure, useful, and easy to understand.
The name libnode brings together two ideas that shape the way I work.
Liberty is a reference to the open-source world that taught me so much over the years. I have always been inspired by people who share their time, knowledge, and tools so others can learn, build, and stay in control of their own systems. That mindset shaped my view that data ownership, autonomy, and transparency matter.
Node speaks to connection. Technology is at its best when it creates useful links between people, ideas, and services. The internet showed what becomes possible when people connect, share, and improve things together. libnode is built around that balance: more freedom, more clarity, and a better connection between human needs and digital tools.
I hold a Master’s degree in Management and Business with a specialization in MIS (Management of Information Systems) from IESEG. That background gave me a broader way of thinking about technology: not only how it works, but why it matters, how it supports decision-making, and how it fits into real projects and real constraints.
I spent most of my life in France and also lived for three years in the UK, which gave me a strong command of English and a more international perspective. Alongside that, my internships, independent projects, and long-term curiosity for technology taught me how to move comfortably between business logic and technical execution.
After years of being drawn to technology, building projects, and learning through practice, entrepreneurship felt like the right next step. Today, libnode is how I put that mix into practice. I work with individuals, small businesses, and more tech-savvy collaborators who want clear thinking, practical implementation, and a better path from idea to realization.
I believe technology should stay understandable. Whether someone is highly technical or completely new to a subject, they should still be able to understand the direction of a project, why certain choices are being made, and what they can expect from the result.
I also believe security should be considered from the beginning, not added at the end. My thesis focused on the evolution of malware in companies, and that work reinforced how important it is to think seriously about risk, exposure, and resilience from the start.
AI is part of that conversation too. I care a lot about AI and local LLMs, and I actively work with them in my own environment. But I do not see AI as a magic answer to everything. It is an opportunity when used with purpose, good judgment, and the right security mindset. Otherwise, it can add noise, unnecessary risk, or false confidence.
More broadly, I try to work with tools that create real value. If a service makes a workflow better, more secure, or easier to maintain, it deserves attention. If it only adds complexity or follows hype without a clear reason, it probably does not.
Much of the way I think has been shaped by building and testing things for myself. I run my own homelab and work with VPS environments to experiment, learn, and refine ideas in conditions that are close to real-world use. It helps me stay hands-on, curious, and honest about what is truly useful.
It is also why I care about projects beyond my own client work. I am currently working on ways to strengthen the OpenStreetMap ecosystem because I value tools and services that offer real public utility without relying on questionable data practices. For me, supporting more open and practical alternatives is part of the same philosophy behind libnode.
My role is not just to build something technical and disappear. I want to help people move forward with more confidence, whether they need clear explanations, secure foundations, or someone who can think across the whole project.
That means adapting to the person in front of me. Some clients want plain language and guidance. Others are more tech-savvy and want a reliable partner who understands infrastructure, web projects, AI, or digital workflows in a broader sense. Both matter.
Through libnode, I bring clear communication, attention to detail, security awareness, and End-to-End Digital Solutions that connect strategy, implementation, and day-to-day use.
I pay close attention to structure, exposure, and long-term reliability so projects start from a solid base instead of collecting risk later.
I am enthusiastic about AI when it solves a real problem. My approach stays practical, security-minded, and focused on tools that genuinely improve workflows.
From infrastructure questions to web projects and broader digital workflows, I aim to build solutions that stay clear, maintainable, and aligned with real needs.
If you have an idea, a project, or a technical problem you want to approach with more clarity, I would be glad to discuss it with you. You do not need to have everything fully defined before reaching out. Sometimes the first useful step is simply talking things through.
Talk through your project ->