Multisite, multilingual CMS, one Drupal for every site.

A content management platform, open source, covering the technical core, the design system foundations, editorial training, an accessibility and security baseline, and running the platform over time. The Discovery sets the scope, with what is included and what is optional.

Yes. We develop the platform with specifications written with you, tests and review on every change, and a person on the team who approves every release. In the editor AI proposes and the editorial team decides, with a record of who approved. Code, configuration and content stay yours and exportable.

We do not publish a price list, because the cost depends on how many sites, how many languages, how much content there is to migrate and how many integrations are needed. The difference from a licensed CMS is structural: there is no annual fee for the right to use the software. The Discovery gives you a phased roadmap with an order of magnitude for each phase.

Yes, for everything that is composing content: new pages, landing pages, campaigns, translations, updates. Developers come in for a new component or a new integration: your editors only wait when the platform itself has to be extended.

Yes, and it is the most common starting point. We start with a content inventory, decide what to migrate and what to archive, map URLs and redirects so rankings survive, then migrate in batches with verification. FiscoOggi migrated more than 42,000 items of content, 35,000 images and 2,700 media files with almost 600 authors at work.

Yes, it is built on Drupal. “Drupal CMS” is the Drupal project’s ready-to-use distribution, with a guided installation and preconfigured setups; Drupal is the platform underneath. We start from one or the other depending on the project: Drupal CMS shortens the start, Drupal gives more room when the content model is complex.

The stated starting point is WCAG 2.2 AA and EN 301 549: components are born accessible, so the level holds even when the person publishing has never read the guidelines. Delivery happens inside a perimeter certified to ISO/IEC 27001:2022, 27017:2015 and 27018:2025, with dated, downloadable certificates. On GDPR, NIS2 and DORA we have a dedicated guide for regulated sectors.

No. The AI suggests and a person approves, and the record shows who approved. Technically this means putting guardrails on agent actions: we maintain the guardrails module and the MCP client these projects run on, so we wrote the point where automation stops ourselves.

Through documented APIs, in both directions. The most common case is a PIM as the single source of product data: the CMS reads it, enriches it with editorial content and keeps serving pages even if the link goes down. The same applies to CRM, ERP, marketing automation, e-commerce and payment gateways.

We do, if you want: cloud native hosting, monitoring, updates, security and an agreed roadmap. Or your own team, with the documentation and the training. The code is open source, so the choice stays yours afterwards too. We have worked with Caleffi since 2013, and its previous site lasted ten years: that is the horizon we plan on.

It depends on how many channels you have to serve. If the website is the destination, a traditional architecture is simpler to run and faster to evolve. If the same content also has to reach apps, kiosks, e-paper or other front ends, decoupled makes sense. The platform supports both, so the choice stays open.

Because we build the platform ourselves. The founders have contributed to the open source project since 2008, SparkFabrik since 2015; we maintain public modules on drupal.org, and in May 2026 we became the first Drupal Certified Partner Gold in Italy. In practice that means direct access to the people who maintain the critical modules when something breaks, and first-hand knowledge of the roadmap, because we take part in the discussions where it is decided.