InTechHouse vs Lobaro GmbH: full comparison for 2026
Quick verdict
InTechHouse (4.2/5) edges ahead of Lobaro GmbH (4.0/5) overall. InTechHouse is the better choice for enterprise programs needing a publicly disclosed, EU-certified R&D partner. Lobaro GmbH is the stronger option for LoRaWAN and low-power wide-area network firmware for industrial IoT. The right choice depends on your project size, budget, and required tech stack.
InTechHouse vs Lobaro GmbH: head-to-head summary
| Criterion | InTechHouse | Lobaro GmbH |
|---|---|---|
| Founded | 2003 | 2012 |
| HQ | Bydgoszcz, Poland | Hamburg, Germany |
| Team size | 51–200 | 15 |
| Rating | 4.2 / 5 | 4.0 / 5 |
| Primary differentiator | Publicly listed on Warsaw's NewConnect market since 2015, giving financial transparency most private firmware vendors don't offer | LoRa Alliance membership and Nordic Semiconductor design partner status with deep LPWAN protocol experience |
| Pricing model | Project-based hardware and embedded engineering | Project-based IoT firmware and platform engagements |
| Min. engagement | Not published | Not published |
| Primary tech stack | C, C++, Embedded Systems Programming | LoRa, LoRaWAN, Sigfox |
| Industries served | Industrial, Consumer electronics, Data & analytics products | Industrial IoT, Utility metering, Environmental monitoring |
InTechHouse vs Lobaro GmbH: overview
InTechHouse
InTechHouse operates as SoftBlue S.A., a company founded in 2003 and headquartered in Bydgoszcz, Poland, listed on the Warsaw Stock Exchange's NewConnect market since 2015. Its 51 to 200-person team works across hardware design, embedded systems, and data analytics, positioning itself as an EU-certified R&D partner delivering products from concept through production rather than firmware alone. Public-company status brings a level of financial disclosure and governance that privately held competitors don't carry, which can matter to enterprise procurement teams running vendor due diligence.
Lobaro GmbH
Lobaro GmbH was founded in Hamburg in 2012 by Tobias Rohde and has grown to around 15 people, a design partner of Nordic Semiconductor and a member of the LoRa Alliance. The company's stated work covers IoT sensors, gateways, and the firmware, backend, and platform software that runs them, with specific protocol experience in LoRa, LoRaWAN, Sigfox, LTE, and wireless M-Bus for industrial metering and monitoring applications. That protocol depth in low-power wide-area networking is a narrower but deeper specialty than the general IoT connectivity claims many larger firms make.
Services and capabilities: InTechHouse vs Lobaro GmbH
| Capability | InTechHouse | Lobaro GmbH |
|---|---|---|
| RTOS firmware development | ✓ | ✓ |
| Bare-metal & driver development | ✓ | ✗ |
| Secure boot / OTA firmware updates | ✗ | ✗ |
| MCU & platform migration | ✗ | ✗ |
| Connectivity & IoT protocols | ✗ | ✓ |
| Functional safety / compliance | ✗ | ✗ |
| Embedded AI / on-device inference | ✓ | ✗ |
| Firmware GUI development | ✗ | ✗ |
| Hardware co-design / board bring-up | ✓ | ✓ |
| Staff augmentation | ✗ | ✗ |
Tech stack comparison: InTechHouse vs Lobaro GmbH
| Framework / platform | InTechHouse | Lobaro GmbH |
|---|---|---|
| FreeRTOS | N/A | N/A |
| Zephyr | N/A | N/A |
| STM32 | N/A | N/A |
| ARM Cortex-M | N/A | N/A |
| Embedded Linux | N/A | N/A |
| BLE | N/A | N/A |
| MISRA | N/A | N/A |
| Secure Boot | N/A | N/A |
| AWS IoT | N/A | N/A |
| RISC-V | N/A | N/A |
Pricing comparison: InTechHouse vs Lobaro GmbH
| Criterion | InTechHouse | Lobaro GmbH |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Project-based engineering, Concept-to-production programs | Project-based IoT firmware and platform development |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: InTechHouse vs Lobaro GmbH
| Dimension | InTechHouse | Lobaro GmbH |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Industrial, Consumer electronics, Data & analytics products | Industrial IoT, Utility metering, Environmental monitoring |
| Best use cases | Concept-to-production hardware and firmware program for a new device, Embedded systems development requiring integrated data analytics | LoRaWAN sensor and gateway firmware for an industrial monitoring deployment, Wireless M-Bus firmware for a utility metering product |
| Typical project type | Project-based engineering | Project-based IoT firmware and platform development |
InTechHouse vs Lobaro GmbH: pros and cons
| InTechHouse | |
|---|---|
| + | Public listing on the Warsaw Stock Exchange's NewConnect market since 2015 gives financial disclosure competitors don't provide |
| + | 22 years of operating history under the SoftBlue S.A. legal entity |
| + | Combined hardware design, embedded systems, and data analytics capability covers connected-product programs beyond firmware alone |
| + | EU-certified R&D partner status can simplify grant-funded or EU-based procurement processes |
| - | 51 to 200 employees is spread across hardware, embedded, and data analytics work, not a dedicated firmware-only team |
| - | Public listing means quarterly disclosure obligations, which is a governance factor rather than a delivery one but can affect how the company discusses client work publicly |
| - | No published pricing or minimum engagement figure |
| Lobaro GmbH | |
|---|---|
| + | LoRa Alliance membership and Nordic Semiconductor design partner status verify its low-power wide-area networking credentials |
| + | Protocol depth spans LoRa, LoRaWAN, Sigfox, LTE, and wireless M-Bus, a specific set most generalist firmware vendors don't cover together |
| + | 13 years of operating history with a consistent focus on industrial IoT sensor and gateway firmware |
| + | Received public innovation funding through IFB Hamburg's InnoRampUp programme, an independently verifiable signal of institutional confidence |
| - | A team of around 15 people is small relative to industrial IoT programs requiring firmware across many product lines at once |
| - | LPWAN protocol focus is a narrower fit for firmware projects centered on Wi-Fi, Bluetooth, or cellular broadband instead |
| - | No published pricing or minimum engagement figure |
Who should choose InTechHouse?
A typical fit: concept-to-production hardware and firmware program for a new device.
Publicly listed on Warsaw's NewConnect market since 2015, giving financial transparency most private firmware vendors don't offer. Minimum engagement is not publicly disclosed. Works best with clients in Industrial, Consumer electronics, Data & analytics products.
Who should choose Lobaro GmbH?
A typical fit: LoRaWAN sensor and gateway firmware for an industrial monitoring deployment.
LoRa Alliance membership and Nordic Semiconductor design partner status with deep LPWAN protocol experience. Minimum engagement is not publicly disclosed. Works best with clients in Industrial IoT, Utility metering, Environmental monitoring.
Decision matrix: InTechHouse vs Lobaro GmbH
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Both offer fixed-price models |
| You need a large dedicated team for an ongoing programme | Check each company's engagement model |
| Your budget is at the lower end | Compare: InTechHouse (Not published) vs Lobaro GmbH (Not published) |
| You need specialist depth in a specific vertical | InTechHouse |
| You need staff augmentation or team extension | Neither; consider alternatives that offer staff aug |
| You need consulting before committing to a build | Both may offer discovery engagements |
Use case fit: InTechHouse vs Lobaro GmbH
| Use case | InTechHouse fit | Lobaro GmbH fit | Winner |
|---|---|---|---|
| Concept-to-production hardware and firmware program for a new device | Strong | Limited | InTechHouse |
| Embedded systems development requiring integrated data analytics | Strong | Limited | InTechHouse |
| LoRaWAN sensor and gateway firmware for an industrial monitoring deployment | Limited | Strong | Lobaro GmbH |
| Wireless M-Bus firmware for a utility metering product | Limited | Strong | Lobaro GmbH |
| Fixed-price build | Limited | Limited | Both equally |
| Staff augmentation | Limited | Limited | Both equally |
Verdict: InTechHouse vs Lobaro GmbH
InTechHouse (4.2/5) is the stronger overall choice for most Firmware Development projects. Publicly listed on Warsaw's NewConnect market since 2015, giving financial transparency most private firmware vendors don't offer.
Lobaro GmbH (4.0/5) is worth a look if you need wireless M-Bus firmware for a utility metering product. If your situation matches that, Lobaro GmbH is a competitive option.
Related comparisons
InTechHouse vs Lobaro GmbH FAQ
Is InTechHouse better than Lobaro GmbH?
InTechHouse (4.2/5) scores higher overall, but "better" depends on your use case. InTechHouse's strongest advantage: public listing on the Warsaw Stock Exchange's NewConnect market since 2015 gives financial disclosure competitors don't provide. Lobaro GmbH's strongest advantage: LoRa Alliance membership and Nordic Semiconductor design partner status verify its low-power wide-area networking credentials.
How do InTechHouse and Lobaro GmbH differ in pricing?
InTechHouse uses project-based hardware and embedded engineering pricing. Lobaro GmbH uses project-based iot firmware and platform engagements pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: InTechHouse or Lobaro GmbH?
InTechHouse is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each company before shortlisting.
What are the main differences between InTechHouse and Lobaro GmbH?
InTechHouse's primary differentiator is: publicly listed on Warsaw's NewConnect market since 2015, giving financial transparency most private firmware vendors don't offer. Lobaro GmbH's primary differentiator is: LoRa Alliance membership and Nordic Semiconductor design partner status with deep LPWAN protocol experience. They also differ in team size (51–200 vs 15), minimum engagement (Not published vs Not published), and primary industries served (Industrial, Consumer electronics vs Industrial IoT, Utility metering).
Verify all details directly with each company before making a decision.