IoT Consulting, Audits, Sprints, Retainers
Combotto helps engineering-led teams audit the gateway, MQTT, ingest, identity, and observability path under the most pressure right now. Start with a focused audit to get a decisive picture of risk, use the findings to drive a hardening sprint, and keep the path under review with repeatable delta checks.
Proof-led engagement path
Send the asset or message path, the pressure behind the request, and the timing window. You will get a reply with likely scope and the next practical step.
Based in Denmark • Remote-friendly • English & Danish
Specialist IoT Audit Consulting
Senior IoT Consultant
Find the path under pressure, turn it into evidence, and decide what to fix next.
I help engineering-led teams get a clear, evidence-backed view of the edge-to-cloud path creating risk right now — especially where gateways, MQTT infrastructure, identity, TLS posture, buffering, and observability need to hold up under launch deadlines, security reviews, incident follow-up, or fleet scale-up.
Best fit
Launch, security review, incident follow-up, fleet scale-up
Starting scope
1-3 assets or one path under pressure
What you get
Evidence, findings, prioritized backlog
Engagement path
Audit -> Hardening Sprint -> Retainer Review
What keeps the work sharp
Independent IoT audit consulting based in Denmark, working remotely with teams across edge-to-cloud systems.
Engagement path
Combotto starts with one edge-to-cloud path under pressure. The audit creates a shared baseline for leadership and engineering. From there, the team either hardens the path in a sprint, keeps it under review in a retainer, or runs the backlog internally.
Why teams bring me in
Fast audit clarity when launch pressure or customer scrutiny arrives before the architecture story is fully defensible.
System-level review across gateway, broker, ingest, identity, TLS, buffering, and telemetry paths.
Evidence-backed findings with owners, verification steps, and a clear next move for leadership and engineering.
Fast clarity
A focused review of the selected edge-to-cloud path so your team can see where security, reliability, and telemetry risk is concentrated first.
Best first step when the architecture story needs proof
Targeted hardening
A focused hardening pass on the issues most likely to hurt uptime, customer trust, or future scale.
Drift control
An evidence-backed review cadence for teams that want visibility after the audit and first hardening pass.
References / Client Case Studies
Start with the Rust gateway hardening case, then review the wider proof library for more examples of how Combotto turns system pressure into evidence, backlog, and a practical next move.
8 min read ·
Indoor Climate Field Proof
Engineering case study of integrating an SCD4x CO2 sensor with an STM32 B-L475E-IOT01A2 over I2C, publishing CO2, temperature, and humidity through MQTT with live room-state visibility and configurable CO2 alarms.
Shows the system under pressure, the evidence surfaced, and how Combotto turned that into a practical next move.
Review case study
8 min read ·
Audit -> Sprint -> Retainer Case Study
How a before-hardening audit exposed four gateway and ingest findings, a focused sprint fixed them, and the after-hardening check created a clear reference point for ongoing review.
Shows the system under pressure, the evidence surfaced, and how Combotto turned that into a practical next move.
Review case study
Security & Reliability Audit
A comprehensive reliability and security audit of Combotto's secure edge IoT Gateway, identifying strengths, architectural bottlenecks, and a 90-day roadmap toward production-grade resilience.
Shows the system under pressure, the evidence surfaced, and how Combotto turned that into a practical next move.
Review case studyFlagship gateway path
This proof comes from Combotto's own reference Rust IoT gateway: the full Audit -> Sprint -> Retainer case is documented in the flagship gateway case study, with supporting context in the Raspberry Pi 5 migration note, the 24/7 gateway operations write-up, and the audit engine article that makes repeat runs and delta reviews possible.
On that same Raspberry Pi gateway path, the audit turned a vague gateway concern into a concrete finding set, the sprint fixed the highest-impact issues and proved the fixes held, and the retainer turned the hardened state into a reusable reference point.
Turn one pressured path into a concrete finding set the team can act on.
Fix the highest-impact issues on the same path and prove the rerun held.
Keep later releases anchored to the hardened state with a reusable comparison point.
Leadership could immediately see that the path was exposed. Engineering could see which controls were failing, why they mattered, and what to fix first.
Why it matters
The posture was visibly exposed, the failing controls were easy to identify, and the next remediation steps were already tied to evidence.
After the hardening work, the same path was checked again. The posture moved from exposed to healthy, the findings cleared, and the proof stayed tied to the same system slice.
Why it matters
The improvement stayed visible on the exact audit surface that triggered the work instead of drifting into a softer, wider scope.
The comparison report shows what improved, confirms there were no regressions, and gives the team a durable reference point for release reviews or monthly check-ins.
Why it matters
Future releases can be checked against a known-good state instead of relying on memory, reassurance, or guesswork.
Field Notes / Expertise Proof
Articles on gateway, MQTT, identity, and telemetry risk patterns that often become the starting point for an audit conversation.
If one of these pressure patterns already matches your system, prefer direct guidance on your current setup: Start the audit conversation.
6 min read ·
I’m moving my reference IoT gateway from a Dell Linux dev machine to a Raspberry Pi 5 to validate boot, recovery, buffering, and observability on real edge hardware.
8 min read ·
Captured field proof of a Rust IoT gateway on Raspberry Pi 5 handling three STM32 devices over MQTT/TLS, WAL backlog during broker outage, and clean recovery after broker return. Useful for teams evaluating IoT gateway reliability before rollout.
8 min read ·
The Combotto Audit Engine is now ready for pilot projects: canonical reports, run-to-run delta tracking, and alerts for regressions and expiring certificates—built to make Audit → Sprint → Retainer delivery faster and more verifiable.
20 min read ·
What breaks when an edge IoT gateway runs 24/7? Real operational lessons from running a secure edge-to-cloud system under intermittent connectivity, focusing on reliability, observability, and silent failure modes.
10 min read ·
Edge-to-cloud systems without proper observability suffer from slow debugging and reactive incident response. Learn why logs alone fall short and how observability reduces risk.
15 min read ·
I created a structured IoT Architecture Audit Checklist. It captures the core principles of reliability, security, and observability, and provides a consistent process for evaluating device -> gateway -> cloud pipelines.
Send the asset or message path, the pressure behind the request, and the timing window. You’ll get a same-day reply with likely audit scope and the next practical step.
Or contact me directly: +45 22 39 34 91 or tb@combotto.io.