What we value most about Localazy is how well it combines a very user-friendly translation workflow with powerful integration capabilities.
We use Localazy for localisation across both web and mobile applications, and the whole process is remarkably straightforward. The interface is clean and intuitive enough for non-technical team members, while the CLI, API and file-based workflows make it very easy to integrate Localazy into virtually any development and CI/CD environment.
Another feature we use regularly is the ability to quickly translate individual strings using multiple translation providers. It makes it very easy to compare alternatives, choose the most natural translation and move on without interrupting the workflow. For a project with many locales, this saves a considerable amount of time.
The integration between developers, project managers and translators is also very well thought out. Localisation does not feel like a separate process that has to be managed manually — it becomes a natural part of the product development workflow.
And finally, their support deserves a special mention. We recently faced a serious and very unusual localisation incident on our side. The Localazy team responded personally, involved their technical engineers and made a genuine effort to help us recover the data, including investigating recovery possibilities that went far beyond normal first-line support. That experience showed us that there are real people behind the product who care about their customers when something critical happens.
Overall, Localazy has turned what could be a complicated localisation infrastructure into something that is simple to operate, easy to integrate and reliable for day-to-day production use. Review collected by and hosted on G2.com.
The main limitation we have encountered is related to the number of requests made by end-user applications when retrieving translations.
For smaller projects this is unlikely to be noticeable, but when multiple production websites and mobile applications fetch localisation data directly from Localazy, the request limits can become restrictive surprisingly quickly. At our scale, direct delivery to every end-user device is therefore not really practical.
In practice, we solved this by putting our own caching/proxy layer in front of Localazy and effectively running our own localisation CDN. Fortunately, Localazy makes this relatively easy: the official CLI and appropriately scoped read access allow translations to be downloaded automatically and distributed through our own infrastructure.
Still, it means maintaining an additional piece of infrastructure for something that would ideally work out of the box. Localazy also offers its own CDN/delivery solution separately, but we would prefer to see more generous delivery limits included in the standard plans, especially for customers running several production web and mobile applications.
It is not a deal-breaker for us, and the available tooling provides a good workaround, but it is probably the area where we would most like to see improvement. Review collected by and hosted on G2.com.
