Services · Ship
Backend platforms & ERPs
Laravel, Vue and Inertia for the systems a business runs on: ERPs, POS, CRMs, trading back-offices.
What it takes
- From
- $3,200
- Typical delivery
- 14 weeks
A written estimate comes first. The figure above is a starting point, not a price list.
The service
What it is.
We build the platforms that businesses run on — not the marketing site that points at them. The stack is Laravel + Vue + Inertia + MySQL or PostgreSQL, with Redis and Horizon for everything async, Filament for the admin surfaces nobody wants to design twice, and Pest for the test suite that survives the next three engineers. We’ve shipped MetaTrader 5 back-offices for retail forex brokers, multi-branch POS systems for retail chains, ERPs that replaced spreadsheets twelve tabs deep, and CRMs with bespoke workflow engines for service businesses. The stack is unfashionable. The systems run.
What we build it with.
- Framework
- Laravel
- UI
- Vue 3 + Inertia
- Database
- MySQL / PostgreSQL
- Queues / cache
- Redis + Horizon
- Admin
- Filament / Nova
- Testing
- Pest + PHPUnit
- Trading
- MetaTrader 5 Manager API
- Runtime
- Octane / FrankenPHP
What ships
6 things
you get.
Repos, dashboards and runbooks are yours from the first commit.
ERP modules
Inventory, orders, finance, HR, procurement — wired as modules over a single core, not as siloed apps.
Point of sale
Offline-first till, multi-branch sync, cash drawer + receipt printer integrations, end-of-day reconciliation.
CRM with bespoke workflow engine
Lead / deal / ticket pipelines you can configure without redeploying. Webhook triggers, scheduled actions, audit trail.
MetaTrader 5 / forex back-office
Broker dashboards, IB tree and commission engine, deposits / withdrawals, KYC, MT5 Manager API integration.
Role-based access + full audit log
Granular permissions, impersonation for support, every mutation logged with who-when-where. Compliance-ready.
Multi-tenant where it makes sense
Single-database multi-tenant with row-level isolation, or separate databases per tenant. We pick what fits the operations.
Timeline
4 phases,
in order.
14 weeks,
start to finish.
DiscoveryWeeks 1–2
Core modulesWeeks 3–6
Domain modulesWeeks 7–11
Hardening + cutoverWeeks 12–14
Questions
4 questions
we get.
Why Laravel and not Node?
Operational systems live for ten years. Laravel's eloquence around domain models, queues, scheduling, and admin tooling beats anything in the Node ecosystem for this shape of work — and PHP 8 + Octane is fast enough that the 'is PHP slow' debate stopped mattering. We use Node when the workload is event-driven and edge-shaped.
Why Inertia and not a separate SPA?
Internal platforms have hundreds of screens, complex permissions, and one team. Inertia gives you Vue 3 ergonomics on the front end with Laravel's routing, validation, and authorization on the back end — no API to keep in sync, no auth duplication, no CORS theatre.
How do you handle MetaTrader 5 specifically?
We integrate via the MT5 Manager API for back-office operations (account creation, balance ops, position queries) and Gateway API for trade-feed ingestion. We've shipped IB / commission engines, broker dashboards, and KYC / deposit flows wired into MT5 — including the parts the official documentation skips.
Can you take over an existing Laravel codebase?
Often. We start with a one-week audit (code, infrastructure, runbooks, test coverage, security). You get a written assessment with a fix list and a takeover plan. About half of our retainers start this way.
Start
Send a brief.
We reply within one working day with a written estimate or a call.
No newsletters. Your details aren't shared.
Or say hello.
Sunday to Thursday, 09:00–18:00, GMT+4. Remote engineers cover the EU and the US asynchronously. We work in English, Arabic and Urdu.
