MULTINATIONAL · INTERNAL PLATFORM
An internal ops platform: availability, PIM, ticketing and dashboards over three databases
One internal platform over three databases — availability planning, product information, ticketing, per-team dashboards and a deployment log — instead of five tools that do not talk to each other.
AT A GLANCE
The situation
Operational work was spread across tools that each held part of the picture: availability in one place, product information in another, issues in a third, reporting exported by hand from all of them. Every cross-cutting question required a person who knew which tool held which fragment.
What was built
A single internal platform on Nuxt and Laravel, reading across three databases, presenting one interface to the people doing the work.
- Availability planning, on the same data the rest of the platform uses.
- Product information management — the attributes, media and relationships that downstream systems consume.
- Ticketing with priority levels, so operational issues are tracked where the operational data is rather than in a separate tool.
- Dashboards built per team, on shared data, so two teams looking at the same metric see the same number.
- A deployment log visible inside the application, so users can see what changed and when.
Why the deployment log is in the product
Internal tools acquire a reputation for changing under their users. Putting the deployment log where the users are — rather than in a channel they do not read — converts a source of suspicion into a routine line of text.
What changed
Three databases and several previously separate tools behind one interface, with each team's dashboard drawn from the same underlying numbers.
The systems are real. The client is withheld here by default.
STACK