The route is under construction.

When “sent” is not the same as “applied”.

A target system can accept an operation just before the network loses its answer. Retrying automatically may then create a second business effect. Route 7 is building an operation-aware outcome contract that records this boundary as durable uncertainty, stops blind retries, and routes the case into evidence-backed reconciliation.

This is not glamorous infrastructure, but it is central to the promise behind a trusted data route: delivery speed only matters when the business can also understand what happened.

Current focus: proving the same outcome model across REST and OData operations before expanding deployment certification.

Measured throughput, careful claims.

A bounded three-node engineering run reached a 12,177 messages-per-second baseline and repeated above 11,000 messages per second during controlled consumer recovery. The run completed without silent loss or conflicting outcomes, while also revealing replay work that now feeds directly into the reliability contract above.

These are controlled laboratory measurements, not a public SLA or a production-readiness claim. Repeatability matters more than a single peak number.

One product core, several roads to production.

Route 7 is packaging the same tenant-safe product core for on-premises Kubernetes, hyperscaler environments, a shared VPS profile, and SAP BTP Kyma. Configuration, identity, connectivity, storage, and scaling adapters may change; the distribution, consistency, audit, and delivery model must not.

The Kubernetes and bounded VPS profiles are moving through repeatable build, recovery, and upgrade checks. The SAP BTP Kyma package now has versioned deployment profiles, edge policies, and non-mutating preflight checks; live runtime certification remains ahead.

This work is how “one route for every environment” becomes an engineering constraint, not just a line on the homepage.