Electronic aircraft technical logbook. The end of paper in the hangar.

Auridm Aero (auridm.aero) — a company delivering technologies and solutions for the aviation industry. Their product is ePDT, an electronic aircraft technical logbook system. Gorilla Software was responsible for designing and building the end-to-end product: UX, architecture, backend, integrations, and the end-user application.

01 Challenge & approach

× Before

Double work: the mechanic filled out the logbook manually, and then someone transcribed the data into office systems.
Compliance risk: a paper entry can be lost, damaged by liquids, or overlooked. In an industry where documentation is subject to audit, this is an operational risk, not just an organizational one.
Lack of a real-time fleet overview: the technical status of the machine was only known after collecting and transcribing the paperwork.
Wasted time: hours spent on administration instead of technical maintenance.
This is not a domain where you can guess. The logic of a technical logbook is a set of strictly defined rules — who can enter what, in what order, which entries block the aircraft's release to service, and what must be preserved in the history without the possibility of editing.

→ Our approach

A Laravel backend carrying the full domain logic, plus a Flutter app for people working by the machine, not at a desk.

Data model reflecting the structure of the technical logbook and dependencies between entries.
Validation and permission rules enforcing the correct sequence and completeness of entries.
Change history preserved in an auditable manner — entries are never overwritten.
Integrations with the client's other systems.
A single codebase for multiple platforms, ensuring consistent operation on devices used in the hangar.
UX designed for real working conditions: fast data entry, minimum steps, and resistance to errors.
The most difficult part of the project was the architecture — translating complex industry rules into a model that is formally correct, highly performant, and capable of being developed over years. The fact that the system has been running in continuous production since its 2023 deployment is the best validation of these decisions.

02 Technology stack

Laravel

Backend — technical-logbook domain logic, validation rules, auditable history, integrations.

Flutter

Application — a single codebase for multiple platforms, an interface designed for hangar work.

04 Results

What changed.

Paper and manual data transcription → ~40 man-hours per month per aircraft

Time savings

Paper technical logbook → Eliminated — the process is fully digital

Paper documentation

Fleet growth meant growing administrative work → Savings grow linearly — 10 aircraft mean ~400 man-hours per month

Scaling

What this means for you?

If your company maintains documentation subject to regulatory requirements — in aviation, transport, manufacturing, medicine, or energy — the exact same pattern applies: move the process from paper to a system that enforces correctness rather than hoping for it, and preserves a complete history for audit purposes.

Let's talk about your project →