We do not publish client names. We do publish exactly what we built, for which sectors and in which regions — and we will arrange a reference call where the client agrees to it.
We do not publish client names or logos. Every engagement is covered by confidentiality, and that does not lapse because a logo would be useful on a website. Several of our clients operate payment and telecommunications infrastructure where even the fact of a supplier relationship is sensitive.
What we can do is tell you exactly what we have built, for which sectors, in which regions — and let you judge the engineering rather than the logo.
A business-critical system moved onto a two-node Always On platform with automatic failover and encryption at rest, in Australia.
Read more ›Distributed availability groups across two data centres, with disaster recovery testable without an outage.
Read more ›A group replication cluster with automatic promotion and a phased migration onto it, and an Oracle RAC estate moved onto new storage and proven against real applications before production followed it.
Read more ›A business-critical database moved onto a managed Azure platform with no transaction lost at cutover, geo-replicated to a second region that also carries read traffic.
Read more ›The database platform behind a mobile money launch in a new market, proven before it carried traffic.
Read more ›Delivered from Melbourne, with a delivery centre in Colombo. Database work is the exception to that and always has been — every login to a client database instance is made by an Onsys consultant based in Australia.
Published
Every engagement is covered by confidentiality, and several of our clients operate payment and telecommunications infrastructure where even the existence of a supplier relationship is sensitive. We would rather describe the engineering in full and leave the name out than publish a logo we have not been given permission to use.
Where a comparable client agrees to it, yes — we will arrange a reference conversation. We ask them first, which is why we cannot promise it before you ask us.
Read the case studies. They describe the architecture, the decisions and the reasoning in enough detail that your own DBA or architect can tell whether the people who did the work knew what they were doing. Every engagement listed was delivered as a fixed-price project, to the agreed timeline, without a cost variation.