About 8ninths
8ninths is a leading software development company. They wanted to see all of their clients succeed, not just trade them development. They are a Platform & Services company centered on allowing their clients to search and gain new power from AR & VR. They solve difficult problems with productive strategy & expressive developing. They would love to make your experience and chat about your project.
Last updated May 13, 2026
Services
Industries Served
8ninths Reviews
Write a ReviewCloud architecture that reduced our monthly infrastructure spend by over a third
Yuki Hashimoto / Head of Product Development - East Asia Commerce KKJan 25, 2026
Project summary: A previous engagement had delivered something that worked in staging and struggled in production. We approached this project with greater rigour in vendor selection as a result.
The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.
Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
Platform engineering work that let our product teams move independently at last
Niamh O'Sullivan / Director of Product - Munster Digital LtdJan 12, 2026
Project summary: Our internal product thinking was strong but our execution capability in this specific technology domain was limited. We needed depth, not generalism.
The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.
Production system that has performed as specified since go-live without remediation work, documentation thorough enough to support internal maintenance, knowledge transfer that left our team genuinely capable
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
Security posture transformed from a known liability to a competitive differentiator
Nora Al-Otaibi / VP of Engineering - Salam Digital SolutionsJan 03, 2026
Project summary: Matter management had become a significant overhead for our fee earners. Every hour spent on administration was an hour not spent on billable advisory work — the business case was straightforward.
We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.
Architectural decisions designed for longevity rather than just the current brief, thorough automated test coverage, post-launch stability that validated every technical choice made during discovery
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs