Sold by: Saga IT
Deployed on AWS
AWS Free Tier
OpenShare Engine on Windows Server 2025: the Open Integration Engine with the OpenShare admin plugin preinstalled. Run Mirth Connect / OIE channels on your own EC2 instance and administer them from the browser.
Overview
Image
Browser-based engine dashboard
Image
Optional: connect the engine to the free OpenShare console
Image
Fleet monitoring for a connected engine
Image
Message browser with raw HL7 view
Image
Channel list
Image
Servers in the OpenShare console
Image
Console access connections
OpenShare Engine is Saga IT's maintained, OpenShare-branded build of the Open Integration Engine (OIE, the community continuation of Mirth Connect) as a ready-to-run image: engine 4.6.0 on Windows Server 2025 with a bundled Java 21 runtime and the signed OpenShare admin plugin preinstalled. It handles HL7 v2, FHIR, DICOM and X12; existing Mirth Connect and OIE channels import unchanged.
Patched ahead of upstream. This build carries security and bug fixes the current upstream OIE release does not: the web server is Jetty 12 where upstream still ships the end-of-life Jetty 9 line, and Derby, Jackson, Log4j and other libraries are kept current. Defects we find in the field, such as a DICOM sequence round-trip crash, are fixed here first and contributed back upstream. Code-signed by Saga IT; source published under the MPL 2.0.
Secure by default. Each instance generates its own administrator and keystore passwords at first boot; no shared or default credential exists. The password is written to a SYSTEM/Administrators-only file and retrieved with SSM Run Command, and repeated failed sign-ins lock the account. Open only port 8443 plus the ports your channels listen on; RDP is not required.
Bring your own database. Run standalone on the embedded database, or point the engine at PostgreSQL, SQL Server, MySQL or Oracle through EC2 user data at launch. Java heap is sized to half the instance's memory, so one image serves the smallest instances and the largest.
Optional browser administration with OpenShare, a free service from Saga IT: manage the engine from any browser over an outbound-only, end-to-end encrypted connection, with no inbound ports and no PHI visible to the service, and exchange data with partner organizations under sharing agreements. The engine is fully functional on its own; the optional connection is set up at launch as described in the documentation.
This software is free. AWS bills the EC2 instance and EBS storage it runs on at standard rates.
Highlights
- Saga IT's maintained OpenShare build of OIE 4.6.0 (the Mirth Connect community continuation), patched ahead of upstream: Jetty 12 web server and current libraries where upstream still ships end-of-life Jetty 9; field bug fixes land here first and are contributed back. Windows Server 2025, Java 21, signed OpenShare plugin preinstalled.
- Secure from first boot: a unique administrator password and keystore password per instance, delivered in a SYSTEM/Administrators-only file read via SSM Run Command; repeated failed sign-ins lock the account; only port 8443 needs to be open and RDP is not required. HL7 v2, FHIR, DICOM and X12; existing Mirth and OIE channels import unchanged.
- Optional browser administration through OpenShare, a free companion service from Saga IT: outbound-only, end-to-end encrypted management and partner data exchange with no inbound ports and no PHI visible to the service. The engine is fully functional on its own.
Details
Sold by
Delivery method
Delivery option
64-bit (x86) Amazon Machine Image (AMI)
Latest version
Operating system
Win 2025
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
This product is available free of charge. Free subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
If you are an AWS Free Tier customer with a free plan, you are eligible to subscribe to this offer. You can use free credits to cover the cost of eligible AWS infrastructure. See AWS Free Tier for more details. If you created an AWS account before July 15th, 2025, and qualify for the Legacy AWS Free Tier, Amazon EC2 charges for Micro instances are free for up to 750 hours per month. See Legacy AWS Free Tier for more details.
Dimensions summary
This listing carries no software license fee. You install the OpenShare Engine plugin on your own Windows server and run it from your browser. The many line items you see are AWS EC2 instance types, each billed hourly. They cover compute-optimized (C), storage-dense (D, I), general-purpose (M), memory-optimized (R, X, Z), and burstable (T) families across several hardware generations. Larger instance sizes carry more CPU, memory, and higher hourly rates. Pick the instance that matches your workload; you pay only the hourly infrastructure cost while the instance runs. Running your own servers is free.
Top-of-mind questions for buyers
Each line item is one AWS EC2 instance type, billed per hour it runs. The rate covers the underlying compute infrastructure — CPU, memory, and storage tied to that instance size. The OpenShare Engine plugin itself carries no software fee; you pay only the running instance-hours.
Software charges apply only while an instance runs, metered by the hour. A fully stopped instance stops accruing hourly compute charges. Underlying AWS storage tied to a stopped instance may still incur separate AWS fees, but the instance-hour meter counts running time only.
Running your own integration servers, monitoring your fleet, and building channels are free. You pay only the hourly cost of the EC2 instance you pick here. Reaching other organizations across the exchange network becomes a separate membership feature after the open beta, not part of this hourly listing.
saga-it.com
Helpful?
Vendor refund policy
This is a free product; there is nothing to refund. Questions: support@saga-it.com
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
OpenShare Engine 4.6.0 on Windows Server 2025, with the signed OpenShare admin plugin preinstalled. Each instance generates its own administrator password and TLS keystore password at first boot; no shared or default credential is ever reachable. Optional EC2 user data can connect the engine to the free OpenShare service and point it at your own PostgreSQL, SQL Server, MySQL or Oracle database. Java heap is sized automatically from the instance's memory.
Additional details
Usage instructions
-
GET YOUR PASSWORD. Each instance generates a unique administrator password at first boot and writes it to C:\ProgramData\OpenShare\initial-credentials.txt (SYSTEM and Administrators only). This file is the ONLY delivery path on Windows - the password is deliberately never written to console output or the event log. Read it with SSM Run Command (AWS-RunPowerShellScript, command: Get-Content 'C:\ProgramData\OpenShare\initial-credentials.txt'); the instance needs an IAM role with AmazonSSMManagedInstanceCore. RDP works too. After you change the password the file is no longer valid; delete it.
-
SIGN IN. Open https://<instance-dns>:8443 in a browser and sign in as 'admin', and change the password immediately. The instance ships a self-signed certificate, so your browser will warn on first visit; install your own certificate for production use.
-
OPEN ONLY WHAT YOU NEED. The recommended security group opens 8443 and nothing else - you do not need inbound RDP to get started, because SSM Run Command needs no open port. If you want RDP, add 3389 yourself and scope it to your own address range rather than 0.0.0.0/0. Any inbound port your own channels listen on (for example an MLLP listener) needs BOTH a security group rule AND a Windows Firewall rule - Windows blocks it by default even when the security group allows it.
-
DATABASE, BACKUP AND KEYS. By default the engine keeps channels, configuration and message history in an embedded Derby database under C:\Program Files\OpenShareEngine\appdata. To back it up, stop the OpenShare Engine service, copy that directory (or snapshot the EBS volume), then start the service again; restore by copying it back before starting. The TLS keystore is C:\Program Files\OpenShareEngine\appdata\keystore.jks; its password was generated at first boot and is recorded in C:\Program Files\OpenShareEngine\conf\mirth.properties, readable only by the engine service user. Replace the self-signed certificate with your own for production and rotate the keystore password from the engine's Settings when you do. At launch, EC2 user data can instead point the engine at your own PostgreSQL, SQL Server, MySQL or Oracle database; include TLS in the JDBC URL (PostgreSQL sslmode=require, SQL Server encrypt=true) because it carries your clinical data.
-
OPTIONAL BROWSER ADMINISTRATION. OpenShare is a free service from Saga IT that lets you manage this engine from any browser over an outbound-only, end-to-end encrypted connection. The engine is fully functional without it. If you want it, the connection is set up at launch through EC2 user data as described in the documentation (link below); it needs no inbound ports and involves no additional cost.
-
HEALTH. In the EC2 console, confirm the instance passes both status checks. The engine is up when https://<instance-dns>:8443/api/server/version returns HTTP 200 (allow several minutes on first boot). The engine log is C:\Program Files\OpenShareEngine\logs\mirth.log; the Dashboard in the web interface shows per-channel status and message counts.
-
SIZING AND QUOTAS. Any listed instance type works; small workloads run on the smallest, and Java heap is set automatically to half the instance's memory. t3 instances earn CPU credits and a busy estate can exhaust them; for sustained production load use a non-burstable type or t3 unlimited. One engine per instance; no AWS service quota beyond the default EC2 limits is needed.
-
COST. This software is free. AWS bills the EC2 instance, EBS storage and data transfer at standard rates.
Documentation: https://docs.openshare.health
Support: support@saga-it.com
Resources
Vendor resources
Support
Vendor support
Support: support@saga-it.com
When reporting a problem, include the engine version shown on the sign-in page, your instance type, and the relevant lines from C:\Program Files\OpenShareEngine\logs\mirth.log. Never include patient data in a support request.
Documentation: https://docs.openshare.health
Source code for the OpenShare Engine build (MPL 2.0): https://github.com/SagaHealthcareIT/open-integration-engine
This software is free, and so is the optional OpenShare service; the engine runs fully standalone without it.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
OpenShare Engine on Ubuntu 24.04 LTS: the Open Integration Engine with the OpenShare admin plugin preinstalled. Run Mirth Connect / OIE channels on your own EC2 instance and administer them from the browser.
Symantec Protection Engine for Cloud Services is a flexible and feature rich client/server application that provides primary and advanced malware and threat detection technologies for application data protection through a single yet simple engine maximizing your AWS protection and performance
Deploy Docker Engine on Windows Server 2022 running the Docker Enterprise Engine
Symantec Protection Engine for Cloud Services is a flexible and feature rich client/server application that provides primary and advanced malware and threat detection technologies for application data protection through a single yet simple engine maximizing your AWS protection and performance.
Customer reviews
No customer reviews yet
Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.