Your integrations. Your platform. Our boundary around it.
We don't sell an integration platform, and we don't ask you to migrate onto one. We build your integrations on a platform you choose and own, then put a secure, observed boundary around it. The boundary is what lets us see every flow, catch every failure, and keep your integrations healthy.
"The platform was never the point. What matters is that every flow is visible, every failure is caught early, and nothing stops working if you ever decide to leave. So we built our delivery around a boundary, not a product."
Vlad Leonov
Solutions Architect at Inite
The setup
One boundary, whichever platform you choose
Your systems stay where they are, outside the boundary. Inside runs a platform you own: Cloudflare, Restate, Microsoft Azure, or AWS. If you have a preference, we build on it; if you don't, we recommend one and explain why. Pick a platform to see how it looks, and try "What if we part ways?".
Xero
NetSuite
MYOB
HubSpot
Woolworths
ShipMonk
Starshipit
CartonCloud
Move Logistics
The protection
What the boundary does
Three things run at the boundary, on every platform, for every flow. This is the part we bring. Inside the boundary we use standard platform services with runbooks you can audit.
Security
Encrypted connections in and out, secrets held in a write-only vault, and nothing crosses the boundary unlogged. Credentials are stored so that nobody reads them back, including us.
Access control
Each system gets the narrowest access that works. Every integration runs under its own identity, so access is easy to audit and easy to revoke.
Watched, and self-healing
Every flow is observed: Kori, our AI Integration Support Engineer, watches around the clock. Failures retry with limits and then are investigated with full context, so fixes go in at the cause, not just the symptom.
The ownership
You own everything we build
The platform accounts are yours, and the integrations are code your organisation owns, in your repositories. Every flow ships with the artifacts that keep it maintainable without us, kept current as part of the work, not promised for later. This is what you hold:
A runbook for every flow
What it does, how it fails, and how to fix it, written so an engineer who has never met us could take over cold. The flow diagram is generated from the real flows, so it stays current instead of rotting in a wiki.
Changes you can audit
Updates arrive as reviewed pull requests to your code, sitting in your repository history like any other change. Every one has an author, a review, and a timestamp. Nothing quietly goes stale.
Knowledge lands with your team
Kori reports every investigation in the shared chat your team can see, so answers land where everyone reads them, not in one inbox. Cindy leads support, and alerts go to the whole team.
Built to not depend on any one person
"What happens if you get hit by a bus?" is a question we like being asked. Plenty of NZ businesses run on flows that live in one contractor's head; here, everything above answers it. We built Inite so nothing important lives in anyone's head.
It's also the exit plan. Cancel, and the boundary lifts away: your integrations keep running exactly where they are, and any capable engineer can take over from the documentation alone. Day to day, we work in the same shared chat as your other vendors, and the repo, secrets and diagram live in your accounts from day one, on the platform you chose and pay for directly. We would rather you stay because the service is worth it than because leaving is hard. The response times behind all of this are in writing on our pricing page.
What's the next step?
An hour talking through your systems and your future integration plans. No preparation needed, no obligation after.
Meet an integration architect