Case Study
Plone 6 Classic
16/10/2025
Auditorio 1
en
Plone 6 Classic UI - A Success Story
SysAdmin
Developer
Decision-maker
Intermediate
Webcloud7 launched a new product called 7inOne, which uses Plone 6 Classic UI as a backend. The frontend is developed independently, either by a third party or in-house. Our first big customer went online in October 2024.

Details

The site receives an average of 500K to 1M hits per day, peaking at 2M, with approximately 100K to 350K API (Plone) requests every 24 hours. 300 users actively create content on the platform. The backend, API, and frontend all run behind Cloudflare, which handles caching, WAF, and more. In the meantime, four more customers are live, all running the same codebase, but with completely different configurations. The API handles approximately 2 million requests per day.

High performance is achieved primarily through Cloudflare and a somewhat sophisticated cache invalidation strategy triggered by content changes. It’s possible to cache 90% of all API requests and nearly 95% of frontend requests. Additionally, some recent REST API changes reduced the response time to 200ms to 250ms for the 95th percentile.

Tech Stack: Kubernetes, Docker, Plone 6.1.2, ZEO setup with encrypted longhorn volumes, Elasticsearch, Redis/python-rq, Keycloak, Grafana/Loki, CircleCI

On top of that, Webcloud7 builds various open source packages and currently unreleased features: SAML auth, CAS3 auth, Async collective.elasticsearch, Several widgets (JSONField, Opening hours, Maps), Internal task/review systems, general implementation to fetch external data via APIs, Subscribe/notification system, Versioning/WorkingCopy/Staging, Page builder, Trash bin

Further: Challenges/Lessons learned, Why “still” Plone, Why not Volto, Questions from Audience

Updated: Download slides

Video