24hprojects is an in-house product of Groupe BERREBI, built around one simple promise: ship a feature or an MVP in a single day. No endless scoping, a short scope done well, and production that anyone can follow live. The product is in development and not yet deployed online.
The project in detail
I designed and built all of it, front end and API, from 27 to 29 August 2026. The home page shows the production list, with features queued, in progress and delivered, stat tiles and two leaderboards: the most served projects and those trending over the last thirty days. Visitors can sign up with a password or through OAuth with GitHub, GitLab or LinkedIn, then submit their project through a form.
Each owner gets a console with a project selector to break the project into features and attach a budget and links. An admin console manages users, projects, features and reference data: sponsors, contributors and events. An embeddable badge lets a project show up on another website.
The front end runs on TanStack Start with full server rendering, shadcn/ui and Tailwind CSS v4, in French and English with one URL per language, a dynamic sitemap and structured data. The API is written with FastAPI: Postgres for accounts and contact requests, Memgraph for the graph of projects and features, argon2 password hashing and JWT sessions. It exposes ten routers and is covered by 55 test functions.
A few concrete problems needed care: forwarding session cookies during server rendering, telling the public API address apart from its internal Docker network address to avoid DNS errors on the server, ordering graph aggregations to avoid Cartesian products, and showing a clean message instead of a broken page when the API does not answer.
This product is also my test bed. The technical choices I later offer to clients, such as bilingual server rendering or OAuth sign-in, were tried here under real conditions first.
The 24-hour promise enforces a discipline that applies to any project: a scope written before coding, broken into features shipped one by one, and a clear definition of done. It is the same method I apply to my clients' MVPs, on a different timescale.