Auridm Aero
ePDT: no more paper in the hangar.
An electronic aircraft technical log built with Laravel and Flutter. In production since 2023, saving around 40 man-hours per aircraft per month. AURIDM (auridm.aero) develops ePDT, an electronic aircraft technical log for aviation. It is a tool for the people who service aircraft and are responsible for their airworthiness. Gorilla was responsible for UX, architecture, back end, integrations and the entire application end to end. It was one of the most architecturally demanding projects in our portfolio.
- Double work. Entries were written by hand on paper, and then someone retyped them into other systems. Every retyping cost time and was a chance for error.
- Compliance risk. A paper log can be lost, soaked or damaged. In aviation, a missing record is a regulatory problem, not just an organizational one.
- No up-to-date view of the fleet. The technical condition of the aircraft was known only after the paperwork was collected. Planning relied on delayed information.
- Hours spent on admin. Handling documentation took up technical staff's time. That time wasn't going into the actual work on the aircraft.
- Strict domain rules. You have to define who enters what and in which order. Some entries block release to service, and the history cannot be edited.
A Laravel backend carrying the full domain logic, plus a Flutter app for people working by the machine, not at a desk.
- Domain logic in Laravel. We encoded the aviation rules in the back end, not in the interface. That way they always apply, regardless of the device.
- The log data model. We designed the structure of entries and their relationships first. The rest of the application is built on that model.
- Validation and permissions. The system checks whether a person is allowed to make an entry and whether the order has been followed. An entry that blocks release is visible immediately. An aircraft with an open defect never looks ready to fly in the system.
- Auditable history. Entries cannot be overwritten. Every change stays in the history, which meets the requirements of aviation documentation.
- Flutter and a single codebase. The app runs on multiple devices from one codebase. A fix or a new feature reaches every device at once.
- UX built for the hangar. We designed for work next to the aircraft, often in a hurry and on a tablet. What matters is quick entries, minimal steps and resistance to mistakes. Required fields are clearly marked, and the system stops an invalid entry before it is saved.
- Integrations instead of retyping. We connected the app to a calendar and data export. Information entered once goes wherever it's needed.
- An electronic technical log. Entries are created directly in the app, with validation and permission checks. The step of retyping from paper disappears. Data is available to the team moments after it is entered, not after the sheets are collected.
What changed.
Data regarding time savings comes from the client and applies to technical documentation handling per single aircraft.
Is your technical documentation still on paper?
We'll design a system that keeps the rules and the history for you. In regulated industries, the hardest part is the logic, not the screen. When the rules live in the back end, they always apply and are easy to audit. Flutter lets you maintain one app across many devices, which lowers development costs. It also pays to measure the impact in man-hours per unit, because that figure scales easily to an entire fleet or machine park.
Let's talk about your system →