TrustRadius

1upHealth vs. Azure API Management

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
1upHealth
Score 7.0 out of 10
N/A
As a specialist of FHIR® interoperability, 1upHealth focuses on bridging the gap between patient centered data and provider needs, thus creating a platform for patients to aggregate and share medical data from external health systems and wearable devices with providers, to enable improved healthcare outcomes and lower costs. 1upHealth provides data interoperability between healthcare systems, boasting a low cost at fractions of a cent per API call, utilizing the latest FHIR® standards,…N/A
Azure API Management
Score 8.0 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
Lightweight and serverless version of API Management service, billed per execution
Pricing
1upHealthAzure API Management
Editions & Modules
No answers on this topic
Consumption
0.042 per 10,000 calls
Lightweight and serverless version of API Management service, billed per execution
Developer
$48.04
per month Non-production use cases and evaluations
Basic
$147.17
per month Entry-level production use cases
Standard
$686.72
per month Medium-volume production use cases
Premium
$2,795.17
per month High-volume or enterprise production use cases
Isolated
TBA
per month Enterprise production use cases requiring high degree of isolation
Offerings
Pricing Offerings
1upHealthAzure API Management
Free Trial
YesNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeRequiredNo setup fee
Additional Details——
More Pricing Information
Community Pulse
1upHealthAzure API Management
Considered Both Products
1upHealth

No answer on this topic

Azure API Management
Verified User
Anonymous
Chose Azure API Management
Apigee is by Google and seems to be promising. The cost seems high though. With Azure, we do not have to make any special purchases. CapEx vs OpEx! But, Apigee could be more environment independent compared to Azure APIM. The promise of speed by Apigee is also better compared …
Verified User
Anonymous
Chose Azure API Management
It’s a great tool, and so easy to seamlessly connect into your current Azure world that it’s hard not to look at it or even test the waters with it. It’s priced well, and is feature-rich enough to accomplish most tasks. I think the ease of having everything together and the …
Gordon Lo | TrustRadius Reviewer
Gordon Lo
Digital Solutions Architect
Chose Azure API Management
Azure APIM vs Amazon API Gateway:
1) Azure APIM was a complete package that included a developer portal.
2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.
Features
1upHealthAzure API Management
API Management
Comparison of API Management features of Product A and Product B
1upHealth
-
Ratings
Azure API Management
8.0
Ratings
4% below category average
API access control00 Ratings8.90 Ratings
Rate limits and usage policies00 Ratings5.40 Ratings
API usage data00 Ratings8.90 Ratings
API user onboarding00 Ratings9.00 Ratings
API versioning00 Ratings8.90 Ratings
Usage billing and payments00 Ratings5.20 Ratings
API monitoring and logging00 Ratings9.80 Ratings
Best Alternatives
1upHealthAzure API Management
Small Businesses
NGINX
NGINX
Score 9.2 out of 10
NGINX
NGINX
Score 9.2 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.2 out of 10
NGINX
NGINX
Score 9.2 out of 10
Enterprises
NGINX
NGINX
Score 9.2 out of 10
NGINX
NGINX
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
1upHealthAzure API Management
Likelihood to Recommend
-
(0 ratings)
8.0
(0 ratings)
User Testimonials
1upHealthAzure API Management
Likelihood to Recommend
No answers on this topic
The range of policies that enable the APIs to loosely couple it with security, rate limit, retry, etc. are good. We can easily tie authentication mechanisms to external and other internal services without having to modify the backend.
Verified User
Anonymous
Read full review
Pros
No answers on this topic
  • Management of APIs
  • Security of the API through Azure AD, AD B2C etc.
  • Providing an outer layer through APIs
Verified User
Anonymous
Read full review
Cons
No answers on this topic
  • Cost - the upfront cost is a bit restrictive. I've been told it is because there are a few underlying VMs that are running this service. So if you're just starting out with API management, it can be an expensive proposition. Value increases as you add additional APIs. If you're using Azure B2C for the developer portal, you'll require Standard or Premium since they support AAD integration.
  • Security granularity - at time of writing, APIM doesn't support breaking out operations to products. For example, if you have an API that has a GET and a POST operation, and you want the POST operation to require a different subscription. There is a work around, but it makes management a bit messy.
  • Developer and Publisher portal - it's a little weird. Microsoft hasn't migrated all the publisher portal functionality into the "native" Azure portal. So some of it feels a little weird - especially when working with the content management side of things for the developer portal.
  • Scaling - while it's easy to scale up, the cost of APIM ramps up very quickly. Standard -> Premium is a 4x jump.
Gordon Lo | TrustRadius Reviewer
Gordon Lo
Digital Solutions Architect
Read full review
Alternatives Considered
No answers on this topic
Azure APIM vs Amazon API Gateway:
1) Azure APIM was a complete package that included a developer portal.
2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.
3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.
Gordon Lo | TrustRadius Reviewer
Gordon Lo
Digital Solutions Architect
Read full review
Return on Investment
No answers on this topic
  • It’s really pay as you go, so it's not that costly to get in and try it out. There’s no expensive client to buy and manage, but you do need to stay on top of the rapidly changing Azure environment to be sure you upgrade or adjust when needed.
  • It’s not great having more than one API tool, but it’s ok to spread out your work, as you always want the right tool for the right job. For example, if you are a Salesforce-heavy organization, I’d go with Mule over Azure.
  • It was easy getting an external consultant access to the tool to build their own API for a project they were working on for us.
Verified User
Anonymous
Read full review
ScreenShots