Five ways to ship into Epic. What each actually owns.
"Compare" pages usually argue on price. We're going to argue on responsibility — what stays your problem under each option, and what doesn't.
SoFaaS™ VectorCare | Redox Integration platform | 1upHealth FHIR data platform | Build it yourself Internal engineering | Epic Showroom alone Listing only | |
|---|---|---|---|---|---|
| What it actually is | A compliant runtime your app launches inside Epic on top of | An integration platform that translates data between systems | A FHIR API gateway and longitudinal patient data layer | Engineering scope for your team to design, build, and operate | Epic's vendor marketplace listing program |
| HIPAA hosting + BAA on day one | Inherited from the SoFaaS™ platform | Hosting yes; per-deal BAA varies | Hosting yes; per-deal BAA varies | You build and certify it yourself | Not Showroom's role |
| SOC 2 Type II evidence packet | One report, accepted across the platform | Vendor-level report | Vendor-level report | Your audit, your timeline | Not part of the listing |
| Multi-hospital distribution | Same runtime, every hospital — config, not custom code | Per-hospital integration work each time | Per-hospital integration work each time | Re-validation per hospital | Listing visible to every Epic hospital |
| Time to first hospital | Weeks | Months | Months | 12–18 months | Months (submission cycle), then you still need a runtime |
| Time to tenth hospital | Days of configuration | Months per hospital | Months per hospital | Quarter per hospital | Same listing; runtime work still per-hospital |
| Maintenance when Epic ships breaking changes | Platform-managed; your app keeps running | Platform-managed for the integration layer only | Platform-managed for the integration layer only | Your team, every quarter | Vendor's responsibility |
| Epic Showroom listing handled | Submission run on your behalf | You handle it | You handle it | You handle it | It is the listing |
| What you still own | Your code, your IP, your clinical UX, your customer relationship | Your code + your hosting + your compliance posture | Your code + your hosting + your compliance posture | Everything | Your code + hosting + compliance + maintenance |
Where we don't compete
Redox and 1upHealth solve a different problem. If you need to translate clinical data between many non-Epic systems, normalize FHIR across payers, or aggregate longitudinal patient records, those platforms are the right tool. Many SoFaaS™ customers use one of them alongside SoFaaS™ for non-Epic data flows. We're not asking you to pick.
Epic Showroom is non-negotiable. Every Epic-deployed third-party app needs the listing. The question is who runs the submission and who runs the runtime your listing points at. SoFaaS™ does both as part of the same engagement.
Building it yourself is a real option. If you have the engineering bench, the compliance team, and the patience for 12–18 months before the first hospital is live — you can build it. Most healthcare vendors who try end up shipping a runtime that looks a lot like SoFaaS™, four quarters later, after the first deal already churned.
A note on pricing
SoFaaS™ pricing is scoped to your deployment — implementation plus a recurring fee tied to the size of the deal we unblock. We don't publish a number because the right number depends on the deal you're trying to close. When we run the math against that deal, it tends to get obvious fast.
FAQ
Is SoFaaS™ a replacement for Redox or 1upHealth?
No. Redox and 1upHealth are integration platforms — they translate clinical data between systems. SoFaaS™ is a deployment runtime — your app launches inside Epic on top of it. Many SoFaaS™ customers use an integration platform alongside SoFaaS™ for non-Epic data flows.
Can I just build it myself?
If you have the engineering bench, the compliance team, and the patience for 12–18 months before the first hospital is live, yes. Most healthcare vendors who try end up shipping a runtime that looks a lot like SoFaaS™, four quarters later, after the first deal already churned.
Do I still need an Epic Showroom listing?
Yes. Every Epic-deployed third-party app needs the listing. The question is who runs the submission and who runs the runtime your listing points at. SoFaaS™ does both as part of the same engagement.
Why doesn't this page show prices?
SoFaaS™ pricing is scoped to your deployment — implementation plus a recurring fee tied to the size of the deal we unblock. We don't publish a number because the right number depends on the deal you're trying to close. When we run the math against that deal, it tends to get obvious fast.
Have a deal stuck on Epic?
Tell us which option you're already on, what's actually blocked, and we'll tell you within 15 minutes whether SoFaaS™ would change the answer.