Wapka is an open-source, all-in-one web development platform that combines a visual site builder, a server-side Lua scripting engine, backward-compatible legacy support, and a full REST API. It has existed for over a decade, evolving through three eras without breaking anything built in the first one.
It is the only platform that simultaneously serves absolute beginners, intermediate users, advanced developers, and AI agents — without requiring migration at any stage.
What Wapka is
At its core, Wapka solves a problem most platforms don’t: how do you give someone a website that starts simple but can grow into something powerful — without ever forcing them to rebuild?
You sign up. You get a visual builder, server-side scripting, a database, file storage, SSL, CDN, and pre-built modules — instantly. If you never write a line of code, you have a functional dynamic site. If you do write code, you have a full-stack development environment. If you want to leave, you export your data and self-host.
The architecture
| Component | Technology |
|---|---|
| Backend | PHP (core), Lua (scripting) |
| Scripting runtime | Lua 5.1 via PHP LuaSandbox |
| Database | NoSQL Dataset |
| API | Full REST |
| Containerization | Enterprise (public soon) |
| AI protocol | MCP |
The choice of Lua is deliberate. In a shared hosting environment running thousands of user scripts, you need sandboxing that is fast, secure, and cheap. Lua via PHP LuaSandbox provides all three. It is why the free tier exists at all.
The platform runs three request handlers simultaneously — a legacy parser for old WAP tags, a Lua router for modern scripts, and a Native App handler for visual builder pages — all against the same data layer. Code from 2013 and code from 2026 coexist without conflict.
The freedom model
Wapka is open source on GitHub. You can:
- Export your data as JSON — no proprietary format
- Clone the repository and run
docker compose up - Self-host on your own server with the same software
- Reattach to the managed cloud anytime
This is the opposite of vendor lock-in. Most platforms build walls. Wapka builds doors that open from both sides.
The verdict
| Category | Score | Notes |
|---|---|---|
| Concept | 10/10 | Open-source, self-hostable, backward-compatible, AI-ready |
| Architecture | 9/10 | Lua sandboxing is the key insight. Three-era compatibility is unique. |
| Infrastructure | 9/10 | 100GB free tier with SSL and CDN is unmatched. |
| Freedom | 10/10 | Raw DB export. Docker self-host. No lock-in. |
| AI readiness | 10/10 | MCP protocol. Markdown-native docs. Future-facing. |
| Developer experience | 7/10 | Lua ecosystem is niche. Self-host docs could deepen. |
| Non-tech experience | 9/10 | Visual builder. Pre-built modules. Zero DevOps. |
| Overall | 9/10 | Best “own your data” platform available. |
Who it’s for
- Creators who want a visual builder with room to grow into code
- Students learning full-stack — free, no credit card, no DevOps
- Developers who value open source, self-hosting, and data ownership
- Small teams building dynamic sites without infrastructure overhead
- Anyone who has been burned by platform lock-in
Who it’s not for
- Teams needing a massive plugin marketplace (use WordPress)
- Frontend specialists committed to Next.js/Vercel
- Enterprises requiring corporate SLAs without self-hosting
- Teams unwilling to work with Lua at all
The bottom line
Wapka is not trying to be the biggest platform. It is trying to be the most free. Free to use. Free to leave. Free to self-host. Free to grow. Free to integrate with AI. Free to own your data.
Most platforms ask you to trust their brand. Wapka asks you to trust the code — because the code is open and the exit is always available.
That is the strongest foundation a platform can offer.
Continue reading: Why Lua? The architectural decision → You can leave anytime — and that is why people stay → Wapka vs WordPress vs Wix vs Vercel →