A: 1. Does this work similarly to Localize and Weglot, where we create DNS on a CNAME?
• Yes, MultiLipi uses a similar approach for handling translations. You can set up a CNAME for each language subdomain (e.g., en.domain.com, es.domain.com) and route traffic to the translated content.
2. Where are the servers located and on what platform? AWS, etc?
• Our servers are hosted on Azure, leveraging a robust infrastructure to handle translations securely and reliably.
3. What is the latency like? Are you using a Google Translate-like feature to do the automatic translations?
• Latency is typically low. We use Azure’s translation services, which provide fast and efficient translations. We are working on optimizing the performance and plan to switch to Google Translate post-AppSumo to further improve accuracy and performance.
4. Is there a frontend where we can log in and manually tweak the translations?
• Yes, MultiLipi provides a frontend dashboard where you can manage your translations. You can review, edit, and approve translations manually as needed.
5. How many users per account?
• MultiLipi allows a single account to manage multiple projects. The number of users per account may depend on the tier you have subscribed to. You can invite team members to collaborate on projects.
6. The translation words, once a word is translated and doesn’t change, will it be counted as translated again the next month?
• No, once a word is translated and stored in the system, it won’t count again for the next month unless it’s part of a new or updated page.
7. What is considered as a Translated request? If a word has already been translated, it shouldn’t need to be translated again?
• A translated request is any time a page or text is accessed and the translation is served. If the text is already translated and cached, it won’t consume credits again.
8. Please explain what does Translation memory mean?
• Translation memory stores previously translated content to ensure consistency across pages and minimize redundant translations. It helps you avoid translating the same content multiple times.
9. What data is sent to your backend?
• We collect basic data to facilitate the translation process, such as page URLs, content, and language preferences. The content is processed by our translation system and is not used for any other purpose.

If you have any more questions or need further clarification, feel free to reach out. We’re here to help!