Platform to Platform · Australia and New Zealand
Protocolzone integrates ERP, CRM, finance and custom platforms, and modernises the systems a business already runs on without a rip and replace. The engineers who build an integration run it afterwards, with a 24x7 operations desk.
Engineering team in Ahmedabad, India, working across Australian and New Zealand business hours. We do not have an office in Australia or New Zealand.
Connecting two APIs on a good day is the easy part. These are the cases that decide whether an integration can be trusted with money, stock or customer records.
A call to another system times out. Did the invoice post or not? Retry it like an ordinary failure and you can post it twice. We record each instruction before it is sent and treat an uncertain result as its own state, with a defined recovery path.
How we handle uncertain resultsRecords drift apart: a session expires on one side only, a callback is lost, a reply arrives empty. Each kind of drift needs a reconciliation job that finds it and puts it right, not a support ticket.
Reconciliation in a live identity pipelineIdentifiers get reused, fields get renamed, history gets corrected after the fact. We map every source into one canonical model, keep mappings versioned and store corrections as new events.
Normalising feeds that disagreeIntegrations fail at 2am. Ours are watched by the engineers who built them, and a fault opens a ticket with the affected customer attached so they hear from us before they have to ask.
Acting before your customer noticesSAP, Oracle NetSuite, Microsoft Dynamics 365, Xero, MYOB and in-house finance systems.
Salesforce, HubSpot, Dynamics and the customer records your own platform holds.
Payment gateways and operator wallets, with idempotent requests and reconciliation.
Identity verification (KYC) providers, enterprise single sign on and audit trails.
Exchange APIs, data vendors and partner feeds, normalised into one model.
Databases, file drops and batch jobs that nobody wants to touch but everything depends on.
Payment, wallet, identity verification, exchange and market data integrations are work we have delivered and describe on this site. For ERP and CRM platforms such as SAP, Salesforce or NetSuite we work from the vendor's published APIs and your constraints. We do not claim a partnership or certification with any of them.
The system that runs your business keeps running it. We put an API and event layer around it, move one workflow at a time onto the new platform, and retire the old part only when the new one has carried real traffic.
Schema changes and releases are planned around a platform that cannot stop: when a deploy fails, the pipeline detects it and proposes the fix for an engineer to confirm.
Read the deploy remediation case studyTypical stack: Core Java and Spring Boot, Node.js, Python, Kafka, Kubernetes, MySQL, MongoDB and Cassandra, with Prometheus and Grafana for monitoring.
01
We map the systems, what must move between them, who owns each record, and how each connection can fail. You get a written plan with the first integration to build.
02
One workflow, end to end, with retries, reconciliation and monitoring. The old system keeps running alongside it.
03
The same team runs it 24x7 and moves the next workflow across. Modernisation happens one piece at a time, without a rip and replace.
Which systems, what has to move between them, and what happens today when it fails. A diagram or a list is plenty; a specification is optional.
Your enquiry goes directly to Kartik Modi, our Managing Director, and an engineer replies by email.
