English
Mozhi Hosting
Mozhi is a self-hosted translation front end that forwards each query to an engine you enable and returns the text in the browser.
- One click deploy
- 15 GB Disk Space Needed
- 1 GB RAM Memory needed
- From 2 € Price
No setup fees
Official links
Mozhi’s official links and original website
- More
Mozhi Website
What you get
on AvaHost
One-click deployment, a custom domain, free HTTPS, automatic application updates, and scheduled backups come with every Cloud App. You can run multiple apps on one server, and terminal access is included.
This template does not include a database container.
Tech
- Docker image
- codeberg.org/aryak/mozhi:latest
- Default port
- 0
How Mozhi works
Mozhi, by aryak, is an alternative front end for translation engines. It began as a maintained fork of SimplyTranslate and grew extra engines and an API. You run the small container, by default on port 3000, image codeberg.org/aryak/mozhi. There is no database. Visitors type text in the browser. Mozhi forwards the query to whichever engine is enabled and shows the result.
Engines mentioned upstream include Google, Reverso, DeepL, LibreTranslate, Yandex, MyMemory, and DuckDuckGo, each with an environment flag. A LibreTranslate URL can be set so that engine talks to an instance you choose. Default source and target languages are configurable. The process is a thin proxy: it does not contain the translation models itself unless you point it at a self-hosted LibreTranslate.
Key Mozhi features
You can disable engines you do not want exposed on your page. The API sits beside the web UI, which is useful if another tool on your network should translate without sending users to a public site. The image is small, which matches a Plan 1 baseline of 256 MB. There is nothing large to store beyond logs.
The privacy story is limited and should be stated plainly. The engine you enable still receives the text. Mozhi hides your visitors from browsing that engine's website directly. It does not stop the engine operator from seeing the query. Automatic updates and scheduled backups on AvaHost cover the container config, which is mostly environment flags.
Mozhi vs Google Translate
Mozhi
Mozhi is a page you host, with a switch for which backend answers. Google Translate is the hosted product people already know, with its own accounts, apps, and policies. Use Google Translate when you want that service as-is. Use Mozhi when you want the form on your hostname and the option to prefer LibreTranslate or to disable engines.
Google Translate
Quality follows the engine, not the front end. Mozhi does not invent a better model than the backend you selected.
Who uses Mozhi
Operators who want a translate box on an internal or public hostname use Mozhi. Teams that already run LibreTranslate use it as a friendlier front. It is a weak fit if you need an offline model inside the same container, because the default image does not bundle one.
Self-hosting Mozhi: requirements and cost
The baseline is 256 MB of RAM and a quarter of a CPU core, no database container, image codeberg.org/aryak/mozhi. On AvaHost the recommended minimum for Mozhi is Plan 1 at €2. The Mozhi package includes one-click deployment, your hostname, automated HTTPS, automatic updates, and scheduled backups. Application mail is not included with Mozhi. Engine terms, rate limits, and any API fees belong to those engines, not to this plan.
F.A.Q
Mozhi is listed from €2 on Plan 1. The price is the front-end container, not a translation model and not a paid engine subscription. If you attach DeepL or another metered API, that vendor bills you separately. The process is small, so most people stay on this minimum unless they colocate a heavy LibreTranslate beside it.
Yes. Point the hostname at the instance and automated HTTPS covers the translate page. Visitors then avoid opening each engine site themselves, while the server still calls the engine you left enabled. You control DNS and which engine flags are on.
AvaHost updates Mozhi automatically. There is no database to migrate. Backups on a schedule cover the deployment. After an update, submit one short phrase and confirm the engine you rely on still answers. Keep a note of the environment flags, especially a custom LibreTranslate URL.
Only partly. Mozhi stops visitors from using the engine website directly, but the enabled engine still receives the text. Pick LibreTranslate on hardware you trust if that distinction matters. Public engines keep their own logs and policies. Mozhi is not an offline translator unless you supply one.