Software engineering
Web applications, operational platforms and backends built around real workflows. From access control and multi-tenancy to real-time data and internal engineering tools.
TypeScript / React / Node.js / PostgreSQL / Rust
Independent engineering / Netherlands
Engineering systems that work in the real world.
Hardware. Software. Infrastructure. One engineering partner. We build products, platforms and internal systems for problems that off-the-shelf software cannot solve alone.
Rotterdam / Waalhaven5 example assets
Loading map…
Generator 60 kVA
Operating- Load
- 42 %
- Coolant
- 78 °C
- Last report
- 10:41:48 UTC
EventMachine readings received
Equipment trailer
No recent report- Battery
- 72 %
- Motion
- Stationary
- Last report
- 08:26:12 UTC
EventScheduled report not received
Drainage pump
Operating- Pressure
- 2.4 bar
- Flow
- 18 m³/h
- Last report
- 10:41:35 UTC
EventPressure and operating input received
Mobile crane
Operating- Engine speed
- 1,250 rpm
- Hydraulics
- 184 bar
- Last report
- 10:41:52 UTC
EventService due within 20 operating hours
Workboat
Stationary- Speed
- 0.0 kn
- Bilge alarm
- Inactive
- Last report
- 10:39:10 UTC
EventStationary state and shore power confirmed
2. Follow the message
A machine signal is measured. Follow how it becomes useful information.
- 01Software engineering
- 02Embedded & hardware
- 03Integrations & infrastructure
- 04Research & prototyping
01 / Engineering, end to end
The difficult part is making it all work together.
The difficult part is rarely just the app, device or backend. It is everything between them. We engineer complete systems, and help existing ones become more understandable, testable and maintainable.
Embedded & hardware
Firmware, sensors and connected devices that interact with the physical world. Including the interfaces, diagnostics and test tooling around them.
Microcontrollers / BLE / Wi-Fi / Data acquisition
Integrations & infrastructure
Connect APIs, legacy systems and databases with clear ownership and failure behaviour. Queues, background workers and deployments are part of the system.
APIs / Event processing / Containers / CI/CD
Research & prototyping
Investigate the unfamiliar and test the difficult assumptions. A useful prototype produces working evidence—not just a presentation about what might work.
Feasibility / Protocols / Performance / Validation
02 / Software you can inspect
Not just concepts. Explore the work.
Our open-source projects make the software side tangible. Browse the interfaces, documentation and source alongside our connected-equipment work.
CaddyUI
A self-hosted interface for the Caddy reverse proxy.
03 / A system we are developing
Different equipment. One operational view.
PolderNode + Fleet Manager bring our hardware and software work together. A connected equipment platform for mixed fleets, older machinery and assets that do not fit neatly into one telematics system.
PolderNode · In development
Fleet Management
- Visibility
- Know where equipment was last reported.
- Utilisation
- Understand when machines are being used.
- Events
- Identify movement, power and equipment-specific signals.
Application-specific sensors and integrations are explored through pilots.
Sense & connectPolderNode
GNSS · I/O · LoRaWAN
Understand & integrateFleet Manager
Location · Utilisation · Events
System concept · application-specific configuration
Built around the equipment
A trailer does not need to report like a generator. We start with what needs to be known, then choose what to measure and how to connect it.
- Generators & pumps
- Trailers & rental assets
- Construction machinery
- Boats & marine equipment
Engineering beyond the happy path
Designed for when things go wrong.
A system is not finished because the demo works. Failure handling, diagnostics and maintainability belong in the architecture—not at the end of the project.
01
A connection disappears
Buffer locally, reconnect and synchronise deliberately.
02
A message arrives twice
Idempotent processing prevents duplicate actions.
03
An external API is unavailable
Bounded retries, queues and visible failure handling.
04
An operator needs answers
Logs, diagnostics and a comprehensible event history.
04 / A practical starting point
Bring the problem. We’ll work out the next step.
You might need a specialised platform, a reliable integration, connected equipment or a prototype ready for its next stage. You do not need a finished specification to start a conversation.
How we think and work- 01
Understand the context
What exists today, what is missing and who needs the outcome?
- 02
Test the difficult part
Build enough to make the technical risks visible.
- 03
Decide with evidence
Use the results to choose what to develop, integrate or change.
Let’s start there
Build something that does not exist yet.
Bring us the problem. We will help engineer the system around it.
Discuss your challengePolderLabs
Let’s talk.
A technical question or an idea? Talk directly with an engineer.
Send an emailinfo@polderlabs.ioTell us about your projectOpen the contact form