Skip to content
LARMORLAB

METU alumni team · HAB Aerospace Zone, Ankara

Working systems forcritical operations.

We build production tracking and operations ERP for defence industry companies, and robotic process automation (RPA) for international manufacturing plants.

Explore the projectsDiscuss your project

Production ownership

OKTrack runs in production operations at OKAS today. The team that builds it also owns releases, incident response and operational continuity. There is no extra layer to pass responsibility to.

¹ Figures as of August 2026. Work still at research stage falls outside the scope of this statement.

Selected projects

01

OKAS OKTrack

Operations Division

Active in production at OKAS

The operations platform that runs production at OKAS, a supplier to the defence and aerospace industry. Every movement is traceable, from incoming inspection and operation routing to treatment stations, audit and invoicing.

  • 23 operational screens
  • 24-collection data model
  • Surface treatment and machining
  • Mobile flow for shop-floor teams
See the project
02

Lazzoni RPA

Operations Division

Completed and delivered

Robotic process automation taking over repetitive steps in the enterprise processes of Lazzoni, a furniture and interior architecture company. The manual work between existing systems moved into software without replacing those systems.

  • Manual steps between systems
  • Rule-based, repeatable execution
  • Run status and failure record
  • No change to existing systems
See the project

Who we work with

We build systems connected to real processes, not requirements described from a distance.

An engineering culture shaped at METU

Critical systems need ownership.

Every founder and team member at Larmor Lab is a METU graduate. That shared engineering culture guides how we learn the operation, design for failure and stay accountable in production.

We learn the operation

We model the work, not the screens. Development starts after we understand the user's decisions, the source of the data and where the process can stop.

We stay in production

The first release is not the finish line. Monitoring, incident response, capacity and release management continue the engineering work.

We design for traceability

State changes, permissions and decision records are not reports added later. They belong in the system's core.

We build for handover

Code, data models and technical decisions remain clear enough for another team to take over. Ownership does not mean creating dependency.