The vendor landscape, by category
"PACS vendor" covers a wider range of businesses than the name suggests. Before comparing quotes, it helps to know which category each one belongs to, because the category predicts the pricing model, the support model and the exit path more reliably than any feature list does.
- Large enterprise vendors: built for hospital networks and multi-site radiology groups. Deep feature sets, long sales cycles, implementations measured in months, and pricing that assumes a dedicated IT department on the buyer's side.
- Cloud PACS subscriptions: the images live on the vendor's servers and the clinic pays monthly rent, commonly somewhere in the $150 to $2,000 a month range depending on volume and tier. No hardware to own, but the archive lives on someone else's infrastructure for as long as the clinic pays.
- Open-source engines: projects like Orthanc give a clinic or a contractor a real DICOM server to build on, free to run, but the clinic (or whoever it hires) is responsible for assembling a usable system around it: worklist, viewer, backups, security hardening. See Orthanc alternative for what that build-versus-buy tradeoff looks like in practice.
- Packaged self-hosted products: the archive runs on hardware the clinic owns, but it ships as a finished product with a license, installation, updates and support, not as a do-it-yourself project. This is the category a clinic lands in when it wants ownership without taking on system integration work itself.
For the mechanics of what a PACS actually does day to day, see what is PACS; for the on-premise versus cloud decision specifically, see cloud vs onsite.
What the pricing model does to five-year cost
The category a vendor falls into determines whether the clinic is renting or buying, and rent versus buy compounds differently over time. A concrete example: at a typical $700 a month cloud PACS bill, five years of rent totals $42,000. A combined self-hosted license, priced flat rather than per study, can total $38,400 over the same five years. The crossover sits around $642 a month. Above that monthly rent, renting costs more over five years. Below it, switching to a self-hosted system buys the archive itself rather than producing a straightforward savings line, since the clinic is now also responsible for the hardware and the relationship that keeps it running.
The number that matters is not the sticker price on either option, it is whether the pricing model is flat or scales with volume. A flat monthly or yearly license is predictable five years out. A per-study or per-exam fee is not: it grows with the clinic's own success, which turns a good year for the business into a worse year for the PACS bill.
Ten questions to ask every vendor
- Who owns the data, and what's the export path? Get the answer in writing, not as a sales assurance.
- What happens if the clinic stops paying? Full lockout, degraded read-only access, or something else.
- Where do the images physically live? On the clinic's own hardware, in the vendor's cloud, or in a third-party cloud account the vendor manages.
- How fast does a study open at the worklist? Ask for a number, not an adjective.
- What is the security posture? Specifically, does the server have open inbound ports to the internet, or does it only dial out.
- Will the vendor sign a BAA, and what does the HIPAA paperwork look like? Ask which safeguards are built in versus which ones the clinic still has to arrange itself.
- Who owns the backups, and are restores ever tested? A backup nobody has restored from is a guess, not a plan.
- Is support a named person or a ticket queue? Ask what the response time actually is, in hours, not in marketing language.
- Is pricing per-study or flat? This is a major driver of five-year cost variance between otherwise similar-looking quotes.
- What are the contract's exit terms? Notice period, data export timeline, and whether the studies are handed over in a standard DICOM format or something proprietary.
Red flags
A few patterns are worth walking away from on their own, before any deeper evaluation:
- Per-study pricing that scales with growth. Per-study fees make the PACS bill rise with study volume; model the projected volume for the next few years before signing.
- Export queues that run on the vendor's timeline. If getting the clinic's own archive out requires a support ticket and a wait, that is not really ownership of the data, regardless of what the contract says.
- Viewers that need a plugin or a separate desktop client. A study that will not open in an ordinary browser adds a point of failure and a support burden that a browser-native viewer does not have.
| Rented cloud PACS | Owned self-hosted PACS | |
|---|---|---|
| Where images live | On the vendor's servers, for as long as the bill is paid | On hardware the clinic owns |
| Typical monthly cost | $150 to $2,000 depending on volume and tier | Flat license fee regardless of study volume |
| 5-year cost at $700/mo | $42,000 in rent | $38,400 for a comparable combined license |
| Break-even point | Below roughly $642/month, renting is usually cheaper | Above roughly $642/month, owning is usually cheaper |
| If payment lapses | Depends on the vendor's contract terms | Depends on the vendor's contract terms |
| Who runs the hardware | The vendor | The clinic, or whoever it hires to maintain it |
Where MiniPACS sits
MiniPACS is a packaged self-hosted product, not an enterprise vendor built for hospital networks and not a do-it-yourself open-source build. The archive runs on hardware the clinic owns, the license is flat rather than per study, backups are encrypted before they leave the machine, and read-only access continues if payment ever lapses rather than a hard lockout. Licensing is per location, so a group grows by adding a license per clinic, each site running its own server. What it is not: an enterprise deployment for a hospital network's integration stack, or the free route of assembling something on top of Orthanc. For an imaging center or group weighing rent against ownership, see the landing for the full pricing and how the system is put together. For how PACS and RIS functions split up in a vendor's product, see RIS vs PACS.
FAQ
What are the main types of PACS system vendors?
Broadly four categories: large enterprise vendors built for hospital networks, cloud PACS subscriptions billed monthly per study or per user, open-source engines like Orthanc that a clinic or a contractor assembles into a working system, and packaged self-hosted products that combine a self-hosted archive with a license and support contract.
Is cloud PACS or self-hosted PACS cheaper?
It depends on the monthly rent. At a typical $700 a month cloud PACS bill, five years of rent runs $42,000 versus $38,400 for a combined self-hosted license. The math flips around $642 a month: above that, renting costs more over five years; below it, a self-hosted switch buys the archive rather than saving money outright.
What questions should I ask a PACS vendor before signing?
At minimum: who owns the data, what the export path looks like, what happens if you stop paying, where images physically live, how fast a study opens, whether ports are open to the internet, whether they sign a BAA, who owns backups and whether restores are tested, whether support is a person or a ticket queue, whether pricing is per-study or flat, and what the contract's exit terms are.
What is a red flag when comparing PACS vendors?
Per-study or per-exam pricing that scales up as the clinic grows, an export process that runs on the vendor's timeline rather than the clinic's, and viewers that require a browser plugin or a separate desktop client instead of opening in any modern browser.
What makes a PACS HIPAA compliant?
HIPAA compliance is not a checkbox on the software; it is a property of how the whole system is deployed and operated. The same PACS can be run compliantly or not, depending on access controls, audit logging, encryption, backups, and who holds the data under what agreement. A vendor that hosts your studies should be willing to sign a business associate agreement (BAA) and show how PHI is protected on their infrastructure. A self-hosted PACS keeps the studies on your own server under your own controls, which puts the compliance work, and the responsibility, in your hands rather than a vendor's. Ask any vendor how their system supports the specific safeguards HIPAA requires, rather than accepting compliant as a label.
Does an independent imaging center need an enterprise PACS vendor?
Usually not. Enterprise PACS vendors are built for hospital networks with many sites, complex integrations and dedicated IT staff. A single-location clinic or a small multi-site group is closer in fit to a packaged self-hosted product or a right-sized cloud subscription than to an enterprise deployment built for a different scale of problem.