01of 05
Replace the legacy backend foundation
- Migrated from a custom PHP framework to Leaf MVC
- Refactored into a cleaner, more maintainable structure
- Improved developer experience and long-term scalability
Bitkern
A new foundation for a platform that had outgrown its own.
Our roleBackend, frontend + CMS
Client
BitkernScope
5 workstreamsBuilt with
Leaf MVC, Leaf Lingo, Craftly CMSTeam
Andy + Michael01 · The context
A platform that had outgrown its foundation.
Bitkern’s platform had grown over time on a custom in-house PHP framework. As the product evolved, it became harder to maintain, extend, and scale.
Simplify the platform, modernize the stack, and reduce future maintenance risk.
Before and after
Backend
Translations
Frontend
Content
02 · What we did
Five pieces of work, one clearer system.
02of 05
Move translation logic into one system
- Replaced a complex routing and middleware setup
- Implemented Leaf Lingo for streamlined localization
ResultOne Leaf Lingo integration instead of scattered i18n logic.
03of 05
Cut interaction delays
- Modernized JavaScript structure and DOM updates
- Optimized key interactions such as cart updates
ResultReworked the frontend JavaScript behind user interactions.
04of 05
Harden critical request paths
- Strengthened the application’s security posture
- Reinforced critical areas of the system for stability
05of 05
Give the team direct content control
- Migrated the whole frontend: landing pages, marketing pages, blog
- Integrated Craftly CMS, a block-based content system
ResultPages and posts published without a developer.
03 · What we learned
The biggest improvements came from simplifying complexity.
Clear systems scale better than complex ones.
Faster interactions
A more responsive platform across the board
Clearer code
A maintainable codebase ready for growth
One translation system
Simpler internationalization workflows
Content in the team’s hands
Full control for non-technical people
Next case study
Selll→