Wapka

Some users upload a profile picture. Others upload entire media streaming libraries. The file manager handles both — and everything in between. What it handles Small files: images, CSS, JavaScript, documents Large files: video, audio, archives, datasets Structured storage: organized by site, with access controls Public and private: configurable visibility per file or directory Direct linking: every file gets a permanent URL Backup: automated redundancy for managed cloud users The file manager is not an afterthought. It is one of the most-used features on the platform, and it has been battle-tested by users pushing it to extremes. ...

Hosting someone’s website is not like hosting a file. A website is someone’s creative work. Their business. Their community. Their years of effort. When they choose your platform, they are not choosing a service provider — they are choosing a steward. That is the part of platform building no one talks about. What trust demands Trust demands that data remains accessible. That sites from ten years ago still work. That users who built on one version of the platform are not abandoned when the next version ships. That the person running the platform understands the weight of what they are carrying. ...

One of the first things the Wapka community did — back in the feature phone era — was create themes. Neon-colored layouts. Scrolling marquees. Custom CSS that pushed tiny screens to their limits. It was creative, chaotic, and deeply personal. That tradition continues today. How theming works Wapka uses Twig templates for Lua-powered sites. Users can: Create templates from scratch with HTML, CSS, and Twig syntax Customize existing templates — colors, fonts, layouts Share templates with the community Apply templates to their site with one click Theming is not a walled garden. You have full access to the underlying code. The visual builder generates clean markup that you can style. Lua scripts can inject dynamic content into any Twig template. ...

Wix has a beautiful visual builder. You cannot write server-side code in it. Vercel lets you write any code you want. You cannot drag and drop a page layout. Wapka does both — and they work together. How they coexist The visual builder generates standard HTML and CSS. Every element you drag onto the canvas produces clean markup that you can inspect, modify, and extend. A Lua script can run alongside any visual builder page. The visual builder handles the layout. The Lua script handles the logic. If you never write a line of code, you have a functional site. If you do write code, you have a full-stack development environment. ...

Choosing a web platform is personal. It depends on what you are building, your technical skill, your budget, and how much control you want. This comparison is honest — including where Wapka is not the right choice. Wapka vs Wix Wix Wapka Visual builder Excellent Excellent Server-side code None Full Lua scripting engine Free tier Wix branding, limited storage 100GB storage, full features Open source No Yes — full codebase on GitHub Self-hosting Impossible Docker, one command Best for Simple business sites, portfolios Dynamic sites, apps, creators who want to grow Verdict: Wix wins for pure brochure sites with zero technical needs. Wapka wins when you want a visual builder now and the option to add custom backend logic later — without switching platforms. ...

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. ...

Ten years is a long time to work on one thing. Long enough to see trends rise and fall. Long enough to rebuild the same system three times. Long enough to learn that most advice about building products is wrong — not maliciously wrong, just too short-term to matter. Here is what actually sticks. Consistency over intensity The internet rewards intensity. Launch weeks. Viral moments. Growth hacks. But platforms are not built in bursts. They are built in thousands of small decisions made over years. ...

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. ...

For over five years, Wapka was completely free. No tiers. No limits. No credit card required. I funded it personally — savings, platform ad revenue, and contributions from community members who believed in the mission. That worked until it didn’t. The tipping point When your user base grows past a certain threshold, so do your costs. Storage is the big one. Users hosting media streaming sites. Users uploading terabytes of files. Bandwidth bills that compound monthly. ...

Open-sourcing a platform you have spent years building is not the obvious move. Most platforms keep their code private. It is their competitive advantage. Their moat. I believe the opposite. I believe the moat is trust — and you cannot build trust behind a closed door. The decision The decision to open-source Wapka came from a simple question: if I disappear tomorrow, do the people who trusted this platform lose everything? ...