Skip to content

Behind the screen

I build web products. And I live with them, for years.

I’m Alexandre Brun-Giglio, a full-stack web developer based in Aix-en-Provence.

I was born in Corsica and grew up between the island and the mainland. I started tinkering with websites in secondary school and made it my job in 2019. Since then I’ve delivered agency work for national accounts while building my own products on the side. That combination changes how I approach a project: when you maintain what you wrote for two years, you don’t make the same decisions as when you ship and move on.

Background

Master’s degree in web development at Aix Ynov Campus. Then several years at Nextalys, a consultancy based in Cabriès, delivering for national accounts including Morgan & Mallet International and Isover, part of Saint-Gobain. After that, EKIP Méditerranée, a hosted-services operator working between Marseille and Bastia, alternating remote work and time on site.

I started out with Angular and NestJS; today I work mostly with React, Astro and TypeScript. The shift wasn’t ideological: the projects changed, and the tools followed.

What I build for myself

I develop and operate my own products. They aren’t demos: they have users, releases, and bugs to fix on a Sunday evening.

jibu, a budgeting app in production. Axobot and Axoquest, a community Discord bot and a full RPG, 230 releases shipped. Axo’s Corp, the platform that makes that ecosystem installable on any server.

That’s where I learn what a client never funds: what breaks after eighteen months.

See the case studies

How I work

  • One bug fixed, one test added

    Every fix ships with its regression test. No patch without proof that it won’t come back.

  • You can replace me

    The code is documented and the content editable without me. A delivered project has to survive in someone else’s hands.

  • Your data doesn’t disappear

    Database migrations are strictly additive: nothing is ever dropped. A little accepted debt in exchange for never losing data during a release.

  • Release notes people can read

    Written for the people using the product, not for the people who built it.

Want to learn more?

Let’s talk.

Let’s talk