Web Development2026

A React registration platform and a Laravel race marketplace

Two public platforms for YouTooCanRun: racesregistrations.com, where runners find races by city, distance and date and enter them before registration closes, and racemart.in, where races are listed, compared and reviewed. Both were taken through the full development lifecycle to deployment, remediated against a security audit, and have been maintained since.

Visit the live site(opens in a new tab)

2 platforms
Built, deployed and maintained: Full lifecycle
Requirements through deployment: Ongoing
Security fixes and maintenance

The challenge

YouTooCanRun meets runners at two different moments, and they want different things at each. Someone still choosing a race wants to compare what is on offer — where it is, how far, what other runners made of it. Someone who has already chosen wants to enter it, before a registration window closes on a date that does not move. One platform answers each question, and neither is much use if it only half works.

Both are public and in constant use. Registration opens and closes on fixed dates, organisers add listings as their events are announced, and the platforms carry participant signups — so work has to land without taking either site down, and the security posture has to be reviewed rather than assumed.

What we were asked to do

Take both platforms through the full web development lifecycle — requirements, build, testing and deployment — then act on what a security audit found and keep both running as events open and close week after week.

What we did

Built the registration platform in React
racesregistrations.com presents races by city, by distance from 5K to ultra, and by period, each with its own registration window and current status — so a runner sees what is still open to enter rather than reading a static list of dates.
Built the race marketplace on Laravel and PHP
racemart.in carries the listings themselves: searchable by race and by city, with comparison, event reviews, and a route for organisers to submit their own events, so the catalogue grows without a developer publishing each entry by hand.
Ran the full development lifecycle on both
Requirements, build, testing and deployment were carried for each platform as one engagement rather than handed over at the end of the build, so what shipped is what was specified and both went live under our own release.
Remediated what the security audit found
Both platforms were audited and the findings were fixed. What those findings were stays out of a public case study, remediated or not.
Kept both platforms in maintenance
The engagement did not end at launch. Both sites are maintained in service, with fixes and updates released while events are live, because a registration window does not pause for a deployment.

Results

2 platformsBuilt, deployed and maintained: A React registration platform and a Laravel marketplace, each taken from requirements through to deployment and kept in service since.
Full lifecycleRequirements through deployment: Both sites were specified, built, tested and deployed as a single engagement rather than handed over at the end of the build.
OngoingSecurity fixes and maintenance: Audit findings were remediated, and both platforms remain under continuous maintenance as events open and close.

Next case study

All case studies

Testriq QA LabQA & Testing SolutionsWeb Development