From €100 / month
Managed website
For a standard site: hosting and routine technical maintenance after reviewing the installation. Migration, licences and out-of-scope work are quoted separately.
Managed hosting and deployment
Continuous responsibility from infrastructure to application
Environments designed and operated around the actual needs of each application, with one accountable partner able to work across the system, deployment and software.
Services
A public starting point, followed by a defined scope
Pricing depends on criticality, traffic, dependencies and the required operating model. A technical review establishes what is included before responsibility is transferred.
Custom quote
Managed business platform
Drupal, CiviCRM, portals and ERP-like applications: architecture, deployment, operations and dependencies brought into one explicit scope of responsibility.
Custom quote
Complementary application services
Managed Typesense, n8n, Mattermost and other compatible software can be deployed when their purpose, data and maintenance lifecycle are clearly defined.
Technical foundation
Practical, maintainable choices fitted to the application
Technology is not sold for its own sake. It is used to reduce opaque dependencies and retain an operating chain that can be diagnosed.
System
RHEL and compatible distributions
RHEL and systems from the same ecosystem provide a stable Linux foundation, with maintained updates and access aligned with actual responsibilities.
Web
OpenLiteSpeed and caching
OpenLiteSpeed and appropriate caching mechanisms can accelerate website delivery, with a PHP stack and settings tailored to each application.
Isolation
Rootless Podman
Containerised services without unnecessary privileges when that separation materially improves deployment and maintenance.
Operations
Observe and recover
Logs, monitoring, backups and recovery paths are defined for the service instead of being assumed through a generic package.
Application protection
WAF solutions
Deployment and tuning of web application firewalls suited to exposed services, with rule and false-positive monitoring.
Service scope
What must be explicit before production
A serious service is not reduced to storage capacity or an abstract availability claim. Responsibilities and limitations are established for each environment.
01
Scope
Applications, versions, dependencies, volumes, access and included work are inventoried before responsibility is transferred.
02
Continuity
Backup frequency, retention, checks and recovery objectives are matched to actual criticality.
03
Access and maintenance
Permissions, secrets, update windows, alerts and out-of-scope work remain identifiable.
04
Reversibility
Data, code, documented configuration and exit arrangements must not become a means of lock-in.
First conversation
Start with the application and its criticality
An existing website, a CiviCRM platform or a complementary service is enough to establish an initial technical and commercial scope.