SoftComply QMS Software Review

Bottom line: SoftComply is best understood as a set of regulated-content and workflow apps that turn Atlassian Confluence and Jira into a medical-device quality environment. It can be a pragmatic fit for a team already committed to Atlassian, but the complete solution is assembled from several products and suppliers rather than delivered as one standalone eQMS.

We retain our 3/5 rating. The approach offers strong authoring and useful medical-device content, while architecture, pricing and validation require more assembly than a single-vendor eQMS. This review uses SoftComply and Atlassian Marketplace information checked in August 2026.

What SoftComply actually sells

The SoftComply eQMS product is a QMS content package installed into Confluence. It provides a quality manual, policy, SOPs, technical-document templates, an example QMS and embedded guidance based on standards and regulations. It helps a team start and tailor its documentation; by itself, it is not the complete workflow and validation layer.

SoftComply's broader cloud eQMS architecture adds:

• SoftComply eQMS: controlled-content starting point and QMS checklist in Confluence.
• Document Manager: document lifecycle, approval, electronic-signature and audit-trail functions for Confluence Cloud.
• Validation for Confluence: automated integrity checks and validation documentation.
• Static Snapshots: frozen views of dynamic Confluence pages and macros.
• Risk Manager Plus and reporting: Jira-based product, enterprise, cybersecurity and other risk registers with Confluence reporting.

Confluence and Jira licenses also come from Atlassian. Other apps may be involved depending on the chosen workflow. Map every component, agreement, data flow and support boundary before treating “SoftComply” as one system.

Why the Atlassian approach can work

Confluence is a capable collaborative editor and knowledge base. Jira is a flexible workflow and issue platform. Many software and SaMD teams already use both, know their administration model and have single sign-on, backups and security review in place. Keeping QMS documents, engineering work and risk information in the same ecosystem can reduce duplicate tools and improve adoption.

The SoftComply content also addresses a real startup problem: an empty Confluence space does not tell a new quality manager which procedures and records are needed. Templates and an example system provide structure and prompts. They must still be adapted to the company's devices, roles and actual processes.

Document control

Document Manager is the key operational component for a controlled QMS. Its current Marketplace listing describes customizable approval workflows, electronic signatures, version and audit history, bulk approvals and a centralized task dashboard. It works with Confluence Cloud Standard or higher.

Evaluate the lifecycle using a representative SOP:

1. author and review a revision with restricted editors;
2. approve it with the required signature meaning;
3. make the correct version effective and available to users;
4. assign and record training;
5. change linked dynamic Jira content without silently changing the approved record;
6. create the next revision; and
7. retrieve the obsolete version, signatures and complete audit trail.

Dynamic pages are the hard case. A Confluence macro can show changing Jira data inside an apparently approved page. Static Snapshots is intended to freeze such content, but the team must define when and how snapshots become part of the controlled record.

Pricing: why the old “confusing” label was unfair but understandable

SoftComply now provides calculators and clearer component pages. On the eQMS page during this review, the displayed annual eQMS price was $2,900 and the page explicitly said Atlassian fees also apply. The document-management solution has its own calculator, and Jira/Confluence apps can be priced by user tier through Marketplace.

The commercial model remains composite. A realistic total may include:

• Confluence Cloud and possibly Jira Cloud;
• the annual SoftComply eQMS content license;
• Document Manager and any workflow dependencies;
• Validation for Confluence;
• Static Snapshots;
• Risk Manager Plus and validation; and
• configuration, migration, validation and support services.

SoftComply's eQMS terms describe annual advance payment and a one-year license period, so the former one-month minimum was incorrect. The trial exposes the QMS structure but limits content and functionality. Obtain a line-by-line quote at your actual Atlassian user tier and model growth because Marketplace pricing can jump at tier boundaries.

What happens if you stop paying?

SoftComply says a deployed QMS space remains when an eQMS license is not renewed, but macros and creation of additional QMS spaces stop working. That is helpful continuity, not a complete exit plan. The controlled solution may depend on Document Manager, snapshots and Atlassian itself.

Test an export and a disabled-license scenario. Confirm how pages, attachments, approval evidence, signatures, audit trails, Jira relationships and snapshot records are returned and read without active apps. Contract language should address data deletion and vendor access as well as retention.

Validation and shared responsibility

The validated state spans Atlassian Cloud, SoftComply apps, configuration, templates, user permissions and any integrations. Atlassian and each app vendor can release changes. Your organization needs a supplier and release-assessment process that identifies changes, evaluates impact and runs appropriate regression tests.

SoftComply's validation apps can automate checks and create documentation, which may reduce effort. Inspect the requirements, coverage and raw results. A weekly successful automated run does not prove your intended workflows, migrated content, permissions, signatures and operating procedures remain suitable.

Also review each Marketplace app's data residency, subprocessors, permissions and security program. “Runs on Atlassian” and “Cloud Fortified” are useful signals but do not make all apps one supplier or one security boundary.

Strengths

• Medical-device-specific QMS content, example documents and embedded guidance.
• Native use of familiar Confluence authoring and Jira workflows.
• Specialized document, snapshot, risk and validation apps can create a capable environment.
• Free trials and visible calculators improve evaluation.
• Deployed Confluence content remains accessible after the eQMS content license ends, subject to component limitations.

Tradeoffs

• The complete eQMS is a stack, so cost, validation, support and change management span several components.
• Templates require substantial company-specific review; old references in supplied content should be checked against current law and standards.
• Dynamic Confluence content needs deliberate snapshot and approval controls.
• Atlassian user-tier pricing can make expansion less linear than a simple per-user estimate.
• Structured data portability across pages, app records and Jira relationships must be demonstrated.

Best fit and evaluation checklist

SoftComply best fits an Atlassian-first medical-device or SaMD company with people capable of administering Confluence/Jira and owning validation. It is less attractive when the company wants one contract, one support desk and a fixed standalone eQMS data model.

1. Draw the full component and supplier architecture for the proposed solution.
2. Complete a controlled-document lifecycle with a dynamic Jira macro and snapshot.
3. Run a risk record through Jira, approval and a frozen Confluence report.
4. Inspect the automated validation requirements, evidence and failure handling.
5. Calculate five-year cost at current and expected Atlassian user tiers.
6. Disable a trial component and prove what remains usable and exportable.
7. Review every supplied SOP against current QMSR, MDR/IVDR and standards before approval.

Compare your next option

Start with our separate analysis of SoftComply pricing and its component stack. Then compare the broader field in the medical-device QMS software comparison and review the underlying products in the QMS software directory.

Sources

We reviewed the current SoftComply eQMS page, document-management solution, risk-management solution, eQMS terms and the Document Manager Marketplace listing. Recalculate pricing for your tenant before purchase.