Design the open automation layer before a single cable is pulled

For new builds and deep retrofits where no proper automation layer exists yet. puniq engineers the vendor-neutral, open-protocol foundation your building will run on for the next twenty years, then hands you the blueprint and the data map to keep.

Open-protocol by design Hardware Shield you own the kit GEG §71a ready

When it applies

A blueprint, not an audit

Our Data Auditor exists for buildings that already run five or more vendor systems and need them unified. The Infrastructure Blueprint is the opposite starting point. Here there is nothing to unify yet, because the automation layer has not been built. Getting it right at design time is far cheaper than fixing it after handover.

This is the right engagement when:

You are planning a new commercial, residential or mixed-use development and the controls package is still on the drawing board.

You are gutting an existing asset in a deep retrofit and want to replace ad-hoc controls with one coherent layer instead of patching the old mess.

You are about to sign a controls contractor and do not want to be locked to whatever proprietary ecosystem they prefer to sell.

You need the building to satisfy GEG §71a automation and monitoring duties, and to produce clean data for EU Taxonomy and CSRD reporting from day one.

Decisions made at design stage either open the door to clean, reportable data or quietly nail it shut.

What we design

One open-protocol layer, built from the ground up

We specify a building management system built on open protocols from the first decision, so HVAC, lighting, metering and access do not arrive as four sealed islands. They arrive as one readable layer with a single, documented language. No black boxes, no vendor that holds your data hostage.

Yours to keep

Unified data layer and reporting

One readable model, closed with the Documented Data Map, GEG and CSRD ready from day one

Open protocol bus

BACnet · Modbus · MQTT

One documented language every subsystem speaks, with no proprietary gateways in the way

Field layer, specified open

HVAC and energy, lighting, metering, access

Exact, open, interchangeable controllers, sensors and meters, bought and owned by you

Every subsystem, specified open

Four islands become one readable layer

⚙

HVAC and energy

Heating, cooling, ventilation and on-site generation specified on open protocols (BACnet, Modbus, MQTT) so every setpoint, sensor and meter is exposed and controllable, not buried in a proprietary controller.

☀

Lighting

Lighting control designed to publish occupancy, schedules and consumption into the same layer, so it can be optimized alongside HVAC rather than run on its own private island.

☷

Metering

Sub-metering laid out for clean, granular energy data from day one, the raw material every Taxonomy, CSRD and GEG report depends on.

🔒

Access and safety

Access control and safety systems integrated into the readable layer where appropriate, with the right boundaries kept for security-critical functions.

The Hardware Shield

★We specify, you own

puniq is an asset-light software company. We design the controllers, sensors, gateways and network you need, and we name exact, open, interchangeable parts. The hardware is bought by you, installed by your contractors, and owned by you. Nothing sits on our balance sheet, so we have no incentive to over-specify boxes to hit a hardware margin.

No hardware markup hidden in the design fee

Open, interchangeable parts you can source competitively

Any qualified integrator can install and service it

Lower regulatory friction software advice, not an equipment vendor

The asset stays yours fully and permanently

Exact, open, interchangeable parts you own

How we work

Vendor-neutral, alongside your contractors and integrators

We design, you tender

We produce the open-protocol blueprint. You take it to market and tender it competitively, because every part and protocol in it is open. No supplier is pre-baked in.

We brief your integrator

We work directly with your chosen controls contractor and MEP team, hand over the specification, and answer the integration questions so the build matches the design.

We verify at commissioning

At handover we check that what was installed actually exposes its data the way the blueprint requires, then capture it in the Documented Data Map.

We never become a dependency you cannot remove. The whole point of the Blueprint is that any competent integrator can build it, any competent firm can maintain it, and you can change either one without re-engineering the building. That is what vendor-neutral means in practice, not as a slogan.

Why now

The building you design now is judged on its data later

The German BMS market is moving from USD 1.53B in 2024 toward USD 9.88B by 2035. Buildings designed now will be judged on the data they can report for the next decade. Specify the open layer first and that data is yours, not a vendor's.

GEG §71a, from day one

Designing for automation and monitoring duties at the blueprint stage is far cheaper than retrofitting them after handover, and it produces the documentation an inspector will ask for.

◎

EU Taxonomy and CSRD

Clean, granular metered data designed in from the start is the raw material every Taxonomy and CSRD report depends on, drawn from real readings rather than annual estimates.

Client testimonials

puniq brought real structure to a project we expected to stay messy. They designed the system around our goals, not a product catalogue.

Houssem BaakaFounder, Saura Agency

Questions

The questions developers actually ask

Do you sell or install the hardware?+

No. We specify exact, open, interchangeable parts, but you buy them and your contractors install them. Nothing sits on our balance sheet. This is the Hardware Shield, and it keeps our advice independent of any equipment margin.

Will we be locked to puniq afterwards?+

No. The blueprint is built on open protocols so any qualified integrator can build and maintain it. You can change contractors, or us, without re-engineering the building.

How is this different from the Data Auditor?+

The Data Auditor unifies systems you already have. The Infrastructure Blueprint designs the layer from scratch where none exists yet, for new builds and deep retrofits. Both close with the Documented Data Map.

Can we run AI optimization on top later?+

Yes, and that is the point of doing it right now. A building designed on the open layer feeds clean data straight into our AI Optimization service for benchmarking, forecasting and compliance reporting, which stays advisory and human-in-the-loop.

Does this help with German and EU regulation?+

Yes. Designing for GEG §71a automation and monitoring duties, and for clean EU Taxonomy and CSRD data, is far cheaper at design stage than retrofitting it after handover.

Building from the ground up? Get the layer right first.

Tell us about the project and where it stands. We will map the open, vendor-neutral automation layer it should be built on.

See Data Auditor

DE FR ES TR ع