Kreare: Google Cloud infrastructure and system administration for a web agency
Client:Kreare (Riccione, Italy)Year:2023

- Google Cloud
- Linux
- Nginx
- MySQL
Kreare is a marketing and web communication agency in Riccione: it handles e-commerce, websites, social media and digital strategy for its own clients. An agency needs to focus on projects, not on managing servers.
init.d is their behind-the-scenes systems partner:
- Design and management of the infrastructure on Google Cloud.
- Configuration and tuning of Linux servers and Nginx web servers.
- Security, TLS certificates and tested backups.
- Monitoring and ongoing system administration, with on-call availability on request.
What does a white-label systems partner do for a web agency?
It takes care of the servers that run the agency's projects, while staying behind the scenes. The agency keeps the relationship with its clients, the design, the graphics and the development; the systems partner designs the infrastructure, keeps it updated and secure, and steps in when needed. For end clients the point of contact remains the agency, which can rely on specialised system administration skills without having to build them in-house. The model works when roles are clear: who opens requests, who takes them on, with what timing and on which systems. That is why we set it up with written procedures and defined contact channels, so every request follows a traceable path.
How do you organise infrastructure that hosts many clients' sites?
By separating projects so that each one has its own resources, access and configuration. In the setup we normally use, on a Linux server with Nginx each site has its own configuration block, its own system user and, for PHP, its own process pool; each MySQL database has a dedicated user with permissions limited to that database alone. This way a problem on one site stays confined to that site, and resources can be assigned according to each one's needs. On Google Cloud, projects, labels and network rules keep environments and costs in order, and allow spending to be attributed to individual projects when needed. Everything is described in documented configurations, not in steps remembered by heart.
How do you handle security and backups across many sites?
With the same procedures for all of them, automated where possible and checked regularly. TLS certificates renew automatically and are monitored to avoid unexpected expiries; security updates for the operating system and services are applied on a known schedule; server access goes through personal keys and permissions are kept to the minimum needed. Backups only make sense if they can be restored, so we verify them with periodic restore tests. Monitoring checks resources, reachability and expiry dates, so many problems are spotted before they reach the agency's clients. We go into detail on the server security page.
When is out-of-hours on-call cover needed?
When the managed projects include services that must stay up in the evening and at weekends, such as e-commerce sites. Ordinary cover follows office hours; for real emergencies, meaning a site down, data loss or a security incident, an on-call plan can be added on the systems we manage. For an agency it is a way to offer its own clients broader cover, enabling it only on the projects that really need it.
Kreare delivers projects to its clients with solid infrastructure behind them, managed by a dedicated systems partner. It's the white-label model we offer to web agencies.