Lobaro GmbH vs EES: full comparison for 2026
Quick verdict
Lobaro GmbH (3.8/5) edges ahead of EES (3.8/5) overall. Lobaro GmbH is the better choice for teams needing deep LoRaWAN and low-power wide-area network specialists. EES is the stronger option for teams deliberately avoiding a large delivery organization in favor of senior-led staff. The right choice depends on your project size, budget, and required tech stack.
Lobaro GmbH vs EES: head-to-head summary
| Criterion | Lobaro GmbH | EES |
|---|---|---|
| Founded | 2012 | 2012 |
| HQ | Hamburg, Germany | Tempe / Chandler, AZ, USA |
| Team size | 15 | 3–50 |
| Rating | 3.8 / 5 | 3.8 / 5 |
| Primary differentiator | LoRa Alliance membership and Nordic Semiconductor design partner status with a 15-person team built around LPWAN protocol depth | Explicitly positions itself as senior-led, keeping the team small by design rather than as a growth-stage limitation |
| Pricing model | Project-based IoT firmware and platform engagements | Contract engineering engagements |
| Min. engagement | Not published | Not published |
| Primary tech stack | LoRa, LoRaWAN, Sigfox | C, C++, Industrial Embedded Systems |
| Industries served | Industrial IoT, Utility metering, Environmental monitoring | Industrial |
Lobaro GmbH vs EES: overview
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. That small, focused size means a hiring buyer working with Lobaro is working with a meaningful fraction of the entire firm's engineering capacity on any given engagement, not a rotating slice of a much larger organization. The team's protocol depth spans LoRa, LoRaWAN, Sigfox, LTE, and wireless M-Bus, a specific low-power wide-area networking specialty built over 13 years.
EES
Embedded Engineering Solutions (EES) was launched in 2012 and is based in Tempe, Arizona, with reported headcount varying across sources from roughly 3 to 50 employees, most consistently described as a small, senior-led firm. The company specializes in contract firmware, embedded systems, and hardware design engineering for the industrial sector, and its own positioning leans on being senior-led rather than layered with junior staff. For a hiring buyer specifically avoiding a large delivery organization, that's the stated value proposition, not an incidental trait.
Services and capabilities: Lobaro GmbH vs EES
| Capability | Lobaro GmbH | EES |
|---|---|---|
| Firmware development | ✓ | ✓ |
| RTOS development | ✗ | ✗ |
| Hardware co-design | ✓ | ✓ |
| Embedded GUI development | ✗ | ✗ |
| Medical device firmware | ✗ | ✗ |
| Functional safety | ✗ | ✗ |
| Technical training | ✗ | ✗ |
| Expert-witness services | ✗ | ✗ |
| Staff augmentation | ✗ | ✗ |
Tech stack comparison: Lobaro GmbH vs EES
| Framework / platform | Lobaro GmbH | EES |
|---|---|---|
| C | ✓ | ✓ |
| C++ | N/A | ✓ |
| FreeRTOS | N/A | N/A |
| Zephyr | N/A | N/A |
| FPGA | N/A | N/A |
| Embedded Linux | N/A | N/A |
| LVGL | N/A | N/A |
| AWS IoT | N/A | N/A |
| ARM Cortex-M | N/A | N/A |
Pricing comparison: Lobaro GmbH vs EES
| Criterion | Lobaro GmbH | EES |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Project-based IoT firmware and platform development | Contract firmware and hardware engineering |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Lobaro GmbH vs EES
| Dimension | Lobaro GmbH | EES |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Industrial IoT, Utility metering, Environmental monitoring | Industrial |
| Best use cases | Hiring a specialized LoRaWAN team for an industrial monitoring deployment, Wireless M-Bus firmware development for a utility metering product | Hiring a deliberately small, senior-led team for an industrial firmware program, Combined hardware and firmware engineering without separate specialist vendors |
| Typical project type | Project-based IoT firmware and platform development | Contract firmware and hardware engineering |
Lobaro GmbH vs EES: pros and cons
| Lobaro GmbH | |
|---|---|
| + | LoRa Alliance membership and Nordic Semiconductor design partner status verify its low-power wide-area networking credentials |
| + | A team of around 15 means a client's engagement represents a substantial share of the firm's total capacity, not a thin slice |
| + | 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 |
| EES | |
|---|---|
| + | Explicit senior-led positioning means the small team size is a deliberate choice, not just a growth-stage limitation |
| + | 13 years of operating history as a contract engineering firm for the industrial sector |
| + | Combines firmware, embedded systems, and hardware design in one team, covering multiple disciplines without separate specialist hires |
| + | Small size means a client's engagement represents a meaningful share of the firm's total capacity |
| - | Reported employee counts vary widely across sources, from roughly 3 to 50, worth confirming current headcount directly |
| - | Small team size caps capacity for a large or multi-workstream program |
| - | No published pricing or minimum engagement figure |
Who should choose Lobaro GmbH?
A typical fit: hiring a specialized LoRaWAN team for an industrial monitoring deployment.
LoRa Alliance membership and Nordic Semiconductor design partner status with a 15-person team built around LPWAN protocol depth. Minimum engagement is not publicly disclosed. Works best with clients in Industrial IoT, Utility metering, Environmental monitoring.
Who should choose EES?
A typical fit: hiring a deliberately small, senior-led team for an industrial firmware program.
Explicitly positions itself as senior-led, keeping the team small by design rather than as a growth-stage limitation. Minimum engagement is not publicly disclosed. Works best with clients in Industrial.
Decision matrix: Lobaro GmbH vs EES
| 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: Lobaro GmbH (Not published) vs EES (Not published) |
| You need specialist depth in a specific vertical | Lobaro GmbH |
| 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: Lobaro GmbH vs EES
| Use case | Lobaro GmbH fit | EES fit | Winner |
|---|---|---|---|
| Hiring a specialized LoRaWAN team for an industrial monitoring deployment | Strong | Strong | Both equally |
| Wireless M-Bus firmware development for a utility metering product | Strong | Limited | Lobaro GmbH |
| Hiring a deliberately small, senior-led team for an industrial firmware program | Strong | Strong | Both equally |
| Combined hardware and firmware engineering without separate specialist vendors | Limited | Strong | EES |
| Fixed-price build | Limited | Limited | Both equally |
| Staff augmentation | Limited | Limited | Both equally |
Verdict: Lobaro GmbH vs EES
Lobaro GmbH (3.8/5) is the stronger overall choice for most Embedded Firmware Development projects. LoRa Alliance membership and Nordic Semiconductor design partner status with a 15-person team built around LPWAN protocol depth.
EES (3.8/5) is worth a look if you need combined hardware and firmware engineering without separate specialist vendors. If your situation matches that, EES is a competitive option.
Related comparisons
Lobaro GmbH vs EES FAQ
Is Lobaro GmbH better than EES?
Lobaro GmbH (3.8/5) scores higher overall, but "better" depends on your use case. Lobaro GmbH's strongest advantage: LoRa Alliance membership and Nordic Semiconductor design partner status verify its low-power wide-area networking credentials. EES's strongest advantage: explicit senior-led positioning means the small team size is a deliberate choice, not just a growth-stage limitation.
How do Lobaro GmbH and EES differ in pricing?
Lobaro GmbH uses project-based iot firmware and platform engagements pricing. EES uses contract engineering engagements pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Lobaro GmbH or EES?
EES is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each developer before shortlisting.
What are the main differences between Lobaro GmbH and EES?
Lobaro GmbH's primary differentiator is: LoRa Alliance membership and Nordic Semiconductor design partner status with a 15-person team built around LPWAN protocol depth. EES's primary differentiator is: explicitly positions itself as senior-led, keeping the team small by design rather than as a growth-stage limitation. They also differ in team size (15 vs 3–50), minimum engagement (Not published vs Not published), and primary industries served (Industrial IoT, Utility metering vs Industrial).
Verify all details directly with each developer before making a decision.