StarFish Medical vs S3 Connected Health: full comparison for 2026
Quick verdict
StarFish Medical (4.6/5) edges ahead of S3 Connected Health (4.2/5) overall. StarFish Medical is the better choice for startups needing design plus pilot manufacturing. S3 Connected Health is the stronger option for pharma companies adding connectivity to drug delivery. The right choice depends on your project size, budget, and required tech stack.
StarFish Medical vs S3 Connected Health: head-to-head summary
| Criterion | StarFish Medical | S3 Connected Health |
|---|---|---|
| Founded | 1999 | 2001 |
| HQ | Victoria, BC, Canada | Dublin, Ireland |
| Team size | 201–250 | 200–300 |
| Rating | 4.6 / 5 | 4.2 / 5 |
| Primary differentiator | Medtech-only practice that can build clinical and early commercial units in its own certified clean room | Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs |
| Pricing model | Phased fixed project, time and materials | Fixed project, time and materials, managed service |
| Min. engagement | Not disclosed | Not disclosed |
| Primary tech stack | ISO 13485 QMS, IEC 62304, ISO 14971 | BLE, Embedded C/C++, iOS |
| Industries served | Diagnostics & lab devices, Surgical & therapeutic devices, Wearables & remote monitoring, Drug delivery | Drug delivery, Digital health, Wearables & remote monitoring |
StarFish Medical vs S3 Connected Health: overview
StarFish Medical
StarFish Medical was founded in Victoria, British Columbia, by Scott Phillips (the company gives 1999; some directories list 1998). It works only on medical devices, covering design, development and low-volume manufacturing in ISO 13485 certified facilities, and reports around 230 staff across Victoria, Toronto and Irvine (per company website; independently unverifiable). In November 2024 it acquired Omnica Corporation, a California medical device design firm, which added a larger US West Coast presence. Victoria remains the headquarters and its largest site.
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.
Services and capabilities: StarFish Medical vs S3 Connected Health
| Capability | StarFish Medical | S3 Connected Health |
|---|---|---|
| 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: StarFish Medical vs S3 Connected Health
| Framework / platform | StarFish Medical | S3 Connected Health |
|---|---|---|
| Embedded C/C++ | ✓ | ✓ |
| Embedded Linux | N/A | N/A |
| RTOS | N/A | N/A |
| BLE | N/A | ✓ |
| Cloud (AWS/Azure) | N/A | ✓ |
| IEC 62304 | ✓ | ✓ |
| ISO 14971 | ✓ | N/A |
| ISO 13485 QMS | ✓ | N/A |
| Qt | N/A | N/A |
Pricing comparison: StarFish Medical vs S3 Connected Health
| Criterion | StarFish Medical | S3 Connected Health |
|---|---|---|
| Minimum engagement | Not disclosed | Not disclosed |
| Engagement models | Fixed project, Manufacturing contract, Time & materials | Dedicated team, Fixed project, Time & materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: StarFish Medical vs S3 Connected Health
| Dimension | StarFish Medical | S3 Connected Health |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Diagnostics & lab devices, Surgical & therapeutic devices, Wearables & remote monitoring | Drug delivery, Digital health, Wearables & remote monitoring |
| Best use cases | Taking a venture-backed device from proof of concept to clinical-trial units, Designing an optical diagnostic instrument with its consumable | Adding Bluetooth connectivity to an autoinjector, Building a patient adherence app and backend |
| Typical project type | Fixed project | Dedicated team |
StarFish Medical vs S3 Connected Health: pros and cons
| StarFish Medical | |
|---|---|
| + | Every project is a medical device, so design reviews, risk files and documentation follow medtech practice by default |
| + | Prototype and pilot production happen in its own ISO 13485 facility, avoiding an early transfer to a contract manufacturer |
| + | The Omnica acquisition adds Southern California capacity for US clients |
| + | Multidisciplinary teams cover industrial design, mechanics, electronics, software and human factors |
| - | Volume manufacturing beyond pilot quantities still needs a larger contract manufacturer |
| - | North American cost base makes it more expensive than Eastern European or Asian engineering teams |
| - | The Omnica integration is recent, so cross-site processes are still settling |
| 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 |
Who should choose StarFish Medical?
A typical fit: taking a venture-backed device from proof of concept to clinical-trial units.
Medtech-only practice that can build clinical and early commercial units in its own certified clean room. Minimum engagement is not publicly disclosed. Works best with clients in Diagnostics & lab devices, Surgical & therapeutic devices, Wearables & remote monitoring, Drug delivery.
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.
Decision matrix: StarFish Medical vs S3 Connected Health
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | StarFish Medical |
| You need a large dedicated team for an ongoing programme | S3 Connected Health |
| Your budget is at the lower end | Compare: StarFish Medical (Not disclosed) vs S3 Connected Health (Not disclosed) |
| You need specialist depth in a specific vertical | StarFish Medical |
| 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: StarFish Medical vs S3 Connected Health
| Use case | StarFish Medical fit | S3 Connected Health fit | Winner |
|---|---|---|---|
| Taking a venture-backed device from proof of concept to clinical-trial units | Strong | Limited | StarFish Medical |
| Designing an optical diagnostic instrument with its consumable | Strong | Limited | StarFish Medical |
| Adding Bluetooth connectivity to an autoinjector | Limited | Strong | S3 Connected Health |
| Building a patient adherence app and backend | Limited | Strong | S3 Connected Health |
Verdict: StarFish Medical vs S3 Connected Health
StarFish Medical (4.6/5) is the stronger overall choice for most Medical Device Development projects. Medtech-only practice that can build clinical and early commercial units in its own certified clean room.
S3 Connected Health (4.2/5) is worth a look if you need building a patient adherence app and backend. If your situation matches that, S3 Connected Health is a competitive option.
Related comparisons
StarFish Medical vs S3 Connected Health FAQ
Is StarFish Medical better than S3 Connected Health?
StarFish Medical (4.6/5) scores higher overall, but "better" depends on your use case. StarFish Medical's strongest advantage: every project is a medical device, so design reviews, risk files and documentation follow medtech practice by default. S3 Connected Health's strongest advantage: long experience in wireless and embedded software from its S3 Group background.
How do StarFish Medical and S3 Connected Health differ in pricing?
StarFish Medical uses phased fixed project, time and materials pricing. S3 Connected Health uses fixed project, time and materials, managed service pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: StarFish Medical or S3 Connected Health?
StarFish Medical 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 StarFish Medical and S3 Connected Health?
StarFish Medical's primary differentiator is: medtech-only practice that can build clinical and early commercial units in its own certified clean room. S3 Connected Health's primary differentiator is: combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs. They also differ in team size (201–250 vs 200–300), minimum engagement (Not disclosed vs Not disclosed), and primary industries served (Diagnostics & lab devices, Surgical & therapeutic devices vs Drug delivery, Digital health).
Verify all details directly with each company before making a decision.