Prevention
Regular checks help identify issues before they cause outages or malfunctions.
TECHNICAL CARE
Website care plans
Ongoing technical care to keep your website stable, up to date and working over time.
LONG-TERM CONTINUITY
Technical care with clear priorities
Continuity
Updates, checks and maintenance are handled at a defined frequency.
Priority
Requests included in a plan take priority over occasional interventions.
CARE AREAS
Technical continuity shaped around your website architecture
The activities actually included depend on the selected plan and the project’s technical setup.
Priority technical support
Assessment of anomalies, errors and malfunctions based on priority and complexity.
Small website updates
Text, images, links, CTAs and minor corrections to existing components.
Performance checks
Periodic checks of loading and website behaviour.
Website monitoring
Availability, SSL, domain and key forms, according to the plan.
Technical updates
Framework, dependencies, CMS and configuration updates compatible with the architecture.
Backups and versioning where supported by the architecture
Repository, CMS, database, content or configuration only when present and accessible.
Activity reports
A summary of checks and interventions at the frequency defined by the plan.
Advanced features and integrations
APIs, external services, automations and critical components when included in the agreed plan.
CARE PLANS
Three levels for different project needs
Essential for stable websites, Premium for more involved sites, and Custom for complex systems.
Technical continuity for stable websites
Essential Care
For brochure sites, blogs and custom projects with a stable architecture and occasional support needs.
Quarterly billing
€69per month
€207 per quarter
Annual billing
€59per month
€708 per year
Annual saving: €120
Includes
- 24/7 uptime monitoringAutomated monitoring; this is not 24/7 human support.
- Periodic website checks
- Checks of key forms
- SSL and domain checks
- Compatible technical updates
- Build and deployment checks
- Versioning and backups where supported by the architecture
- Core performance checks
- Quarterly report
- Up to 60 minutes of small updates per quarter
- 15% off additional work
Limits and terms
- Does not include new pages, features, redesigns, integrations, migrations or structural changes.
- Additional work can be quoted separately.
Ongoing technical care for more involved websites
Premium Care
For multilingual websites, e-commerce projects and digital products with CMSs, APIs, automations or integrations that require more frequent checks and ongoing technical management.
Quarterly billing
€149per month
€447 per quarter
Annual billing
€129per month
€1,548 per year
Annual saving: €240
Includes
- Everything in Essential Care
- Existing APIs and integrations
- More frequent checks on critical features, flows, forms and automationsFor e-commerce: checks of existing catalogue, product, variant, cart and checkout flows. New features, custom checkout, complex automations, redesigns and migrations are scoped separately.
- CMS / headless CMS, when present
- More frequent performance checks
- More frequent backups where supported by the architecture
- Staging / preview deployments when available
- Monthly report
- Priority technical support
- Up to 2 hours of interventions per month
- 20% off additional work
Using the included time
Unused hours do not roll over to the next month.
Includes
- Small frontend updates
- CMS updates
- Form corrections
- Existing automations and integrations
- Corrections to the current architecture
Limits and terms
- New features or integrations
- Redesigns or migrations
- Major refactoring
- Structural product development
Technical care for complex systems
Custom Care
For complex or business-critical systems, such as e-commerce projects with custom architectures or critical dependencies, booking systems, dashboards, private areas and web apps.
Plan defined after a preliminary review
Request a free preliminary reviewThe preliminary review considers
The free preliminary review helps identify the architecture, critical components and level of ongoing technical care needed to define the plan.
- Stack and hosting
- CMS and databases
- APIs and external services
- Authentication and infrastructure
- Risks and check frequency
- Projects developed in-house or by third parties
If defining the plan requires a deeper technical assessment of the project, it will be proposed separately before the project is taken on.
Possible areas to configure
- Initial technical assessment
- Monitoring of critical components
- APIs, databases and integrations
- Authentication and private areas
- CMSs and external services
- Booking, checkout and automations
- Build, deployment and staging
- Backup strategy
- Performance and application issues
- Technical reports
- Project-specific priority support
Activities are configured in the plan and are not automatically all included.
Ongoing care for the existing architecture
New features, integrations, redesigns, structural refactoring and ongoing product development are scoped separately.
Projects built by other developers
I can also take over projects built by other professionals after a preliminary compatibility check. Taking over the project is confirmed after this review.
THE PROCESS
How to activate a care plan
- 01
Review
I check the architecture, stack, hosting and project needs.
- 02
Plan
We define the care level, frequency and included activities.
- 03
Setup
I configure monitoring, access and the required tools.
- 04
Ongoing care
Checks, interventions and reports follow the agreed schedule.
SERVICE SCOPE
What maintenance covers
Includes
Plans cover checks, updates and small interventions on the existing architecture.
Limits and terms
New features, complex new pages, redesigns, integrations and structural changes are assessed separately.
FAQ
Frequently asked questions
What is included in small interventions?
Depending on the plan, they may cover edits to text, images, links and CTAs, as well as minor corrections to existing components. They do not include new pages or structural changes.
What happens if I exceed the included time?
Work beyond the time included in your plan is assessed and quoted separately before it begins.
Do unused hours roll over?
No. Essential’s 60 minutes and Premium’s 2 hours apply to their respective period and do not roll over.
Does maintenance include new features?
No. New features, integrations, redesigns, migrations, major refactoring and structural product development are scoped separately.
Can I use the plan for a site built by someone else?
Yes, after a free preliminary compatibility and scope check. If a deeper review of the code or infrastructure is needed, it is proposed separately before taking on the project.
How does the preliminary review for Custom Care work?
It is free and helps identify the architecture, critical areas and level of ongoing care needed; it does not include a full technical audit. If defining the plan requires a deeper review of the code or infrastructure, it is proposed separately.
Is the service suitable for WordPress?
It can cover projects using WordPress as a CMS or headless CMS when they fit the plan. Traditional WordPress sites are assessed individually.
How long is the subscription?
Essential and Premium offer the quarterly and annual billing options shown in their plans. Custom Care terms are defined after the preliminary review and, when needed, a separate in-depth technical assessment.
Can I change plans?
The plan can be reviewed if the architecture, complexity or technical needs change. Updated terms are agreed before taking effect.
Are hosting, licences and external services included?
Hosting, domains, premium plugins, SaaS, paid APIs and other external services are not automatically included in the plan fee. Their costs remain separate unless agreed otherwise.
Will I receive a report?
Yes. Essential includes a quarterly report and Premium a monthly report. Custom Care reporting frequency is defined in the plan.
TECHNICAL CARE
Not sure which plan is right?
We can start with your project architecture and the level of technical continuity you actually need.