Malto Birreria: a custom management tool for draft beers - init.d - Linux systems, DevOps and PrestaShop development

Malto Birreria: a custom management tool for draft beers

Client:Malto Birreria (Riccione, Italy)Year:2025

https://www.maltobirreria.it
Malto Birreria: a custom management tool for draft beers

Malto is a Riccione pub specialising in craft beers on tap, burgers and dry-aged meat. A pub with many rotating taps needs to know at any moment what's connected, what's running low and what to show on the taplist: that is why we designed a dedicated tool.

init.d built a custom management tool:

  • Draft beer management: active kegs, history, rotation and availability.
  • An always-up-to-date taplist, ready to show to customers.
  • A simple interface designed for daily use behind the bar.
  • Infrastructure on Google Cloud with backups and updates handled by us.

What does draft beer management software need to handle?

It needs to follow each keg's path, from arrival in the cellar to the last pint. In a craft-beer pub the taps change often: one beer runs out, another takes its place, some come back weeks later. The tool keeps track of which kegs are active and on which tap, which are waiting and which are finished, and keeps the history of beers served. The taplist comes from this data: the list of beers available at that moment, with the information people need to choose. The principle is a single source of data: when a tap changes, the taplist changes too, without updating several lists by hand.

Why a custom tool instead of generic software?

Because software built around the pub's actual work uses its words, its steps and only the fields that matter. Generic hospitality software covers tills, tables and stock well, but tap rotation is a specific workflow with its own rules. A custom tool starts from that workflow and makes it fast: few actions, in the order they are really done behind the bar, during service. The benefit lasts over time too, because the software can grow with the pub, adding features when they are needed and without paying for modules that go unused. We describe our approach on the custom software page.

Why Laravel and Vue for a web-based management tool?

Because together they cover both the data side and the interface well. Laravel is a mature PHP framework that already provides the tools for authentication, data validation, database management through versioned migrations and scheduled tasks: you only write the project-specific logic, on proven and well-documented foundations. Vue handles the in-browser interface, so screens update instantly without reloading the page, a useful feature when the tool is used standing up, with little time and perhaps from a phone. The tool runs in the browser, so it needs no installation on the pub's devices. Data lives in a MySQL database.

How do you maintain custom software over time?

With the same method we use for servers: planned updates, tested backups and monitoring. The tool runs on Google Cloud and we look after it both as code and as infrastructure: we update Laravel, its dependencies and PHP, testing changes first in a separate environment, run regular database backups and verify them with restore tests, and apply system security updates. Having a single point of contact for development and servers means every change is assessed as a whole, on the code and on the environment it runs in. There is also a page on Laravel support.

The pub now has a single tool to keep its cellar under control and communicate the taplist. init.d handled both software development and infrastructure, with ongoing system administration.

Book a 30-minute call
Open in a new tab