Art2link was built from the ground up for Kubernetes — not packaged for it after the fact. Stateless workers, declarative deployments, per-pipeline scaling, and the operational ergonomics modern platform teams expect.
Pick the deployment that matches your security posture. The control plane, data plane, and customer data live in different places depending on which model you choose — toggle below to see each.
Art2link runs the runtime. You configure pipelines via console or API. Lowest operational burden, highest velocity. Most customers start here.
Control plane in Art2link Cloud. Data plane — including all message payloads — runs inside your VPC and never crosses the boundary. The right choice for regulated workloads.
The entire stack runs in your infrastructure — air-gapped, on-prem, sovereign cloud. Helm chart, offline activation, no inbound call-home.
Every pipeline runs as a pool of stateless workers. Crashes are non-events — pods restart, the message broker holds state, no in-flight work is lost.
Each pipeline scales independently. The high-throughput EDI lane doesn’t starve the low-latency HL7 lane. KEDA-driven, queue-depth-aware.
Messages persist only long enough to deliver — configurable retention per pipeline. Audit metadata is long-lived and immutable. Right-to-be-forgotten compliant.
Pipelines can span regions for disaster tolerance. Cross-region replication is opt-in per pipeline. Failover is config, not surgery.
VNet integration, Private Link, AWS PrivateLink, customer-managed IP allowlists. No public ingress required for any production pipeline.
Every pipeline change is a signed deployment artifact. Roll forward, roll back, A/B route — same primitives engineers expect for code.
Show us the topology you’re running today — we’ll sketch the Art2link version on a 30-minute call. No slides.