Platform

Helix is the core transport layer. Mercury builds on it. RedSpider runs it in the field.

The platform is deliberately structured as follows: Helix secures the movement of data between systems. Mercury applies those same transport and assurance foundations to secure messaging. RedSpider provides the deployment and control layer for corporate implementations.

Architecture at a glance

Applications and SystemsOperational workflows, files, messages and other data sources
iC-MercurySecure messaging capability built on Helix
iC-HelixCore transport layer for controlled, auditable data movement
RedSpiderExecution and control layer available as hardware or containerised software
InfrastructureCloud, on-premises or hybrid environments

Every corporate iCoriolis deployment is intended to run on RedSpider. Hosted individual Helix accounts can also be provided directly by iCoriolis to support beta testing, early access and wider adoption activity.

Core capability

iC-Helix

A secure data transport layer designed for environments where integrity, confidentiality and availability are critical. Helix can move files, structured data and messages while maintaining control, traceability and strong assurance over how that data travels.

  • Controlled and auditable movement of data between systems
  • Applicable to distributed and hybrid environments rather than tied to a single infrastructure model
  • Designed to support regulated use cases where transport risk must be addressed explicitly

Layered capability

iC-Mercury

A secure messaging capability built on the iC-Helix transport layer. By sitting on Helix, Mercury enables messages to benefit from the same security, auditability and integrity controls as any other data moving across the platform.

  • Signed, time-aware and verifiable communication patterns
  • Suited to sensitive operational and clinical workflows
  • Built to support trusted communication in high-consequence environments

Deployment and control layer

RedSpider

RedSpider is the deployment and control component for the iCoriolis platform. It provides the execution environment through which corporate platform capabilities are delivered, whether deployed as a containerised software instance or as a dedicated hardware appliance.

  • Standardises how the platform is deployed and enforced
  • Supports consistent control, policy application and operational behaviour across environments
  • Provides a practical enterprise deployment pattern familiar to infrastructure and security teams

Architectural position

Control and accountability matter more than infrastructure fashion

Many organisations rely on cloud services to support critical systems. That can bring flexibility and scale, but it also introduces complexity around responsibility, control and operational dependency. In practice, the distinction between provider responsibility and organisational accountability can create gaps in how sensitive data is protected in transit.

iCoriolis is not positioned as anti-cloud. It is positioned as pro-control, pro-accountability and pro-architecture clarity. The platform direction is intended to operate across environments while reducing reliance on any single point of control.

Current implementation

The current implementation is best described as an early-stage MVP demonstrating the core transport concept in practice. It is not being presented as a fully production-hardened platform.

Next-stage work

The most important next steps are architecture formalisation, governance, security diligence, assurance activities and the testing required to support production-readiness in regulated environments.

Why that matters

A secure platform that does not remain secure under scrutiny is not viable. Product credibility depends on architecture and assurance being treated as first-class concerns.