Knoldus Inc
Overall Review Rating
4.1 (4 Ratings)
Overview
Knoldus is the world’s largest Functional Programming (Scala, Rust, Java) and Fast Data (Spark, Flink) company. Our mission is to provide reactive & streaming fast data solutions that are message-driven, elastic, resilient, and responsive to build High-Performance Systems. We help organizations by developing and modernizing their system with custom IT solutions. We build on the work ethics and values, which translate directly to the quality of our systems.
Services
- Drupal
- Cryptocurrency Wallet Development
- Mobile App Development
- Web Development
- iOS App Development
- CRM Development
- Cross Platform Development
- Research & Investigation
- Android App Development
- Cross Platform App Development
- PHP Development
- App Marketing
Industries Served
Knoldus Inc Reviews
Have a look at these client reviews on previously delivered projects.
Zofia Kamińska
CTO - Odra Tech StudioApp store debut with a 4.7 rating. The reviews write themselves when the product is good.
Honestly, I came into this engagement with some scepticism. We had a bad experience with a vendor twelve months earlier and I wanted to see evidence of competence, not just hear about it. The discovery documentation was the first signal. The sprint delivery consistency was the second. By go-live I had stopped being sceptical and started planning how to expand the engagement. The production system has been stable from day one and our internal team loves working with the codebase they left us.
Project summary
Our internal team was committed to maintenance and could not absorb a new build of this complexity. An external partner was the only way to hit the timeline.
Beatriz Cavalcanti
Chief Digital Officer - Cerrado Tech SAEvery milestone hit. Every commitment met. No excuses, just delivery.
The technical quality is the obvious thing to highlight. The automated test suite is comprehensive, the deployment pipeline is solid, and the documentation is actually useful rather than written to satisfy a checklist. But the metric I keep coming back to is what has NOT happened since go-live. No 2am incident calls. No emergency patches. No post-launch retrospectives about what went wrong. For a system of this complexity, that outcome is exactly what we paid for.
Project summary
Unplanned downtime was our single largest controllable cost. Predictive maintenance data showed we could address most of it — but only with the right data infrastructure in place first.
Omar Al-Farsi
Chief Technology Officer - Falcon Digital VenturesFinally solved the trust problem our procurement team had argued about for two years
Honestly, I came into this engagement with some scepticism. We had a bad experience with a vendor twelve months earlier and I wanted to see evidence of competence, not just hear about it. The discovery documentation was the first signal. The sprint delivery consistency was the second. By go-live I had stopped being sceptical and started planning how to expand the engagement. The production system has been stable from day one and our internal team loves working with the codebase they left us.
Project summary
Years of incremental development had left us with a platform that was functional but limiting. A structured rebuild was the agreed path forward.
Ryan Calloway
Founder & CTO - Apex Digital Media LLCCustom workflows that match our sales motion exactly. No workarounds needed.
Our stakeholder group was unusually broad — board sponsors, operational users, compliance leads, and an IT team with strong opinions. I have watched vendors handle that kind of environment badly. This team adjusted how they communicated depending on who they were talking to, managed expectations honestly when things shifted, and delivered something that each group considers a success. Getting everyone to agree on that outcome was not straightforward and they deserve credit for making it happen.
Project summary
Broker portal satisfaction scores had fallen for two consecutive years. Specific feedback pointed to the same workflow frustrations. We needed a redesign, not a patch.