Engineering work, with its origin stated

These are 15 documented engineering projects. Each one states its origin: internal product, independent work, R&D or academic project. Most are academic or R&D, and none is presented as paid client work.

The projects below are engineering work, not a client portfolio. Every one carries a label that tells you where it came from, because a reader deciding whether to trust us should know whether a project was a product, independent work, research or a university assignment.

What are these pages?

Each project page describes a problem, what was built, the technical approach and how the result was checked. We wrote them to be specific enough for an engineer to judge. The projects span software systems, data, AI, FPGA, embedded and Linux.

Why does every project show its origin?

Because it is honest, and because it makes the evidence usable. There are four origins:

  • Product: engineering done for a product we built.
  • Independent: work done on our own initiative.
  • R&D: research and experiments.
  • Academic: university engineering projects.

Of the 15 projects, 13 are academic or R&D, one is an internal product and one is an independent project. None is a paid client project. We have no client case studies yet, and we do not present these as if they were. Our live proof is our three products.

What do they show about the team?

They show range and depth. The work includes streaming image processing on FPGA in VHDL, embedded C firmware with IoT telemetry, distributed geospatial analytics, machine learning on satellite images, Linux kernel and filesystem work, and an interoperability platform for toll operators. This is the engineering background of the team behind the studio.

How should I read a project page?

Start with the origin label and the one-line evidence at the top. Then read the problem, what was built and the technical approach. Where a project lists how it was checked, that is the part to weigh most. If a page says a project was an academic assignment, treat it as evidence of skill, not as a record of running a service for a customer.

How does it connect to our services?

If you have a problem like one of these, tell us about it.

Our own products and internal systems

Independent builds

Academic engineering projects

Tell us what you want to build.

A product, a website, a search problem or a system that should work better. We reply with a plain answer and the first step.

Email
[email protected]
Phone
+30 698 179 8240

A few sentences are enough (at least 20 characters).

We use your details only to answer your inquiry. See our privacy policy.