What's under the hood, explained plainly
The technical choices behind every project: architecture, network, security, performance and continuity over time.
Static by default, dynamic by necessity
Public pages are generated before the visit, not on every request. The server has nothing to compute: it hands over a file that is already ready.
- Generated in advance
- On every change the project is rebuilt into HTML pages, CSS and optimised images. No database is queried while people browse.
- No attack surface
- With no public admin panel, plugins or exposed databases, the vulnerabilities typical of traditional CMSs simply do not exist.
- Isolated logic
- Forms, payments, private areas and management software run as separate, dedicated services, switched on only where they are needed.
- Editable content
- When the client needs to update copy and products on their own, we connect a content management panel kept separate from the public site.
Every release, tracked and reversible
Versioning
All code is stored with a complete history of changes.
Build
Automated build, with images, scripts and styles optimised.
Preview
Every change can be seen on a staging environment before it goes live.
Deployment
Published to the global network in seconds, with no downtime.
Static part
The core of every project: everything that is public and the same for everyone.
- Pages, product pages, articles
- Images resized and in modern formats
- Delivered from the cache nearest the visitor
- Roll back to the previous version in one click
Dynamic part, on demand
Only where the project really calls for it, to the same security standards.
- Functions run at the edge of the network
- Dedicated APIs for management software and web apps
- Databases with role-based access
- Integrations with payments, CRM and ERP
A global network in front of every project
We publish on Cloudflare: content is replicated across the network's data centres and served from the point nearest each visitor.
Distributed cache
Pages are already copied close to visitors, in Italy and abroad alike.
HTTP/2 and HTTP/3
Faster, more stable connections, on mobile networks too.
Brotli and Gzip
Lighter files, transferred in less time.
Managed DNS
Fast domain resolution, protected against tampering.
Edge computing
Dynamic logic runs close to the user, not on a distant server.
No practical limit
A campaign or a launch will not bring the site to its knees.
Layered protection, from the edge to the data
Traffic filtering
DDoS mitigation, a web application firewall (WAF) and malicious bots blocked before they reach the project.
Encrypted connection
HTTPS enforced with TLS 1.3, certificates renewed automatically, HSTS on.
Defensive code
Security headers, Content Security Policy, validation of every input.
Least privilege
No exposed databases, role-based permissions, regular backups and GDPR-compliant processing.
Measured, not promised
We design every page to stay within the “good” thresholds of the Core Web Vitals, the metrics Google uses to assess real users' experience.
Time for the main content to appear.
How quickly the page responds to clicks and taps.
Visual stability: nothing jumps around while the page loads.
Reference thresholds published by Google for the Core Web Vitals. Actual values depend on each project's content and are checked before delivery.
The same foundation, different tools
The architecture changes with what the project has to do, never the other way round.
- Fully static, multilingual too
- Optional, separate content management
- Spam-protected contact forms
- Technical SEO and structured data
- Static catalogue, dynamic cart and checkout
- Payments through certified gateways
- Sync with stock and management software
- Dedicated B2B price lists and terms
- Authenticated, role-based access
- Dedicated database with automatic backups
- Custom workflows: orders, quotes, shifts
- Custom exports and reports
- Online services for end customers
- Usable on desktop and smartphone
- APIs to connect to other systems
- Architecture ready to grow with use
After launch, the project is still looked after
- Client portal
- Project status in real time, tracked tickets and a history of documents and deliverables, all behind one login.
- Monitoring
- Continuous uptime and performance checks, with an immediate alert if anything goes wrong.
- Updates
- Dependencies and components kept up to date, without interrupting the service.
- Recovery
- Every published version is kept: rolling back takes a few seconds.
The questions we are asked most often
Yes. If the project includes it, we connect a simple management panel: you edit copy, images and products and the site updates automatically.
No: “static” is about how pages are delivered, not about what they can do. Animations, forms, search and private areas are all possible.
Pages are served by the global network, which absorbs peaks with no slowdown and no unexpected costs.
The domain, content and data stay yours. On request we hand over the source code and documentation.
In most cases, yes: management software, CRM, ERP and payment platforms connect through APIs or dedicated exports.
Let's talk about your project
Tell us what you need: we will propose the best-fitting architecture, without needless jargon.