Several languages are now available not only across the public website, but also in practical resources: how-to guides, documentation, and blog posts. This means developers can explore the product, understand its capabilities, and follow specific setup guides in a language that feels more familiar.
This matters especially for infrastructure tools.
Working with webhooks often involves server configuration, local development, NAT, firewalls, retry logic, delivery logs, and other technical details. Even when the interface itself is straightforward, documentation in an unfamiliar language can create unnecessary friction when you need to test an integration quickly or troubleshoot an issue.
Adal should be easy to evaluate before signing up, easy to configure once you start, and easy to use in day-to-day work. Language should not become another obstacle between developers and the information they need.
That is why localization in Adal goes beyond marketing pages. The available content includes practical resources that help with real-world tasks:
receiving webhooks on a local computer without a public IP address;
accepting webhook requests behind NAT or a firewall;
working with Telegram webhooks locally;
using servers, destinations, delivery history, retries, and replay;
understanding why webhooks can be lost and how to make delivery more reliable.
English remains the primary language of an international product, but Adal is now more accessible to a wider audience. Developers can explore the product and its documentation in the language that works best for them.
This is not a one-time update. New key pages, how-to guides, and important blog posts will continue to be available in the supported languages as Adal evolves.
Reliable webhook delivery should be clear not only at the infrastructure level, but also in the documentation that explains it. That is why multilingual support is part of the product itself, not simply a translation of a few pages.
You can switch languages anywhere in the public part of the Adal website.