Freedom

The detach/reattach cycle is the practical implementation of Wapka’s philosophy: users own their data and can leave anytime. Here is exactly how it works. Step 1: Detach from the managed cloud From your dashboard: Export your data. The Dataset produces a portable JSON export. (Enterprise users can also request a full database clone.) Download your files. The file manager lets you export your entire storage directory as an archive. Your site is now independent. Nothing remains on Wapka’s servers that you do not have locally. Step 2: Self-host On your own server: ...

Most platforms build walls. Terms of service. Proprietary data formats. Export processes that technically exist but practically don’t work. The message is always the same: you can join, but leaving will cost you. Wapka takes the opposite approach. You can leave anytime. And that counterintuitive decision is exactly why people choose to stay. The open source foundation The entire Wapka codebase is open source on GitHub at wapka-web. Every line. The visual builder. The Lua engine. The legacy parser. The REST API. The admin dashboard. ...