About Translazor
Runtime translation for Blazor Server apps
Translazor helps .NET developers add multilingual support to Blazor Server applications without manually managing every translated string through traditional resource files.
Why Translazor exists
Building multilingual applications can become repetitive and time-consuming, especially when every page, component, title, meta description, and small UI label needs to be managed manually.
Translazor was created to make runtime translation easier for Blazor Server projects. It helps developers translate Razor pages, components, and SEO head content at runtime, then cache the results using MemoryCache or Redis.
The goal is practical: make it easier to build multilingual Blazor applications while keeping control inside the developer’s own application.
Meet the founder
Ahmed Elshorbgy
Translazor is built and maintained by Ahmed Elshorbgy, a .NET developer based in Vilnius, Lithuania. Ahmed works with C#, ASP.NET Core, Blazor, SQL, REST APIs, and backend systems, with a focus on building maintainable software that can be used in real-world production applications.
Translazor was created from a practical developer need: making multilingual Blazor applications easier to build without forcing every project into a large manual localization workflow from the beginning.
Backend experience
C#, ASP.NET Core, REST APIs, SQL, application architecture, and production backend systems.
Blazor focus
Blazor Server components, runtime UI behavior, page translation, and SEO head integration.
Cloud integrations
Practical experience with Azure integrations, caching strategies, and external services.
Developer-first mindset
Clear setup, predictable configuration, practical documentation, and maintainable code.
Product principles
Keep control in your app
Your Azure Translator key stays in your application. Translazor is designed so your translation setup remains under your control.
Reduce manual work
Translazor helps reduce the repetitive work of preparing translated UI text, page content, and SEO metadata manually.
Cache for performance
Use MemoryCache to start quickly, or Redis on paid plans when your application needs shared or production-ready caching.
Trust and data
Built with privacy-conscious architecture
No content stored on Translazor servers
Translazor does not store your page content or translated text on Translazor servers.
Your Azure key stays in your app
You configure your own Azure Translator key inside your application settings.
Built for Blazor Server
Translazor currently focuses on Blazor Server and .NET 8 or later.
Transparent third-party services
Azure Translator and Redis hosting are separate third-party services and are not included in a Translazor subscription.
Ready to try it?
Start translating your Blazor app
Start free with 1 target language, or read the quickstart to see how Translazor fits into a Blazor Server project.