Services ยท IoT-Cloud Engineering

Your cloud, our cloud, or none at all.

We develop the software between the device and the person using it: web interfaces on the device, services behind them, and the connection to the system you already run. Whether qdCloud is part of it is your decision.

Areas of work

What we develop

  • Front end and back end, made to fit

    Web applications that run on the device itself, and the services behind them. From the embedded web server for operation on site to the application that manages an entire fleet.

  • qdCloud, tailored to your needs

    Connection to your ERP, your own analyses or your own front end. The stack underneath can also be extended with additional services and your own interfaces, or switched to different data paths. Device management, updates and the certificate service come with the platform.

  • Connecting to your cloud

    If your infrastructure is already running, we connect the device to it: to your cloud, your web services, your existing interfaces. We build whatever the device needs for that. You decide where the data ends up.

The next generation of your device is hidden in the data of this one.

Our IoT cloud for device fleets

  • Your fleet at a glance

    Manage devices, see their state, find anomalies. The dashboards range from an overview of the whole fleet down to the individual device.

  • OTA updates

    Configurations and firmware reach fleets of any size securely. You control rollouts according to your own strategy and with system load in mind.

  • Remote access and operation

    Secure access to every device in the infrastructure, with live support and screen sharing. We run the platform ourselves and provide the same operation for the services we build for you.

View qdCloud
Logo qdCloud

Safety and evidence

  • We know the rules that apply to you

    NIS2, IEC 62443 and ISO 27001 are part of our everyday work. We tell you at the outset which of them affect your system and build the resulting measures straight into the architecture.

  • A management system under external audit

    Sales, development and manufacturing of electronic and electromechanical assemblies and systems are certified to ISO 9001. The information security management system behind them is built to ISO/IEC 27001 and is currently going through certification.

  • Access and roles

    We agree with you who sees which device and who may change it, and record it in the data model. Certificates for the devices; authentication and roles for the people.

  • CVE monitoring

    We monitor the libraries and images in your system and report new vulnerabilities to you as soon as they become known.

  • Security updates in operation

    We close the vulnerabilities we find in the running system. That is part of the operation we take on.

  • What machine builders face in 2027

    The Machinery Regulation makes cybersecurity part of the CE marking from January 2027. The associated standard prEN 50742 has been available as a draft since March 2026. We are tracking it and are already aligning your system with it.

  • NIS2
  • ISO 27001
  • IEC 62443
  • prEN 50742 (draft)

From planning to operation

On request as a fixed-price contract.

  1. Planning

    Requirements, system boundaries and risks. Plus the question that determines everything else: your own infrastructure, qdCloud, or the cloud you already have.

  2. Architecture

    How the services are split, the data model and the interfaces, plus the path the data takes from the device to the display. This is also where we settle who may see what.

  3. Development

    Every commit passes through build, tests and review. Working builds run early on a dedicated environment, so you can test early.

  4. Test

    Automated tests for each service, plus an end-to-end run from the device through the messaging layer to the user interface. With simulated devices, even before the hardware is in series production.

  5. Handover

    Source code, documentation and the description of the environment are transferred to you by contract. You can take over operation yourself or leave it with us.

  6. Operation

    Monitoring, security updates and new features in the running system. For as long as the devices are in the field.

How you can see the project status at any time

  • Access from day one

    Source code, configuration and release versions are open to you from the start of the project.

  • Requirements and tests in one system

    Requirements and tests are written, reviewed, released and versioned, so what was ordered can always be looked up.

  • Regular alignment

    A short meeting every one to two weeks: project status, open technical questions, organisational matters.

Products that save time in the project

  • Logo qdCloud
    IoT platform

    qdCloud

    Operation, monitoring and OTA updates for device fleets. Hosted in Europe or on your own infrastructure.

    View
    View
  • Logo qdCoreX
    Operating system

    qdCoreX

    Buildroot-based Linux with a mainline LTS kernel. The device side for updates, logging and certificates is already built in.

    View
    View
  • Logo qdHardwarePlattform
    Platform

    qdHardware Platform

    Hardware, a Linux base and the build system as a product. Your team starts from a base that already runs.

    View
    View

What we work with

Front end

  • TypeScript
  • React
  • Chakra UI
  • Vite

Back end

  • Go
  • Python
  • REST

Communication

  • MQTT
  • NATS
  • OPC UA

Databases

  • PostgreSQL
  • Redis
  • InfluxDB

Test tooling

  • Vitest
  • Playwright
  • Storybook

Runtime environment

  • Kubernetes
  • Kustomize
  • GitOps

Transparency from the start

Who owns the source code and the development data?

What we develop for you is transferred to you: design, software and manufacturing data, as set out in the development contract. Our own platform modules remain our product. Their documentation is held in escrow with an independent party, so you can carry on should we ever drop out.

Where is our data stored?

In Europe or on your own infrastructure. The set-up is the same; you decide where it runs.

Where is the work done?

In Offenburg, and nowhere else. We work with our own people. Whoever builds your services sits in the same building as the person who writes the firmware for them and the person who tests both.

What does open source mean for our product?

You cannot avoid open source, either on the device or in the data centre. We record which licence applies to which component and, before anything is selected, tell you what follows from it: which source code has to be released and which does not. We integrate your own application so that it remains unaffected.

Do you work at a fixed price?

Yes, when the scope is clear, as a contract with defined acceptance milestones. If the scope is still open, we start with a concept phase and then quote a fixed price for the implementation.

Do you work with AI?

Yes, systematically. Anything a tool contributes goes through the same checks as every other line of code: static analysis, review, test. We build our AI system ourselves, so we know what it does, and we keep improving it.

Tell us about your next project.

Tell us about your product and your schedule. We will tell you how we would approach the project and whether we see any major risks. The assessment, up to an indicative price, is free of charge.

Florian Seibold

Managing Director

info@querdenkerengineering.de

+49 7807 890 80 10