Architecture

CONCEPTUAL DOCUMENTATION

Runtime is in development. These guides explain design intent; they are not a released API or installation reference. Read the release policy →

A foundation with distinct responsibilities

Runtime is the execution foundation under active development. Studio, Platform, AI, and Cloud are planned products around it. The diagram below describes ownership boundaries, not deployed services.

Conceptual architecture: Studio and AI support authoring, Runtime connects external systems, and Platform and Cloud provide planned operational layers.

Layer	Intended responsibility	Maturity
Runtime	Java reactive integration execution	In development
Studio	Low-code and visual authoring	Planned
Platform	Management and control plane	Planned
AI	MCP and Developer Skills	Planned
Cloud	Cloud-neutral hosted iPaaS	Planned

What reactive means here

Reactive composition is a way to express asynchronous work and demand. It is not a guarantee of unbounded throughput, zero blocking, or automatic reliability. Connector boundaries still need cancellation, time budgets, bounded resources, and explicit failure semantics.

The exact Runtime threading, scheduling, memory, and cancellation contracts are not published in these conceptual docs. No performance benchmark is claimed.

Keep hosting outside integration logic

Cloud-neutrality is a design goal. Provider-specific resource provisioning, identity, network policy, and persistence belong at defined boundaries. Portability still requires testing on each supported environment; it cannot be established by architecture language alone.

Separate the public web from the product

This public website is static HTML, CSS, and JavaScript. It does not host a customer console, Runtime execution, secrets, or a management backend. Any future account portal will be a separate deployment with its own security model.

See deployment boundaries for the distinction between serving these docs and deploying a future Runtime release.