What's New in v26

Connexion v26 is a major platform release. It modernizes the runtime, adds Linux and cloud-native deployment options, introduces multi-active scaling, expands database and message-storage choices, and adds governed AI-assisted administration.

The pages below describe the customer-facing changes. Engineering implementation notes are consolidated into these broader stories rather than published as one page per internal change.

Platform and deployment

Modernized Runtime - .NET 10, x64, cross-platform services, and the foundation for the other v26 changes.
Linux Support - installing, configuring, and operating Connexion server workloads on Linux.
Multi-Active Application Servers - multiple active servers sharing workload and providing failover capacity.
Cloud Dynamic Scaling & Integration - cloud infrastructure integration and elastic capacity.
Kubernetes: Dynamic Scaling - how Connexion workload ownership works with Kubernetes scaling.
Kubernetes and Helm: Deployment & Management - installation, upgrades, configuration, and lifecycle management with Helm.
Dynamic Inbound Routing - publishing and routing inbound endpoints as channel ownership changes.
Modern service communications and APIs - Connexion’s legacy Windows-specific service transport has been replaced with cross-platform services built on Kestrel and gRPC. This supports Linux and container deployment, more efficient streaming between Connexion components (secure senders, remote agents), and modern management automation through a certificate-authenticated REST API.
Custom plugin compatibility - The overall device model, configuration experience, and operational concepts remain familiar in v26, but v16 plugins are not binary- or source-compatible without changes. The runtime has moved from .NET Framework to .NET 10; lifecycle and message-processing APIs are now asynchronous; some plugin APIs have been renamed, reorganized, or nested; and custom batch processing is integrated into the base device API rather than implemented through the former separate interface and queue mode. These changes provide a simpler and more efficient API, but existing plugins must be migrated and rebuilt for v26.

Data and message handling

PostgreSQL Support - PostgreSQL as a peer of SQL Server for configuration databases and message repositories.
SQL Server Queue V2 - the high-throughput partitioned SQL Server queue, including its repository-wide Tier 1 retention model and Tier 2 support.
Large Message / Attachment Support - streamed access to large message bodies and attachments, pluggable large-object storage, reduced memory use, and copy-free branching.
Message Archiving and Tier 2 Storage - moving completed partitions to queryable Parquet storage on filesystems or cloud object stores.

Security and governance

Modern Authentication, Authorization, and Certificates - pluggable authentication, server-side authorization, managed certificates, TLS hardening, and cross-platform secret protection.
AI-Assisted Connexion with MCP - governed AI access, listener exposure, bearer tokens, audit attribution, PHI guidance, and supported authoring and diagnostic workflows.

Development and transformation

As a Device Developer: What You Need to Know for v26 - migrating plugins to .NET 10, async lifecycle and message APIs, simplified custom batching, runtime/UI separation, and dependency isolation.
FHIR Devices and Transformation - HL7 v2-to-FHIR conversion, Firely FHIR R4 parsing and validation, FHIR REST delivery, and general-purpose Liquid transformations.
Liquid and Razor Transformation - FHIR Converter-compatible Liquid templates plus the cross-platform RazorEngineCore upgrade.

Operations and observability

Observability, Metrics, and Structured Logging - structured JSON logging, OpenTelemetry metrics, push and pull metrics delivery, managed-cloud export, and source-controlled dashboards.

Additional pages will be added as the remaining customer-facing v26 stories are distilled from the engineering feature library.