Contact
Get in touch with Sébastien Demanou — questions, corrections, feedback, or freelance and consulting enquiries.
Send a message
I read every message and reply when I can.
No tracking, no newsletter. Your message is delivered to me by email, and I read every message.
Message sent
Your message has been sent successfully. Thank you for getting in touch.
Frequently asked questions
Quick answers about who I am, what I work on and which enquiries I can help with.
Skills & technical work
The short answer is anything this site covers: designing and building software, debugging, Linux and the command line, containers and deployment, CI/CD and automation, networking and security, and running AI models locally.
Yes. I'm comfortable landing in code I did not write: reading it, tracing a bug, untangling a build, adding tests, or changing one part without breaking the rest. A repository link and a short description of the problem is the best place to start.
Yes — architecture, data model, API design, the build and the deployment path. I prefer to start from the constraints (what the system must do, who uses it, where it runs) rather than from a stack.
Yes: code, architecture, infrastructure or documentation. Tell me what the work is meant to achieve and what worries you — a review is only useful when it is measured against a goal.
Yes. Linux servers, Docker and Compose, reverse proxies such as Traefik, Kubernetes, CI/CD pipelines, and reproducible environments with Nix or devbox. This site is built and deployed that way.
Training & knowledge sharing
Training and workshops are among the enquiries I welcome. Tell me the subject, the audience and the format, and we can work out together whether I am the right person for it.
The subjects this notebook is written about: Linux and the command line, containers and infrastructure, CI/CD and automation, networking and security, JavaScript/TypeScript and React, Vue, Python, and local AI — models, speech and text running on your own hardware.
Yes. Hands-on sessions work best when they are built around a real problem — your repository, your deployment, your data — rather than a slide deck. Describe the setup and I will tell you what I can do.
That is the point of starting from your constraints. Tell me your stack, your team's level and the outcome you need; the content should follow from that, not the other way around.
Both are worth asking about. Tell me who the training is for and how many people are involved, and I will answer honestly about what fits.
Freelance & consulting
Freelance and consulting enquiries are welcome — that is what the Freelance / consulting subject is for. Availability depends on what I am working on at the time, so send the details and I will give you a straight answer.
Work where software, systems and infrastructure meet: building or fixing an application, untangling a deployment, automating a manual process, setting up CI/CD, or getting AI and local models running on real hardware.
Yes. Sometimes the most useful thing is a second opinion on an architecture, a build, an incident or a decision you are about to commit to. A short engagement is often enough.
Yes, as an external contributor. Tell me the stack, how the team works, where the work would land and how you would like me to fit in.
Remote is the default for this kind of work. If your team is in a specific time zone, tell me which one and I will be explicit about the overlap I can offer.