Get in touch
Case study

Platform development, move to the cloud and a full rebrand for AllAboutLaw

The UK's leading careers platform for aspiring lawyers. We run its engineering: we moved it to the cloud and rebuilt the whole website in a new brand.

Industry
Legal Education & Recruitment
Country
United Kingdom
Timeline
Since 2025, ongoing
Team
5 engineers
AllAboutLaw
0days of downtime

The move to the cloud and the rebrand happened without stopping the business.

24weeks to the new website

From the start of the rebrand to the new site running in production.

31weeks to the full switch

Until the old site was switched off for good.

01 Starting point

Where the client was

AllAboutLaw is the UK's leading careers platform for aspiring lawyers. It brings students together with law firms through events, virtual placements, a jobs board and careers content. In spring 2025 AllAboutLaw was looking for a team to run the engineering of the platform. A move to the cloud had been started by a contractor and had stalled, the site was unreliable during live events, and work on new features had stopped. Codino took responsibility for all of it: the code, the infrastructure, the releases and the plan for what gets built next.

AllAboutLaw needed one partner responsible for the whole platform: someone to finish the stalled move to the cloud, keep the site running when tens of thousands of students arrive on event days, keep delivering what sponsors pay for, and replace the entire website with a new brand without losing the search traffic and leads the business lives on.

02 Timeline

From day one to a new website

  1. Spring 2025

    We start work on the platform

    We make it possible to release changes safely again and set up a test environment.

  2. September 2025

    The platform runs in the cloud

    Production is switched over in the first week of September.

  3. October 2025

    Full handover

    The previous contractor hands everything over to us.

  4. March 2026

    The rebrand starts

    We agree the design rules first, then build the new site page by page.

  5. Week 24

    New site running in production

    Ready and tested, not yet visible to visitors.

  6. Week 27

    Visitors move to the new site

    Gradually, from a small share to everyone, with a switch that brings the old site back in seconds.

  7. Week 31

    Old site switched off

    The rebrand is finished without a single day of downtime.

03 What we did

What we delivered

01

Responsibility for the platform

We learned the whole system without documentation or a handover. Within a few months we were the team that releases changes, watches the platform and fixes problems.

02

Move to the cloud

We finished the migration the previous contractor had started. Production switched to the new infrastructure in the first week of September 2025, and the whole setup is now described in code instead of living on a single server.

03

A site that holds up under load

We removed the bottlenecks that made the site unreliable on event days. The site now adds capacity on its own when traffic grows, and monitoring shows a problem before users report it.

04

New features the whole time

Product work did not wait for the technical work to finish. In that time we delivered registration for several events at once, the Commercial Awareness Compass series, lead delivery to sponsors, simpler login, analytics and campaign pages.

05

New brand, new website

We rebuilt the whole public website in the new brand. Visitors were moved to it gradually, starting with a small share, with a switch that could bring the old site back in seconds.

06

Search traffic protected

Old addresses redirect to the new pages and every page carries the information search engines look for. Search engines kept seeing the old site until the new one was ready.

04 What changed

The platform when we started and today

InfrastructureBeforeA single server and a stalled cloud migrationAfterCloud infrastructure that adds capacity when traffic grows
ReleasesBeforeNo safe way to release changesAfterEvery change is tested automatically before it goes out
Event daysBeforeUnreliable when traffic peaksAfterMonitored, with problems visible before users report them
New featuresBeforeWork on new features had stoppedAfterNew features delivered the whole time
WebsiteBeforeThe old site and the old brandAfterA new website in the new brand
05 How we worked

How the work was run

We started by taking the risk off the client. In the first weeks we made it possible to release changes safely again and joined the unfinished cloud migration. Production moved to the new infrastructure in September 2025, and in October the previous contractor handed everything over. We treated performance as ongoing work, not a single fix. Every change was measured, so we knew what actually helped. New features kept going out the whole time. The rebrand began in March 2026. We agreed the design rules first, which made every later page quicker to build. The new site was running in production after 24 weeks, visitors started moving to it three weeks later, and the old site was switched off in week 31. The business did not stop for a single day.

A platform that was hard to change became one the client can change every week, and both the move to the cloud and the rebrand happened without a single day of downtime.

Scope of work

We own AllAboutLaw's engineering end to end: code, infrastructure, releases and roadmap.

Learning the codebase, restoring the ability to build, test and deploy, and covering on-call duty.

Finishing the migration from Plesk to DigitalOcean Kubernetes, moving the databases, and bringing cluster, services, monitoring and Cloudflare into Terraform.

N+1 fixes, new indexes, Flyway, Redis and Caffeine caches, edge caching rules, tuning of the connection pool and the JVM, autoscaling and full observability.

Events, Compass, sponsorship and lead delivery, SSO and accounts, jobs and law firms, Academy, analytics and campaign tooling across the whole ecosystem.

A Next.js application, a versioned REST API, a design system and an admin app, delivered from first commit to dark release in 24 weeks.

A Cloudflare Worker canary from internal to 100%, crawlers kept on the old site, redirects, sitemap and structured data, with the old frontend removed at week 31.

Technologies

Next.js 16 + React 19 + TypeScript
Java
Spring Boot
MySQL
Redis
BigQuery
Kubernetes + Terraform + Helm
Docker + GitHub Actions

Let's Talk About Your Project

Get In Touch
Maciej Roman|CEO & Co-founder

Not sure where to start? Begin with the AI Readiness Audit