A company that still
writes the code.
SegfaultSec is a software engineering and security company, not an agency. Nobody here is paid to forward your email or to present a deck about your project.
Everyone at SegfaultSec builds, secures or runs software.
Five things we
keep coming back to.
Not values on a wall. These are the arguments we have already had internally, and the ones that decide how a project actually runs.
Anyone can say fast, secure or scalable. A number taken the same way before and after is the only version of that sentence worth paying for. If we cannot measure an improvement, we are not confident we made one.
Every layer between those two costs money and loses information. We removed the layer instead of charging you for it, and it is the single reason our numbers look the way they do.
We pick things we can still support in three years and that another team could pick up tomorrow. Clever choices feel good for a month and become somebody's problem for a decade.
That a rebuild is not worth it. That the offer is the problem, not the page. That we are the wrong size for the job. Losing the work is cheaper for everyone than discovering it in month three.
Ordinary tools, written handover notes, no exit fee and no data held. A client who stays because leaving is painful is not a client, and we would rather earn the next month than trap it.
Trained the
hard way.
SegfaultSec was founded by engineers trained at 42, a school with no lectures and no teachers, where the only way through is to build the thing and have your peers pull it apart. That habit became the company's way of working.
Morocco, France, Germany and the United States. Between them we cover European and North American working hours. Everything is written down, so a time difference is a scheduling detail rather than a delay.
Peer-reviewed, project-based, and unforgiving. It is why code review here is normal rather than something people take personally.
We host what we sell. When we tell you how to keep a system alive, it is because we are doing it for ourselves every day.
What it is
like.
Three things clients tell us are different, and one thing they sometimes find frustrating. We would rather you know both.
The things people
actually ask.
Are you an agency?
No, and the difference is not a word game. An agency sells your project onward and manages the people who do it. We do the work. There is nobody here whose job is to stand between you and the code.
How big are you?
Large enough to cover several projects at once and to have real specialists in security and infrastructure. Small enough that the person answering you knows your system. If a project needs more than we can honestly staff, we say so rather than stretch.
Does a spread-out team slow things down?
It would if we ran on meetings, and we do not. Decisions and updates go in writing, so nothing waits for the right person to wake up. Across the four countries somebody is working in your hours, and you get one named engineer rather than whoever happens to be online. We invoice in your local currency and sign whatever agreement your legal team needs.
Can we see your work?
Some of it. Most of what we build belongs to somebody else and stays private unless they give written permission. We can walk you through anything relevant on a call, including the parts that went wrong.
Why the name?
A segmentation fault is what happens when a program touches memory it has no right to touch. It is the most honest error a computer produces: something is wrong, here, exactly. That is the kind of clarity we are after.
Are you hiring?
Sometimes. Write to us through the contact page with something you built and what you would change about it now. That tells us far more than a CV.
Send us a URL.
We'll tell you what hurts.
The easiest way to find out what we are like is to give us something to look at. The audit is free, takes 48 hours, and commits you to nothing.