Standard
For a company website that needs ongoing technical care and occasional minor changes.
PLN 700
net per year · billed annually
- Full technical maintenance
- 3 hours of changes per year
- Extra website work: PLN 100 net/h
Hosting in expert hands.
Managed hosting for websites and applications.We look after availability, security, updates and backups.We help with content, media and minor website changes.
Compare plansChoose your level of care.
From a company website to an application your team relies on.Choose the change allowance, support priority and environment your business needs.
Business
For a business-critical website: priority incident support and 3 hours of changes per month.
from PLN 700
net per month · billed monthly
- Full maintenance and priority
- 3 hours of changes per month
- Response within 30 min during office hours if the application is down
Bespoke
For applications and resources with dependencies that require a purpose-built environment.
Setup + care
setup and ongoing maintenance quoted separately
- Architecture suited to the application
- Resources and access defined in the design
- A tailored maintenance scope
VAT is added to the prices shown.
Ongoing care for your website.
Technical maintenance is included in every plan.Your change allowance covers content, media and minor website adjustments.
Monitoring and incident support
You do not have to keep checking your website.
We monitor website availability, service health and resource usage. We handle alerts, diagnose faults and restore service within the agreed maintenance scope.
Security and updates
We look after your website’s security.
We manage Imunify360, traffic filtering and malware scans. Updates follow application requirements and agreed maintenance windows.
Backups and recovery
We help restore an earlier working state.
We keep backups of your website and data separate from its hosting environment. We restore them when needed within the agreed maintenance scope.
Help with website changes
Your content does not have to wait.
We publish copy, images and media, and make minor adjustments. These use your change allowance; new functionality is quoted separately.
Compare what is included.
A shared maintenance foundation, with different ways of working together.We agree the details around your application and its role in your business.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Billing | PLN 700 net per year | from PLN 700 net per month | Setup and ongoing care |
| Change allowance | 3 h / subscription year | 3 h / month | As agreed for the engagement |
| Support priority | Standard | Business | Based on the environment |
Environment and performance
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| What we maintain | A website | A website or application | A website or application with bespoke requirements |
| Compute resources | Shared CPU and RAM sized for the website | CPU and RAM sized for the application workload | CPU and RAM specified in the environment design |
| Storage | Capacity agreed before onboarding | Capacity suited to the service | Capacity and growth defined in the design |
| Performance | Configuration and ongoing tuning | Ongoing service performance monitoring | Tuning across the environment |
| Test environments | Agreed before onboarding | Based on the change process | Defined in the architecture |
Security and updates
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Web traffic protection | Web application firewall (WAF) in Imunify360 | Web application firewall (WAF) in Imunify360 | Protection suited to the application |
| Malware protection | Scanning and protection in Imunify360 | Scanning and protection in Imunify360 | Controls suited to the application |
| Updates | Compatible security and feature updates | Compatible security and feature updates | Based on environment dependencies |
| WordPress security | Security configuration and maintenance | Security configuration and maintenance | Where WordPress is part of the environment |
| Checking WordPress updates | Pre-release testing within the agreed scope | Pre-release testing within the agreed scope | Testing process suited to the application |
| SSL/TLS certificates | Managed within the hosting scope | Managed within the hosting scope | Within the agreed scope |
Routine updates compatible with the agreed environment are included in the service. Application redevelopment or work on unsupported dependencies is quoted after assessment. A new version number alone does not mean an additional charge.
Backups and recovery
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Backup schedule | Daily incremental backup; full backup once a week | Daily incremental backup; full backup once a week | An individually agreed schedule |
| Backup storage | Separate from the website environment | Separate from the website environment | As set out in the backup plan |
| Backup history | The latest 4 weekly full backups and related incremental backups | The latest 4 weekly full backups and related incremental backups | An individually agreed retention period |
| Website and data recovery | Within the agreed maintenance scope | Priority recovery within the agreed maintenance scope | Under the recovery plan |
| Recovery arrangements | Agreed before maintenance begins | Recovery objectives agreed for the service | Objectives and verification agreed in the project |
Website changes and development
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Content and media | Within 3 h per year | Within 3 h per month | Within the agreed scope |
| Technical maintenance | Included; does not use change hours | Included; does not use change hours | Included in the agreed maintenance scope |
| Additional website work | PLN 100 net/h | PLN 100 net/h | PLN 100 net/h |
| New features and redesigns | Quoted separately | Quoted separately | A separate project scope |
| Using the allowance | Resets at the subscription year end | Resets monthly; no rollover | As agreed in the scope of work |
| Testing and publishing changes | Testing scope and publication arrangements agreed before work begins | A testing, release and rollback process | A release process agreed for the application |
Technical maintenance, monitoring, compatible updates and incident handling within the agreed scope do not use your change allowance. Fixing an error introduced by our own change does not use your allowance either.
Contact and response arrangements
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Working relationship | Ongoing care and occasional changes | Regular collaboration and priority | Environment design and maintenance |
| Incident response | Within 4 working hours: critical incident | Within 30 min during office hours if the application is down | Under the agreed service level |
| Operator availability | Standard working hours | Mon–Fri 09:00–17:00 (Warsaw) | As agreed for the engagement |
| Outside working hours | Subject to availability and agreed windows | Priority handling; no fixed response time | As agreed for the engagement |
| Monitoring | Around-the-clock automated monitoring | Around-the-clock automated monitoring | Coverage suited to the environment |
Response time means starting to handle the incident, not completing the repair. The clock starts with a monitoring alert or a report through the agreed channel. Office hours are Monday to Friday, 09:00–17:00 Warsaw time, excluding Polish public holidays.
We acknowledge routine requests by the next working day and agree a delivery date separately. Out-of-hours support is shown in the table above.
How we start working together
We first assess the website and its dependencies. Resolving an existing infection or fault is quoted separately. Ongoing maintenance starts from an agreed, stable baseline.
Before work begins, we agree responsibilities, required resources, contact arrangements and onboarding costs. The service terms also record recovery requirements and any additional licences or work.
Billing and ending the service
Monthly subscriptions with an onboarding fee have a one-month notice period. The option without an onboarding fee has a three-month notice period. We agree the scope of onboarding before the service begins.
Annual plans are paid for one year in advance. Renewal terms and the settlement of early termination are set out in the agreement before the service starts.
When the service ends, we hand over the files, database, code you own, configuration and start-up instructions. One plan covers the accepted environment and its components; we do not charge for the same database or machine again under a second subscription.
Costs for domains and paid licences outside the plan are agreed separately. Existing customers retain their individually agreed terms.
Storage and service growth
Storage is sized for the service. Typical data growth is handled within the accepted profile without small surcharges for each additional gigabyte. Significant expansion is agreed before any change.
A new, independently maintained website, shop or service is quoted separately, including its care and any licences. A domain alias or working test copy does not automatically mean another subscription.
Business includes a larger resource budget and broader oversight suited to the company’s operations. More storage or traffic does not require a different level of care; resource expansion is agreed separately.
Taking over care.
- 01
Environment review
We review the application, its condition and dependencies. We identify any work needed before taking over maintenance.
- 02
Scope of care
We choose the plan, maintenance scope and contact arrangements. We agree costs, support hours and how requests are handled.
- 03
Handover plan
We agree access, the sequence of work and acceptance checks. For migrations, we prepare a cutover and rollback plan.