Web Development
Alcodefi
The platform of Alcodefi, a finance and banking training center: a public catalogue and planning, pre-registration and a back-office, kept in sync with the center's ERP. I designed its architecture and built most of it: the ERP sync, role-based access, the back-office, follow and reminder emails, and the audit trail.

- Role
- Lead developer
- Period
- March 2026 – present
- Context
- Client project, with a second developer
Overview
Alcodefi is a training center and consultancy in finance and banking, approved by the Algerian state. Its platform publishes the trainings it offers and when their sessions run, by date or by professional domain, lets visitors pre-register for a session and download the plannings as PDFs, and gives staff a back-office to manage all of it. Most of the catalogue lives in the center's ERP, so the platform keeps itself in sync with it. I designed the architecture and built most of the platform, working alongside a second developer.
What I built
- A one-way sync from the center's Odoo ERP over JSON-RPC, bringing in domains, trainings, sessions and their timeslots every day or from a dashboard button, where a staff edit to a synced field shields that row from the next syncs, and a report email lists what was added, changed or hidden.
- Access control as one static policy: four roles and per-row rules in a single matrix, checked in the data layer on every read and write, and mirrored as database filters so that a paginated listing is narrowed before it is paged.
- A back-office for trainings, sessions split into several timeslots, domains, users, pre-registrations and a bank of SharePoint-hosted images, with a rich-text editor for descriptions and every table paginated, sorted and filtered in SQL.
- Follows and reminders: following a training sends an email when a new session of it is published, and a reminder warns before a session's registration deadline, each sent exactly once.
- An audit log of staff actions, rate limiting on sign-in, sign-up and the public forms, random 256-bit email verification tokens, and constant-time checks on the scheduled jobs' secret.
- Public pages served from the CDN cache and refreshed whenever a write changes what they show, with a sitemap, canonical URLs, link previews and schema.org course markup for search engines.
Tech stack
Screenshots

Want something like this built?
Tell me what you have in mind, even if it is still a rough idea.
Get in touch