Bespoke Cloud Apps & Services
Laravel, APIs and backend systems for real businesses – plus game backends and glue code.
I build web and cloud apps that sit behind shops, training platforms and games. Most of the work is somewhere between “off-the-shelf SaaS is too generic” and “we don’t want a 20-person team to keep the lights on”.
The tools are boring on purpose: Laravel, Bootstrap, MySQL, Linux servers. The point is to ship something maintainable, not chase the latest framework trend.
Typical clients
- Shops and training businesses that have outgrown spreadsheets.
- Small teams who inherited a half-finished Laravel app.
- Game devs who need a basic backend for scores / telemetry.
What I actually build
Business & platform work
- Multi-tenant web apps (multiple shops or clients in one system).
- Order management, subscriptions and digital product delivery.
- Admin dashboards, reporting screens and simple analytics.
- Customer and staff portals with role-based access.
APIs & integrations
- REST APIs for mobile apps, internal tools or third parties.
- Stripe / PayPal integrations for one-off payments and subscriptions.
- Glue code between existing systems (CRMs, booking tools, etc.).
- Background workers for imports, exports, notifications and clean-up.
Game-related services
- Lightweight backends for Unity titles (scores, profiles, unlocks).
- Telemetry collection to see what players are actually doing.
- Remote configuration of game settings and balancing values.
Tech stack
Backend
- PHP / Laravel
- MySQL / MariaDB
- Queues / jobs
Frontend
- Blade templates
- Bootstrap 5
- Vanilla JS / light Vue
Hosting
- Linux servers
- Basic CI / Git
Games
- Unity / C# client
- HTTP/JSON APIs
How I like to work
- Clear scope, then build in small, shippable chunks.
- Fewer moving parts rather than “microservices for everything”.
- Honest about trade-offs and what we can realistically support.
Ways we can work together
Project-based
Fixed scope where we agree what needs to exist, then build that in phases. Good for greenfield apps or clearly bounded rebuilds.
Retainer / ongoing support
A steady number of hours per month to keep an existing system alive, fix bugs, and add small features without spinning up a new project every time.
Employment
I’m also open to a permanent role if the work lines up with what I’m already doing: Laravel, Unity, operations-type systems. See the CV / Hire Me page for more detail.
Rough process
- Short call / email thread. What are you trying to fix or build?
- Quick outline. I sketch the simplest thing that could work.
- Estimate. Ballpark time/cost, and what fits in v1.
- Build. We work in small milestones with something demoable early.
- Hand-over. Code in Git, basic docs, and a simple deployment story.
If you already have a half-working Laravel or Unity project, we can start with an audit instead: what’s salvageable, what should be replaced, and how to stop it falling over every week.
Example work
Ramtronik OMS
Multi-tenant Office Management System used as the base for training and retail-style workflows: products, orders, subscriptions and reporting.
More on OMSTraining / content platforms
Backend and content pipelines for training-catalogue style apps, including mobile clients and subscription handling.
See overview
West Midlands Buses (England)
A cloud based bus tracking and timetable tool, available for iOS.
View gamesGot something specific in mind?
If you have a rough idea, a half-finished project or an existing system that’s creaking, send a short email with where you are now and what “better” looks like.
Email: hello@ramtronik.com
A couple of bullet points and any hard deadlines are enough to start a sensible conversation.