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

 

A small, nerdy premise.
If you notice a few nods to Ghostbusters (1984) along the way, that’s no coincidence.
WebWall v1.2 introduces three distinct roles that give structure and logic to its New Architecture:

– The Gatekeeper – stands at the door.
– Gozer the Destroyer – decides whether the structure holds.
– The Keymaster – maintains order and balance.

The naming is playful, yes—but the roles are very real, and each exists for a reason…

Originally, WebWall was a simple, efficient bouncer. It didn’t analyze or philosophize, it just worked:

“You: yes.”
“You: no.”

For a time, that simplicity was enough. Requests arrived, rules were checked, and anything suspicious stayed out. Fast. Clean. Predictable. But the web changes and today, abuse often isn’t a single bad request. It’s pressure over time. This is why, an important upgrade on WebWall Core was needed.

Blocking a request in 2026 is easy. Knowing when to stop forgiving is not.
That’s why v1.2 changes everything. WebWall now looks beyond the present: it observes patterns, behavior, and time. It remembers, but only just enough.

The Gatekeeper

The Gatekeeper lives in the request lifecycle. It sees everything but decides very little.

It does:

– Track visitors and update hit counters
– Apply lightweight scoring
– Enforce immediate blocks when thresholds are exceeded

It does not:

– Decide permanent bans
– Perform heavy logic
– Talk to external services

Think of it this way: the Gatekeeper keeps the door open, ensuring access control without unnecessary judgment. Most visitors will meet only him, and that’s perfectly fine.

Introducing Gozer

Gozer doesn’t run on every request. It doesn’t care about single hits: it cares about behavior.
Running asynchronously, Gozer looks at the bigger picture and “chooses the form of the Destroyer“:

– Accumulated scores
– Repeated abuse
– Pressure over time
– Decay of inactivity

It answers one question:

“Has this visitor earned consequences?”

There’s no machine learning, AI, or black-box guessing. No fingerprinting. No magic.
Gozer relies on transparent logic:

– Scores rise with bad behavior
– Decay rewards inactivity
– Escalation happens only if pressure persists

If a visitor stops, their score fades. If they insist, Gozer remembers. Persistence is expensive.
From the admin’s perspective, this process translates to:

– Pulse: active tracking
– Temporary blocks: suspicious behavior
– Blacklist (Burned): permanent bans
– Honeypot IPs: known hostiles

Behind the scenes? For esample:

– Score > 100+ = permanent local ban
– Continued activity = escalation
– Extreme abuse = Cloudflare-level block

At that point, the visitor never reaches the server again and the Gatekeeper doesn’t even see them.

The Keymaster

The Keymaster operates in the shadows, within the backend.
He maintains communication, synchronizes data, and keeps systems aligned.

His duties:

– Update the blacklist with bad IPs
– Maintain whitelists for trusted engines
– Check blacklists via lightning DNS
– Push escalation rules to Cloudflare instantly

Think of him as Gozer’s deputy, holding the keys that preserve balance and stability across layers.

A day in the life

When a domain goes live with WebWall v1.2, here’s what a typical 24-hour cycle might look like:

Hours 0–2:
Crawlers and scanners arrive. Scores stay low. The system observes silently.

Hours 3–6:
Aggressive probing begins. Temporary blocks appear.

Hours 6–12:
One IP keeps pushing. It crosses the line. Gozer burns it.

Hours 12–24:
Persistent hits trigger escalation. Cloudflare blocks them at the edge.
Within seconds……….silence: no manual action required.

No alerts. No babysitting. Just logic doing its job.
The separation of Gatekeeper, Gozer, and Keymaster isn’t cosmetic: it’s architectural.

• The fast path remains fast
• Heavy logic runs asynchronously
• Decisions grow smarter over time
• Updates adapt to new threats seamlessly
• The Gatekeeper says: “You may enter…”
• Gozer eventually says: “You shouldn’t have…”
• The Keymaster whispers: “I know you all…”

So, zero dependencies, zero drama
WebWall v1.2 runs wherever you drop it.

• No frameworks
• No external services
• SQLite for live state, MySQL for history
• Optional Cloudflare escalation

Setup is intentionally… boring, and that’s a compliment.
Final note? Yes, Gozer has a link. And yes, it points here:
https://ghostbusters.fandom.com/wiki/Gozer

Because being a little nerdy never hurt anyone, especially when the system just works-and this one does.
PS: There’s one more character worth mentioning, the funniest one, “Slimer“…and indeed, there is. He only does one thing besides making people smile: he tells Gozer who’s bothering him. And if he does…well, we already know what happens.

Discover WebWall 1.2
Try the Live Demo