Replace what needs to change.
Keep surrounding applications outside the rewrite effort where their existing behaviour can be preserved.
Why Avato
Make the change that matters.
Keep the value you've built.
Modernization should create new capability, not make every existing investment a prerequisite for replacement.
Avato makes replacement, coexistence and new capabilities more manageable by separating the change you need from the systems that should keep working.
Business value
Ambitious change.
Without unnecessary change around it.
The choice is not simply “keep everything” or “replace everything.” Change what no longer serves the business, preserve what does, and introduce new capabilities in between.
Coexist through the transition.
Manage sequencing and operational exposure while old and new systems work alongside one another.
Create what comes next.
Build new services and shared processes from capabilities the organization already has.
Keep effort focused on the outcome.
Changing a core platform does not automatically need to become a redevelopment programme for every connected application.
Avato adapts interfaces, information and behaviour at stable boundaries. In the banking conversion, three critical applications retained their code and interfaces.
See the banking resultDeliver capability before every system is replaced.
A new operating model can span existing applications, technologies and organizational boundaries.
BC Health Authorities coordinated hospital replenishment across independently managed systems while retaining their enterprise applications and responsibilities.
See the healthcare resultMake the next initiative easier.
Interfaces, transformations, policies and operational controls should carry value beyond the project that created them.
Avato packages reusable capability. Established banking integration assets later supported alerts, insurance calculations and contact-centre modernization.
Explore composition and reuseOperate the result with confidence.
An integration that works once is not enough. Teams need to know when attention is required, understand the exchange and verify expected behaviour.
Notifications, correlated messages, diagnostics, recovery mechanisms and automated checks are part of the platform, rather than utilities to rebuild for each project.
Explore operational controlOwn the continuing evolution.
The lasting value is not only a working implementation. It is the customer's ability to keep building.
PHSA's team continues to develop new functionality and capabilities on Avato without Avato's assistance. Customer-controlled deployment also keeps the runtime, management and operational records within the customer's environment.
Read about customer independenceConfiguration-driven delivery
Use the platform.
Not a new codebase for every integration.
Customers configure how reusable components receive, adapt, route and coordinate work. The platform supplies the managed execution and operational capabilities.
When a genuinely new technical capability is needed, Avato extends the reusable platform and exposes that capability through configuration. The intent is to keep customer solutions adaptable without customer-specific application forks.
“Avato enabled us to align the outcomes we wanted to achieve in the time frame and price point we were targeting.”
Gustavo Estrada, then Acting Provincial Director, Performance & Transformation, BC Provincial Health Services Authority
Where Avato earns its place
Look for change that crosses important boundaries.
Avato is especially relevant when critical systems must evolve independently, multiple organizations need to cooperate, existing applications must survive replacement, or reusable operational controls matter.
Coexistence, not forced consolidation.
Existing integration tools and enterprise platforms can remain where they provide value. Avato can complement, augment or replace selected capabilities.
Control, not a mandatory cloud dependency.
Operate without a vendor SaaS control plane. Select release streams or versions and manage when updates are applied.
Fit, not a universal prescription.
A simple, stable connection may not warrant a new orchestration layer. We start by understanding whether Avato would improve the change you need to make.
Let's talk
What would you change if those dependencies were manageable?
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.