S3 Connected Health vs Bluefruit Software: full comparison for 2026
Quick verdict
S3 Connected Health (4.2/5) edges ahead of Bluefruit Software (4.1/5) overall. S3 Connected Health is the better choice for pharma companies adding connectivity to drug delivery. Bluefruit Software is the stronger option for UK device makers outsourcing firmware and testing. The right choice depends on your project size, budget, and required tech stack.
S3 Connected Health vs Bluefruit Software: head-to-head summary
| Criterion | S3 Connected Health | Bluefruit Software |
|---|---|---|
| Founded | 2001 | 2000 |
| HQ | Dublin, Ireland | Redruth, Cornwall, UK |
| Team size | 200–300 | 70–90 |
| Rating | 4.2 / 5 | 4.1 / 5 |
| Primary differentiator | Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs | Small, employee-owned embedded team with medical devices as its largest market and a strong testing culture |
| Pricing model | Fixed project, time and materials, managed service | Time and materials, fixed project |
| Min. engagement | Not disclosed | Not disclosed |
| Primary tech stack | BLE, Embedded C/C++, iOS | Embedded C/C++, RTOS, Test automation |
| Industries served | Drug delivery, Digital health, Wearables & remote monitoring | Diagnostics & lab devices, Surgical & therapeutic devices, Industrial |
S3 Connected Health vs Bluefruit Software: overview
S3 Connected Health
S3 Connected Health is the connected health business of Dublin's S3 Group (Silicon & Software Systems), which dates to 1986; the connected health unit itself is listed as founded around 2001. After the group sold its semiconductor unit to Adesto, it concentrated on this business. It works with pharma and medtech companies on connected drug delivery, SaMD, IoMT platforms, wireless connectivity and data security, and partnered with Ypsomed on connected injection devices. Employee figures range from about 200 to 300.
Bluefruit Software
Bluefruit Software has written embedded software from Redruth, Cornwall, since 2000 and is employee-owned. A Plymouth University partnership case study reports that medical devices grew from 10% to 60% of its work. It handles embedded software development, testing, some hardware development and edge AI integration, plus support for regulatory compliance and quality assurance. Its team is roughly 70 to 90 people.
Services and capabilities: S3 Connected Health vs Bluefruit Software
| Capability | S3 Connected Health | Bluefruit Software |
|---|---|---|
| Electronics & PCB design | ✗ | ✗ |
| Firmware & embedded software | ✓ | ✓ |
| SaMD & companion apps | ✓ | ✗ |
| Connected devices & IoT | ✓ | ✗ |
| Industrial design & human factors | ✗ | ✗ |
| Mechanical engineering | ✗ | ✗ |
| Device cybersecurity | ✓ | ✗ |
| Regulatory & QMS support | ✓ | ✓ |
| Manufacturing & scale-up | ✗ | ✗ |
Tech stack comparison: S3 Connected Health vs Bluefruit Software
| Framework / platform | S3 Connected Health | Bluefruit Software |
|---|---|---|
| Embedded C/C++ | ✓ | ✓ |
| Embedded Linux | N/A | N/A |
| RTOS | N/A | ✓ |
| BLE | ✓ | N/A |
| Cloud (AWS/Azure) | ✓ | N/A |
| IEC 62304 | ✓ | ✓ |
| ISO 14971 | N/A | N/A |
| ISO 13485 QMS | N/A | N/A |
| Qt | N/A | N/A |
Pricing comparison: S3 Connected Health vs Bluefruit Software
| Criterion | S3 Connected Health | Bluefruit Software |
|---|---|---|
| Minimum engagement | Not disclosed | Not disclosed |
| Engagement models | Dedicated team, Fixed project, Time & materials | Fixed project, Time & materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: S3 Connected Health vs Bluefruit Software
| Dimension | S3 Connected Health | Bluefruit Software |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Drug delivery, Digital health, Wearables & remote monitoring | Diagnostics & lab devices, Surgical & therapeutic devices, Industrial |
| Best use cases | Adding Bluetooth connectivity to an autoinjector, Building a patient adherence app and backend | Writing IEC 62304 firmware for a UK device startup, Independent verification of an existing device's embedded software |
| Typical project type | Dedicated team | Fixed project |
S3 Connected Health vs Bluefruit Software: pros and cons
| S3 Connected Health | |
|---|---|
| + | Long experience in wireless and embedded software from its S3 Group background |
| + | Works directly with pharma on connected injectors and inhalers, such as the Ypsomed partnership |
| + | Covers apps, cloud and the device connectivity module |
| + | Delivery team includes a site in Poland, which helps with cost |
| - | Founding date and history are tangled with the wider S3 Group, so check which entity you contract with |
| - | Not a mechanical or industrial design firm |
| - | Pharma focus means pure medtech hardware projects are less common |
| Bluefruit Software | |
|---|---|
| + | Medical devices make up most of its work, so regulated firmware practice is routine |
| + | Strong emphasis on testing and test automation |
| + | Lower rates than Cambridge or London consultancies |
| + | Employee ownership |
| - | Limited hardware design compared with full product development firms |
| - | Small team; large multi-year programs may need extra partners |
| - | No industrial design, mechanical engineering or manufacturing |
Who should choose S3 Connected Health?
A typical fit: adding Bluetooth connectivity to an autoinjector.
Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs. Minimum engagement is not publicly disclosed. Works best with clients in Drug delivery, Digital health, Wearables & remote monitoring.
Who should choose Bluefruit Software?
A typical fit: writing IEC 62304 firmware for a UK device startup.
Small, employee-owned embedded team with medical devices as its largest market and a strong testing culture. Minimum engagement is not publicly disclosed. Works best with clients in Diagnostics & lab devices, Surgical & therapeutic devices, Industrial.
Decision matrix: S3 Connected Health vs Bluefruit Software
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | S3 Connected Health |
| You need a large dedicated team for an ongoing programme | S3 Connected Health |
| Your budget is at the lower end | Compare: S3 Connected Health (Not disclosed) vs Bluefruit Software (Not disclosed) |
| You need specialist depth in a specific vertical | S3 Connected Health |
| 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: S3 Connected Health vs Bluefruit Software
| Use case | S3 Connected Health fit | Bluefruit Software fit | Winner |
|---|---|---|---|
| Adding Bluetooth connectivity to an autoinjector | Strong | Strong | Both equally |
| Building a patient adherence app and backend | Strong | Limited | S3 Connected Health |
| Writing IEC 62304 firmware for a UK device startup | Limited | Strong | Bluefruit Software |
| Independent verification of an existing device's embedded software | Limited | Strong | Bluefruit Software |
Verdict: S3 Connected Health vs Bluefruit Software
S3 Connected Health (4.2/5) is the stronger overall choice for most Medical Device Development projects. Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs.
Bluefruit Software (4.1/5) is worth a look if you need independent verification of an existing device's embedded software. If your situation matches that, Bluefruit Software is a competitive option.
Related comparisons
S3 Connected Health vs Bluefruit Software FAQ
Is S3 Connected Health better than Bluefruit Software?
S3 Connected Health (4.2/5) scores higher overall, but "better" depends on your use case. S3 Connected Health's strongest advantage: long experience in wireless and embedded software from its S3 Group background. Bluefruit Software's strongest advantage: medical devices make up most of its work, so regulated firmware practice is routine.
How do S3 Connected Health and Bluefruit Software differ in pricing?
S3 Connected Health uses fixed project, time and materials, managed service pricing. Bluefruit Software uses time and materials, fixed project pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: S3 Connected Health or Bluefruit Software?
S3 Connected Health 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 S3 Connected Health and Bluefruit Software?
S3 Connected Health's primary differentiator is: combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs. Bluefruit Software's primary differentiator is: Small, employee-owned embedded team with medical devices as its largest market and a strong testing culture. They also differ in team size (200–300 vs 70–90), minimum engagement (Not disclosed vs Not disclosed), and primary industries served (Drug delivery, Digital health vs Diagnostics & lab devices, Surgical & therapeutic devices).
Verify all details directly with each company before making a decision.