Choosing the right CMS has a direct impact on website performance, security, scalability, and the overall experience of creators and developers. In this article we compare two related systems: FlatlyPage CMS, the original solution created by our team, and AxElitus CMS, a fork based on FlatlyPage CMS that has been developed in a different technological direction.
Both systems follow a similar philosophy. They are lightweight, block based CMS platforms that do not require a database. However, they differ in their approach to caching, rendering, and hosting requirements.
FlatlyPage CMS vs AxElitus CMS
FlatlyPage CMS approach
FlatlyPage CMS was designed as a modern, lightweight, and efficient system for all users, ranging from individual creators to larger companies. Its architecture focuses on a powerful Renderion v3 engine, built in security protections against various types of attacks, good compatibility with different hosting environments, and predictable behavior even in more complex projects.
FlatlyPage CMS is not a system meant only for small websites. Thanks to Renderion v3 and its optimized structure, it can handle both simple personal sites and medium sized business websites with more advanced content and structure.
FlatlyPage CMS is not a system meant only for small websites. Thanks to Renderion v3 and its optimized structure, it can handle both simple personal sites and medium sized business websites with more advanced content and structure.
AxElitus CMS approach
AxElitus CMS was created as a fork of FlatlyPage CMS but moved in a different technical direction, primarily focusing on minimizing server resource usage. The system generates cache as static HTML files that remain valid for one hour. It is more aggressively optimized for low cost or free hosting environments and offers less dynamic flexibility compared to FlatlyPage CMS. Because of this approach, there is also a higher risk of potential bugs or limitations in certain use cases.
This means that AxElitus CMS can sometimes be faster on weaker servers, but at the same time it is less suitable for projects that require more advanced dynamic functionality.
This means that AxElitus CMS can sometimes be faster on weaker servers, but at the same time it is less suitable for projects that require more advanced dynamic functionality.
Renderion v3 vs Renderion BlocX
FlatlyPage CMS is built on the original Renderion v3 engine, which was designed by WebOrbiton as a lightweight, secure, and efficient content rendering system. Instead of rendering an entire page at once, Renderion v3 processes only the blocks that are actually used on a given page. This makes the system fast, predictable, and easier to maintain. The engine includes protection against XSS attacks, safeguards against cache poisoning, and strict data validation before rendering. In practice, this means that FlatlyPage CMS delivers strong performance while maintaining a high level of security against common web threats.
AxElitus CMS uses a modified version of Renderion v3 called Renderion BlocX. Although it is based on the same core concept, it has been adapted to prioritize aggressive caching and static page generation. Renderion BlocX focuses more on minimizing server load and achieving maximum speed even on very limited hosting. It does this by frequently storing fully rendered pages as static HTML files, reducing the number of operations needed for each visitor. While this improves performance on weaker servers, it also reduces the flexibility that the original Renderion v3 provides in FlatlyPage CMS. Additionally, in AxElitus CMS content updates may take up to one hour to become visible, while in FlatlyPage CMS changes can typically be reflected within minutes.
Both engines share the same roots but have different priorities. Renderion v3 in FlatlyPage CMS balances speed, security, and flexibility, while Renderion BlocX in AxElitus CMS prioritizes maximum performance and minimal server usage.
AxElitus CMS uses a modified version of Renderion v3 called Renderion BlocX. Although it is based on the same core concept, it has been adapted to prioritize aggressive caching and static page generation. Renderion BlocX focuses more on minimizing server load and achieving maximum speed even on very limited hosting. It does this by frequently storing fully rendered pages as static HTML files, reducing the number of operations needed for each visitor. While this improves performance on weaker servers, it also reduces the flexibility that the original Renderion v3 provides in FlatlyPage CMS. Additionally, in AxElitus CMS content updates may take up to one hour to become visible, while in FlatlyPage CMS changes can typically be reflected within minutes.
Both engines share the same roots but have different priorities. Renderion v3 in FlatlyPage CMS balances speed, security, and flexibility, while Renderion BlocX in AxElitus CMS prioritizes maximum performance and minimal server usage.
Authors and project ecosystem
FlatlyPage CMS is owned by WebOrbiton and forms a key part of the WebOrbiton Suite, a collection of lightweight, self hosted web tools designed primarily for shared hosting environments. The goal of WebOrbiton is to provide simple, efficient, and privacy friendly solutions that do not require heavy server infrastructure or databases while still being fully functional for creators, developers, and businesses.
Within the WebOrbiton Suite, FlatlyPage CMS is accompanied by other complementary projects. WebOrbiton Monitor provides real time website and service monitoring without relying on a database. PriviMetrics offers a privacy focused, cookieless analytics solution that can run on standard shared hosting, setting it apart from traditional tracking platforms. OrbitioDocs is a lightweight documentation system with a WYSIWYG editor designed for technical and product documentation. The foundation of many of these tools is the Renderion Engine, a custom rendering system responsible for fast and modular content generation across the WebOrbiton ecosystem.
WebOrbiton is led by Igor Oprządek, the owner and main project leader. Development work is carried out by Szymon Lipski, who contributes to technical implementation, and Wiktoria Kowal, who works on both programming and translations. The WebOrbiton infrastructure is hosted on Hostinger, ensuring stable and professional service operation.
In contrast, AxElitus CMS is led by Michał Jakubiński together with a community of contributors. It is not part of the WebOrbiton Suite and is not organizationally or legally connected to WebOrbiton. Its infrastructure currently runs on InfinityFree, a free hosting platform, which reflects a different approach to costs and project scale.
Within the WebOrbiton Suite, FlatlyPage CMS is accompanied by other complementary projects. WebOrbiton Monitor provides real time website and service monitoring without relying on a database. PriviMetrics offers a privacy focused, cookieless analytics solution that can run on standard shared hosting, setting it apart from traditional tracking platforms. OrbitioDocs is a lightweight documentation system with a WYSIWYG editor designed for technical and product documentation. The foundation of many of these tools is the Renderion Engine, a custom rendering system responsible for fast and modular content generation across the WebOrbiton ecosystem.
WebOrbiton is led by Igor Oprządek, the owner and main project leader. Development work is carried out by Szymon Lipski, who contributes to technical implementation, and Wiktoria Kowal, who works on both programming and translations. The WebOrbiton infrastructure is hosted on Hostinger, ensuring stable and professional service operation.
In contrast, AxElitus CMS is led by Michał Jakubiński together with a community of contributors. It is not part of the WebOrbiton Suite and is not organizationally or legally connected to WebOrbiton. Its infrastructure currently runs on InfinityFree, a free hosting platform, which reflects a different approach to costs and project scale.