Wapka has been evolving for over a decade. The roadmap ahead is shaped by what the community has asked for, what the technology now enables, and what the platform needs to serve the next generation of builders.
2026 priorities
- Advanced native apps: deeper integration with mobile platforms. Progressive web apps with offline support.
- Lua framework v2: improved debugging, better error messages, module sharing system. Making the scripting experience even more accessible.
- Full OpenAPI REST: complete, documented, machine-readable API specification. Enables AI agents and external services to interact with the platform at any level.
- MCP protocol maturity: expanded AI integration. More endpoints. Better documentation for model consumption. The platform becomes fully AI-operable.
- Self-hosting improvements: streamlined Docker setup, one-command deployment, improved upgrade paths. Making self-hosting as simple as managed.
Beyond 2026
- Federation: the ability for self-hosted Wapka nodes to optionally connect to the broader network while maintaining independence. A distributed model where users choose their level of integration.
- Expanded module marketplace: community-built modules discoverable from within the platform. Sharing what people around the world create.
- Enhanced collaboration: multi-user editing, role-based access, team workflows. Building together.
How the roadmap is shaped
This roadmap is not created in isolation. It comes from years of community feedback. Feature requests from users pushing the platform’s limits. Pain points surfaced by developers stretching the Lua engine. Ideas contributed by community members who understand the platform better than anyone.
The direction of Wapka is not determined by a single person. It emerges from the collective intelligence of everyone who builds on it.
Continue reading: Wapka: the complete platform review → The community story →