There are updates that refine a Product, and updates that redefine its direction. WebWall 2.1 belongs firmly to the second category.

With the “Stay Puft Edition“, WebWall evolves into a more structured, more capable, and more responsive security system. It remains fully standalone, written in pure PHP, and intentionally free from unnecessary dependencies, but its internal architecture has grown into something more ambitious. Multiple SQLite engines, a more refined buffering strategy, a stronger scoring model, and experimental edge enforcement all move in the same direction: giving WebWall more awareness, more precision, and more resilience under pressure.

If the Gozer Release introduced the idea of behavioral defense, the Stay Puft Edition turns that idea into a more mature and distributed security model.

A more distributed core

The most significant change in v2.1 is the move toward a multi-engine SQLite architecture, for short-term memory management; MySQL remains the fixed point for data storage, adhering to the timelines specified by the Administrator (GDPR Safe). Instead of concentrating every responsibility into a single database, WebWall now distributes its workload across dedicated nodes. Core manages configuration and identity. Pulse handles real-time traffic and buffering. Ane “Slimer” maintains bot intelligence and CIDR data. Vigo coordinates edge synchronization.

This is not only a technical improvement, but an architectural one. By separating responsibilities, WebWall reduces write contention, improves clarity, and makes each subsystem easier to evolve independently. The result is a system that remains lightweight, but is much better prepared to operate under sustained traffic and real-world pressure of the Website.

Gozer, now pressure-aware

“Gozer” has also been refined. In earlier versions, its strength came from behavior-based scoring and incident aggregation. In v2.1, it becomes even more aware of the environment around it by introducing a broader pressure model. Instead of looking only at isolated events, it now evaluates traffic volume, unique visitors, incident density, ban activity, and latency as part of a more complete picture of system stress. This matters because attacks are not always loud. Some arrive slowly, accumulating pressure over time until the system begins to feel the strain. By incorporating pressure into its decision-making process, “Gozer” can recognize not just malicious behavior, but the conditions that make malicious behavior more dangerous.

The addition of trend detection makes that logic even more useful. A system can react to what has already happened, but it is far more valuable when it can sense whether the situation is stabilizing, worsening, or moving toward a more serious escalation.

Edge protection, when it counts

The native Cloudflare integration also becomes more expressive in v2.1. WebWall continues to support IP List synchronization, but the Stay Puft Edition introduces an experimental layer built around Cloudflare D1 and Workers. This is a powerful option, but deliberately not a simple one. It is designed for users who understand the added complexity and want to push WebWall beyond origin-only protection. That is an important part of the WebWall philosophy. The system should be capable of reaching the edge when needed, but it should never force unnecessary complexity on those who do not want it. In other words, the edge is available as a weapon, not as a requirement.

A dashboard with more meaning

As the system grows, the dashboard grows with it. The enhanced interface does more than display counters: it gives the administrator a clearer sense of the system’s state, its pressure, and its behavior over time. Warnings, temporary jail, permanent bans, verified bots, honeypot activity, bot traffic, and edge-level blocking are now easier to interpret at a glance. That matters because a good security system should not only defend well; it should explain itself well. Visibility builds trust, and trust is essential when a system is making decisions on your behalf. WebWall’s dashboard is becoming not just a reporting surface, but an operational one.

Built for practical control

The new version 2.1 “Stay Puft Edition” does not try to be simple in a superficial way. It tries to remain controlled.

Every new feature has a purpose. Multi-engine storage exists to reduce contention and keep the system stable. Pressure analysis exists to improve behavioral judgment. Edge enforcement exists to stop threats earlier in the chain. None of these additions are there for spectacle alone. They are there because they help WebWall stay what it has always wanted to be: standalone, direct, practical, and just a little nerdy. That, in the end, is still the WebWall philosophy .

Moving forward

If the Gozer Release gave WebWall a stronger brain, the Stay Puft Edition gives it a better body, better sensors, and a much deeper awareness of what pressure really means.

It still watches. It still scores. It still blocks.
But now it does so with a more distributed architecture, a more nuanced view of behavior, and a clearer path to the edge when the situation demands it.

And yes, it still carries exactly the right amount of Ghostbusters in its DNA!

Discover WebWall – Live Demo
Buy Now WebWall v2.1 – Stay Puft Edition with 20% off limited offer

 

In today’s Market for Document Management Systems, there exists a subtle yet fundamental line separating simple File Sharing from Controlled Publishing. Teams often find themselves trapped by tools where collaboration sacrifices document integrity, or where authorial control is so rigid that it isolates content from the necessary feedback….

With the release of Dokky Suite v.2.1.0, we have introduced a dedicated Publisher System for every user, redefining the concepts of document ownership and lifecycle. It is not a shared “whiteboard-style” editor, but a true personal studio where the author retains total control over the creative process, from the initial draft to the final compilation.

Authorial Sovereignty: Ownership and Versioning
The heart of v.2.1.0 lies in the clear distinction between creation and discussion.
In Dokky, a document (whether an uploaded file or one generated within the Suite) belongs to its creator. Only the Author possesses the authority to access the version timeline, deciding which branch to edit and which to “freeze” as a definitive asset.

This approach guarantees the integrity of the work: the user runs no risk of having their draft altered by third parties. Instead, they can generate new instances of the document, allowing their writing, research, or reporting to evolve organically without ever losing sight of the starting point.

The Merge Engine
The true technical innovation of this release is the author’s ability to act as their own curator. Through the Merge function, users can select distinct sections or subsequent versions of their project and fuse them into a single, unified document.

Rather than merely performing a rudimentary binary file concatenation, Dokky executes a comprehensive regeneration of the source code and content for each selected version. The result is a cohesive work that includes:

• Dynamic Table of Contents (TOC): Automatic generation of the table of contents based on the order selected by the author.
• Stylistic Consistency: Application of professional templates (4 pre-filled options) that standardize the layout, headers, and footers across the various chapters.
• PDF/A-3b Certification: An output compliant with ISO 19005-3 standards, ensuring certifiable digital preservation.

A potential extension of this system?
Collaboration Without Compromise: Feedback via Private Groups.

While editing is a private, author-centric act, validation is a collective one. Once the author decides to share their work within a Private Group, Dokky activates an ecosystem of collaborative tools that do not alter the original text, but rather enrich it with added value:

• Inline Annotations: The team can add notes directly onto the PDF.
• Version-Specific Chat and Comments: Discussions remain focused-tied directly to the specific version of the document being reviewed.
• Integrated Assets: The ability to attach images, to-do lists, and structured feedback.

This creates a seamless workflow: the author writes and compiles independently, while the group reviews and offers suggestions. The author can then return to their “Publisher” interface to generate a subsequent version, strengthened by the feedback received.
Dokky v.2.1.0 does not impose a specific working method; instead, it provides an infrastructure. As is the case across the entire Suite, the Administrator can choose to activate the Publisher section only when necessary specifically, where document production demands high standards and forensic traceability.

In an era of ephemeral content and chaotic collaborations, Dokky restores dignity to the role of the author, providing the essential tools to transform simple information into professional, secure, and enduring publications. Let’s run through a quick case study, hypothesizing a possible scenario:

Imagine a financial advisor who needs to draft a complex market analysis.
1. He creates the various chapters as successive versions within his Publisher (inaccessible to others).
2. He uses the Merge feature to combine the chapters into a single, elegant PDF report featuring a verification QR code.
3. He shares it within a Private Group with partners or collaborators.
4. Other authorized users add to-dos and comments to the document thread, without being able to alter a single comma of the original analysis.

Result? Maximum professionalism, no accidental overwriting, total traceability.
Dokky Suite it is available for secure download on our Shop, with exclusive discounts! Or take a look at the Live Demo!

 

After months of development and intensive testing, we are happy to announce the arrival of WebWall® 2.0, the new version of our IDS/IPS designed to protect web applications and infrastructure in real time.

This release marks a major step in the evolution of WebWall: new dynamic scoring algorithms, an improved interface, deeper integrations with Cloudflare, and, above all, an increasingly autonomous and intelligent view of web security.

Among the key new features:

• Separation of the Cloudflare module (Vigo System) and automatic activation of “Under Attack Mode.”
• Optimized IP search with history, integrated whitelists, and full IP lookup.
• Translations in five languages ​​and new data export tools (TXT, CSV, PDF).
• Automatic email reporting system for administrators and partners.

But the news that makes us most proud is the choice of NWN Solutions, an Italian Web Agency, to adopt WebWall® 2.0 as the Official Security Solution for its Clients (a white-label solution), yet true to our name and philosophy.

Partnerships like this confirm our Mission: to provide simple, powerful, and easy to use defense tools that can adapt to the fast pace of the Modern Web.

WebWall continues to grow with and for the Community.

ScriptNet Solutions, proud producer of WebWall – Behavior-Driven Security Script