Peinser is a European engineering team for work that crosses research, platform engineering, and aerial robotics. We help you choose the right approach, prove it, and put it into operation.
Flightdeck · Design-partner alpha · Browser-native UAV operations
Applied research, machine learning, and engineering R&D for questions without an off-the-shelf answer. We produce reproducible prototypes, peer-reviewable results, and a clear path from evidence to production.
Distributed systems, cloud infrastructure, CI/CD, and observability for teams whose platform has become a delivery constraint. We design the target, ship the first production slice, and leave your team able to run it.
Pilot workstations, mission planning, field tooling, payload integration, and autonomy engineering for custom fixed-wing, VTOL, and multirotor systems.
Technical audits, discovery, and decision memos for teams facing an expensive or difficult-to-reverse choice. We make the options, evidence, costs, and risks explicit before you commit.
Flightdeck brings terrain-aware mission planning, live flight operations, video, traffic, RTK, radio, and vehicle tooling into one private browser workspace.
Generic ground stations are broad by design. We configure Flightdeck around the airframe, autopilot, payload, communications, and operating constraints your team actually uses.
Long enough to resolve the important uncertainty. Short enough to act on the result. We agree the question and decision criteria up front, then finish with evidence, a decision, and a working first slice where appropriate.
Read the literature, the code, the data, and the runbooks. Talk to operators and end users. The deliverable is a findings memo with explicit assumptions and open questions.
A small set of options, each with a cost, a risk profile, and an owner. We choose together; the choice — and the rationale — is the deliverable.
Put the decision in front of real users, real infrastructure, or a representative flight environment. The output is a thin, instrumented slice and a concrete plan for what follows.
The hardest engineering decisions are rarely about what to build. They are about what to keep running, what to deprecate, and which version is worth the cost of operating. — Internal note · Wk 03 · Aerial inspections engagement
Products we build from recurring engineering problems. Try the public tools, inspect the open-source work, or talk to us about deploying them in your operation.
A federated CORS / RTK network for centimetre-grade GNSS.
An auditable community network of base stations that broadcasts RTCM corrections to anything with an RTK receiver; surveyors, agricultural rovers, and our own drones. Open protocol, open data, federated by design.
Project site →A small QUIC SNI router for pod-terminated mTLS and HTTP/3 services.
Reads the SNI from incoming QUIC v1 and v2 packets and forwards the original datagrams, untouched, to the right backend pod. TLS, mTLS, and HTTP/3 termination stay in the application; the router is one UDP ingress in front of many QUIC services. Built for Kubernetes, configured in YAML, fuzzed and containerised.
Project site →A document protocol for the full lifecycle: render, sign, archive, dispatch.
Teams repeatedly rebuild the same document plumbing: rendering PDFs from templates, versioning templates, signing output, assembling bundles, dispatching Peppol invoices, and archiving records for the required retention period.
Xarta consolidates the lot behind a DAG protocol. The submitter declares the flow; Xarta executes it deterministically. Plug-in template engines, templates versioned in git rather than locked in a vendor UI, Peppol BIS 3.0 in the same pipeline as everything else. On-prem by default.
Smart EV charging that follows the sun.
An open charging network with auditable sessions for employee cost recovery. Started as a side project; now an independent product with paying users across Belgium. Its OCPP interface gives operators control of their charging infrastructure, data, and workflows.
Visit Zonnetanken →Selected publications and code we have shared with the community. Most of this work feeds back into client engagements.
Tell us what is uncertain, what you have tried, and what a useful outcome would change. In the first conversation, we will test whether we are the right team and outline how we would approach the work. No prepared brief required.