About Lightfin

The person who walks the floor builds the system.

Every conversation is with founder Dmytro Lukanov — the engineer responsible for your automation, not a salesperson or account manager.

He brings 20 years of experience in business automation and leads every decision from Portland–Vancouver. Lightfin’s experienced engineering team in Ukraine works under his direction.

Experience
20years in business automation
Lightfin
4years building operational systems in the United States
Accountability
1engineer responsible for every conversation and decision
Systems specialist walking a fabrication floor with an operations manager
The work starts on site

Founder

Dmytro Lukanov — from the floor to the full system.

The useful part is not a list of technologies. It is standing in your operation, finding where information is recreated instead of reused, and understanding the workflow well enough that the right system stops looking mysterious.

Then comes the engineering: web, mobile, integrations, data, infrastructure, and the operational backbone beneath them. Dmytro remains accountable from the first floor walk through the Monday morning when people depend on it, working with Lightfin’s engineering team in Ukraine.

A consistent way of thinking

Three environments. One approach.

02 · United States

Transportation & logistics

Operational technology work at Skyline Transport Group, then co-founder and engineering lead at Verified Carrier — carrier verification, freight workflows, operational visibility, data, and integrations.

03 · Today

Product engineering

Native mobile applications, web platforms, portals, APIs, containerised infrastructure, and data systems — designed together rather than assembled.

Engineering depth

Built to stay correct as the business grows.

01

Systems that keep working as they grow

Operational systems get slower in specific, predictable ways. Experience includes transportation datasets in the tens of millions of records, with derived data beyond a hundred million — where the difference between a usable system and an unusable one is query design, not hardware.

02

Built to be operated, not just delivered

Containerised infrastructure, queues and asynchronous processing, monitoring, and modern authentication. Software that someone has to run at 6am on a Monday is designed differently from software that only has to demo.

03

Correctness where money is involved

Costing and settlement logic written as pure, testable functions — separate from screens, transport, and authentication — because logic that can only be tested through a browser never actually is.

Start with the operation

Show us where it breaks.

Portland, Vancouver, and the surrounding region — on site when the problem needs to be seen, not guessed.

Show us how it works