About Multilify
Why the plugin exists, how it is built, and what it will never do.
Why it exists
Every established multilingual plugin for WordPress either duplicates your posts or routes your content through someone else's servers, and the feature you actually need tends to sit behind a license. Multilify started as the version of that tool with none of those trade-offs.
How it is built
A translation is not a second post. Each post carries all of its translations in post meta, keyed by language code, and per-language rewrite rules resolve the localized URL back to the original. That is the whole design, and everything else follows from it.
Who maintains it
Kadir Erman, one developer, unpaid. That is worth knowing before you put it on a production site, so here is what it means in practice: releases come when there is something worth releasing, bug reports get read, and the limits above are the ones that will still be true next year.
Getting help
Open a thread on the WordPress.org support forum for anything about using the plugin, or a GitHub issue for anything about the code. Expect a reply within a few days.
What it will not do
Ship a paid tier
Call a third-party translation API
Send your content anywhere
Require another plugin to work