I build your software, and it's secure from day one
I take on a project from design to production, or join your team on its codebase. Security isn't a separate phase: it's part of how I write code, because that's where I come from.
What I do
Rust systems and backends
Servers, network protocols, performance-critical code, FFI with C, WASM. When something has to be fast, run for months, or face hostile input, Rust is my first choice.
See: mh3-rs, Theca
Web backends and apps
APIs and backends in Rust or TypeScript, PostgreSQL, and the front-end when the project needs one: React or Svelte, with Next.js or SvelteKit. I can also host and run what I build: deployment, monitoring, updates.
See: Feezio, Chapter, what2do.ch
Security, built in
Secure code review with a prioritised report, applied cryptography (choosing, integrating and auditing primitives and protocols), and protocol design. For embedded systems, evaluation against fault-injection attacks.
See: E-Laun, the CSEM thesis, two years teaching application security
How I work
Correctness first: a test that fails before the fix, a measurement before a claim. I write down the decisions, so whoever comes after me understands why the code is the way it is.
Codexa Perrenoud
