Overall Review Rating
4.6 (5 Ratings)
Services
- Maintenance
- Cloud Provisioning Services
- Android App Development
- AWS Services
- Cross Platform Development
- DevOps
- Mobile App Development
- Cloud Governance
- iOS App Development
- CMS Development
- Web Development
- Digital Strategy
Industries Served
Amasty Reviews
Have a look at these client reviews on previously delivered projects.
Julien Moreau
Co-Founder & CTO - TechLyon SASClean code, solid documentation, and a site that actually converts
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
OTA update orchestration for our software-defined vehicles needed to be bulletproof. The liability implications of getting it wrong were significant enough to justify specialist development.
Sarah Kimball
Product Manager - Clearpath Health SolutionsTokenisation from whitepaper to mainnet without a single major incident
The platform has been live for six months and is handling three times the transaction volume we scoped for. That is not because we underestimated — it is because the architecture choices made during discovery were genuinely forward-thinking. Most vendors design for exactly what you tell them. This team designed for what you are likely to need. We are already scoping the next phase and there was no question about who we would use.
Project summary
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Matthieu Renard
Directeur Technique - Lumière Technologies SASWebsite went from liability to lead driver within 90 days of launch
We received proposals from six vendors. Four of them quoted us prices that bore no relationship to the actual scope. This team came back with something realistic and then delivered against it exactly. I have worked on enough technology projects to know that the gap between what is proposed and what is delivered is where trust gets destroyed. There was no gap here. What was promised is what we got, and the ongoing relationship we have built from this is something we intend to continue.
Project summary
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Tom Harding
Founder - Meridian SaaS LtdDelivered what the proposal described. More rare than it should be.
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
First notice of loss was averaging three days. The market benchmark was under four hours. Automating intake and triage was the agreed priority for the year.
Marcin Lewandowski
Engineering Manager - Kraków Digital Sp zooVR training module preferred by 89% of trainees over the classroom alternative
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
Grid modernisation funding required us to demonstrate demand-response capability. The ML models existed on paper — we needed an engineering partner to build and deploy them.