About Pylaros

Hi, I’m Lukas.

I founded Pylaros to build custom software for telecom teams. Five years in installation and project engineering taught me where the work slows down, what gets repeated, and which details matter.

Lukas Jasinskas
01 / Background

From the tower to the office.

On site, I learned that documentation follows the work: photos accumulate across phones and days while the team focuses on the installation.

In the office, I saw what it takes to turn that evidence into a delivery: reconcile the documents, check the requirements and resolve the gaps. Pylaros grew from seeing both sides.

  1. 2021

    Tower technician United States

    Tower climbing and rigging at height, microwave alignment, installing and troubleshooting radio equipment.

  2. 2021–2022

    Field team lead Germany

    Led a team on base station installations and worked alongside them: integration, testing, troubleshooting, and the photos and closeout documents that go with it.

  3. 2022–2026

    Project engineer Norway

    Technical designs, site surveys and bills of quantities for mobile network rollouts, working with stakeholders on quality requirements and site-specific solutions.

  4. 2026–

    Pylaros Oslo

    Building software for the work between the site and the office.

02 / Working together

You talk to the person building it.

Bring me a task that takes too much time or causes repeat work. We define the outcome, agree the scope, price and delivery plan, then review the software together as I build it.

Your team tests the software before handover. Hosting, ownership, documentation and ongoing support are agreed as part of the project.

Tell me about your project
03 / See the work

Try my approach to review.

Good software makes decisions easy to inspect: where a result came from, what was checked and what needs a person’s judgement.

The photo demo puts that into practice. Correct a suggested match, confirm the evidence and download your reviewed set.

Try the interactive demo
04 / Get in touch

What needs to
work better?

Tell me which task slows your team down and what you’d like to improve. A few sentences are enough; you don’t need a finished specification.

I’ll reply personally with any questions and a practical next step. If a call would help, we’ll arrange one by email.

Or email me directly:

hello@lukasja.dev

I’ll use your details to respond to this enquiry.