openIMIS

Self-hosted health-financing software supporting health-insurance claim submission, review and reimbursement.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Official Docker distribution and installation guide

  2. Operated by

    Your team

    Scheme operator and implementation partner host, configure and maintain the installation.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Docker distribution and installation guide
InfrastructureServers / containers
The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.
Licensing modelOpen Source / Open Core
The official openIMIS distribution is licensed under AGPL v3 and is available for operators to deploy and maintain. Implementation, hosting and operational services may have separate costs and agreements.
LicenseOpen-source; official distribution licensed under AGPL v3

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The project wiki documents a tested 2025 Keycloak OIDC integration, but its deployment guide requires contributor forks and feature/keycloak-integration branches. This establishes a prototype path, not inclusion in the current supported distribution. Confirm a merged/released integration and release-specific configuration before relying on production SSO.

openIMIS student-project integration versus the supported distribution; release inclusion unconfirmed · Source ↗ · User login and role mapping ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The project production guide links its Docker distribution and requires release-pinned database, backend and frontend image tags, strong secrets and disabled demo data. Development images and example administrator credentials are not the production configuration.

Modular openIMIS production Docker workflow; reconcile component and distribution releases · Source ↗ · Deployment artifact ↗ (repository default branch (moving); pin matching component release tags) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The official server requirements list a production minimum of two CPU cores, 8 GB RAM and 100 GB disk, with Linux as reference OS. This is a starting baseline, not a validated 100-user/1-TB HA deployment; separately size claims processing, attachments, database, replicas and backups.

Official modular openIMIS production minimum; workload and HA additions excluded · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The reviewed Docker distribution grants GNU AGPLv3 rights and disclaims warranty. Individual services/modules and implementation or hosting agreements require separate licence and support review; no commercial-service entitlement follows from the distribution licence.

Moving upstream Docker distribution licence reviewed on this date · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

A sector-specific claims product for health-financing and social-protection programs. Workflows include automated checks, medical review and reimbursement calculations. General property-and-casualty claims functionality was not established. Follow the official production and security guidance when implementing the Docker distribution.

Category fit

Claims management
Health-insurance claim submission, automated checks, medical review and reimbursement are documented; this is not a general property-and-casualty claims platform.

Compare within Claims management

  • FormKiQ Claims Management Directory PublisherManage claims intake, evidence collection, review, adjudication, and resolution with structured workflows, controlled access, and complete audit trails.
    • AWS
    Customer-operated · Commercial Only
  • Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Oracle Insurance Policy Administration (OIPA) (BYOL)Commercial life and annuity policy-administration software with associated claims workflows.
    • Oracle Cloud
    Customer-operated · Commercial Only

These products address related workflows; read their category-fit notes before comparing scope. See all of Claims management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • openIMIS production server deployment on named VPS providers ↗ · AWS, Azure, Google Cloud, DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The project wiki explicitly names AWS, Azure, Google Cloud and DigitalOcean for a VPS deployment of the Django/Gunicorn backend and Nginx frontend. Review the current distribution and modules, database and TLS configuration. Harden example settings such as debug mode, service users and credentials before handling production or health data.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory