Brio-IO Communication Server

Early Access

Brio-IO in Early Access

Brio-IO isn't available as a self-service download yet. We set up early-access accounts individually — so your setup runs cleanly from day one. Tell us which systems you want to connect, and we'll get back to you.

What Early Access includes

Server and UI — deployable independently

Brio-IO consists of two components that ship separately. You get both in Early Access; the N-to-1 architecture stays intact.

Brio-IO Server

Headless Communication Server

Spring Boot application that natively speaks HL7v2, FHIR, CDA, xDT and other healthcare protocols. Runs headless; multiple server instances can run against a single UI.

🌐

Brio-IO UI

Web interface for N servers

Single-page application with a server selector. One UI deployment controls multiple Brio-IO servers at once — production, staging and test in a single console.

Requirements

System requirements

Brio-IO runs on standard hardware. Java 21 and PostgreSQL 16 are the only unusual requirements — both are standard in modern Linux distributions. So you can prepare your setup even before you get access.

Brio-IO Server

  • Java 21 or higher
  • PostgreSQL 16+ (with pg_trgm, pg_partman)
  • 2 GB RAM minimum, 4 GB recommended
  • 2 CPU cores
  • 10 GB disk (more for message storage)
🌐

Brio-IO UI

  • nginx 1.20+ (or Docker)
  • Modern browser (Chrome, Firefox, Edge, Safari)
  • Reachability to at least one Brio-IO server via HTTP/HTTPS
  • Optional: TLS certificate for the domain
🐳

Docker (recommended operation)

  • Docker Engine 24+
  • Docker Compose v2
  • Linux host (or Docker Desktop on Windows/macOS)
  • For the server: persistent volume for Postgres

Ready to try Brio-IO?

Tell us which interfaces you want to replace or connect. We'll set you up with an early-access account and help with the migration from Mirth Connect.