Preserve useful interfaces.
Adapt requests, responses and authentication around stable boundaries, rather than rewriting every consumer.
The Avato Platform
A stable layer for continuous change.
Avato adapts interfaces and information, coordinates work, and applies operational controls between independent systems.
Applications, services and organizations can work together without sharing the same technology, data model, release cycle or owner.
Where Avato fits
Move change into the layer designed to absorb it.
Avato can support a single interaction, a business domain or a distributed ecosystem. The same approach keeps participants from becoming unnecessarily dependent on one another's implementation.
Coordinate shared work.
Compose services and information across applications, business units and independent organizations.
Coexist with your infrastructure.
Retain existing middleware, messaging and enterprise platforms where they continue to provide value.
Configuration-driven by design
Configure capabilities.
Reuse what works.
Customers do not need to develop custom application code to implement their integrations. Avato supplies configurable connectivity, transformation, orchestration, security and operational infrastructure.
Interfaces, schemas, transformations and supporting resources are grouped into packages. Teams combine them into solutions and carry the useful assets into the next initiative.
Discover
Find reusable capabilities and understand what each package provides.
Compose
Combine interfaces, transformations, policies and operational behaviour through configuration.
Extend
Build new capabilities on the same assets rather than starting over as systems change.
A practical example: this website is an Avato package.
The package maps page addresses to JSP resources. Its page declarations also provide the input for sitemap generation, keeping the route definitions and discoverable pages connected.
<Page name="avato-website-platform" jsp-file="/platform/index.jsp">
<Listening>
<Address>/platform</Address>
</Listening>
</Page>An understandable workspace
See how the integration is assembled.
Inspect interfaces, follow component connections and open the relevant documentation beside the work. Built-in testing and request/response views help teams examine actual behaviour.
Configuration defines how the solution runs. The browser workspace helps people understand, test and operate it.
Operational intelligence
Bring issues to attention.
Keep the context close.
Teams should not have to discover every problem by watching a dashboard. Notifications connect an operational issue with the information needed to investigate it.
Error Mailer
Useful notifications.
Less repetitive email.
The first fault sends an alert. Subsequent faults are accumulated into updates, with configurable exponential back-off between repeat notifications.
Recipients can see the affected interfaces and message summaries, follow orchestration references, and examine surrounding traffic.
NotifySend the initial fault notification.
SummarizeAccumulate faults and space repeat notifications according to configuration.
ClearSend an all-clear notification after the configured interval without further recorded faults.
A fault-free interval is distinct from a successful verification test. Operational Assurance provides the checks for intended business behaviour.
“If there's an issue with a connected system, we know before it becomes an issue in operations.”
Kanwar Hayer, BC Provincial Health Services Authority
PHSA uses its own notifications built on Avato's underlying Mailer to bring data mismatches, such as inactive stock records or invalid units of measure, to its team's attention.
Diagnostics and recovery
Follow an exchange.
Understand what happened.
Correlated records show the route through components and connected services. Inspect message metadata, headers, content and timing, then apply the appropriate correction or recovery process.
Trace and inspect.
Use correlation and message history to investigate the exchange, not just isolated log entries.
Retain and recover.
Persistent queues, configured retries and controlled resubmission support recoverable delivery.
Protect operational records.
Apply configured masking, retention and access controls to diagnostic information.
Operational assurance
Verify that the business path still works.
Automated tests, synthetic transactions and scheduled checks can exercise critical integration paths as applications and environments change.
Tests establish whether expected behaviour still holds. Recorded results and message sequences give teams evidence to investigate when it does not.
Deployment and customer control
Your environment.
No vendor SaaS control plane.
The runtime and its management capabilities operate under customer control, alongside configuration, credentials and operational records.
Infrastructure that fits.
Deploy natively or in virtual machines, containers, Kubernetes and highly available clusters. Fit the platform to your operating environment.
Changes on your schedule.
Select an edge, latest or stable release stream, or pin a specific version. Decide when to apply updates through your own validation and release process.
Private-network operation.
Avato does not require an Internet route to a vendor control plane. Customers can arrange update distribution through their own infrastructure for isolated environments.
Avato's online software-distribution services provide updates to systems that use them. They are not a SaaS control plane for customer deployments.
Explore at your own pace
See the product.
Then bring us your context.
Watch the Docker setup walkthrough, read the architecture reference or request access to evaluate the platform. A customer conversation starts with your objectives, not a generic demonstration.
Let's talk
What would a more adaptable architecture make possible?
Bring us the outcome you want to achieve and the systems or dependencies making it difficult. We will listen first, then explore the most useful next step.