You've got questions, we've got answers

And we're looking forward to telling you more

The KeborMed Platform is ready to be used out of the box, so we can have your connected solution up and running in as little as one week, with minimum customizations. Most projects that include custom extensions in addition to the KeborMed Core take between 1 and 6 months, depending on the level of customizations required.
While implementations can be slightly different, the cost of connecting a medical solution using the KeborMed PaaS will always end up being much lower than developing a custom connectivity solution, hosting & supporting it internally. And the platform costs are always directly proportional to your revenue.
KeborMed's microservices architecture can be deployed in any public, on-premise or hybrid cloud environment. While Microsoft Azure is the default cloud hosting and infrastructure services provider recommended by KeborMed, the KBM PaaS is provider-agnostic, with no hard dependencies on any proprietary cloud services.
Cloud connected solutions require regular software updates for both cybersecurity and compliance reasons. Any updates to the core platform will always be KeborMed's responsibility, regardless of your plan. Additionally, depending on the selected plan, KeborMed could take over the responsibility of managing and deploying all related software updates.
You and your users own the data. KeborMed has no ownership claim whatsoever to the data.

Developing a new connected device or retrofitting a disconnected device into a cloud-based, globally compliant, connected solution is a complicated, expensive & lengthy process if you choose to go the custom development route. Many times, the result is an incomplete, marginally compliant or overall inefficient solution.

Employing a managed services approach may help cut some of the initial costs and add speed, but the ongoing cost and operational complexity to securely support and maintain a cloud-connected medical solution will eventually bring costs to values similar or even higher than custom development.

Going the platform route ensures the simplest, fastest, and most cost-effective manner of adding connectivity to a medical solution, both in terms of initial deployment and in terms of supporting and maintaining the deployed solution.

Here is a quick view of what each platform plan is an ideal fit for, along with every plan's advantages:


An ideal fit for customers who are building a connected solution from scratch, without any legacy technology and/or personnel constraints.
  • Guarantees the fastest time-to-market and the highest level of development and support cost savings.


Suited for device manufacturers dealing with one or more of the following issues:
  • an obsolete device connectivity system that is not able to support current business, regulatory and/or technical needs
  • an incomplete internal IT team and limited options to expand it, due to location and/or financial constraints (e.g. can’t compete with Big Tech for hard-to-find technical resources)
  • competitive and/or regulatory pressure to transition to a connected model as soon as possible

Maximizes the effectiveness of the device company’s internal IT team, while transferring the responsibility for all critical system components to the KeborMed PaaS.


Dev Environments are an ideal starting point for companies looking to develop and validate fully functional prototypes or MVPs of a medical device before moving forward with further development.
Have a fully functional connected solution from the early prototyping phases and grow organically on the platform, as your solution matures, and you are ready to migrate to more complex tiers.