Standard
For a simple store that needs ongoing care and occasional product and content changes.
net / year · billed annually
- Store hosting and maintenance
- 3 hours of changes per year
- Extra website work: PLN 100 net/h
Managed hosting for your online store.We look after the environment, security and reliable store operation.One point of contact for updates, backups and support.
Compare plansFrom a simple store to an environment critical to sales.Choose the maintenance scope, change frequency and support priority.
For a simple store that needs ongoing care and occasional product and content changes.
net / year · billed annually
For a store that sales depend on: regular purchase tests, integration oversight and priority support.
net / month · billed monthly
For a store whose architecture and integrations require a purpose-built environment.
setup and ongoing maintenance quoted separately
You can buy additional change hours at PLN 100 net/h. Technical maintenance remains included in the subscription.
Hosting and technical maintenance are included in every plan.Use your change hours for products, content and minor adjustments.
You do not have to keep checking your store.
We monitor store availability, services and resources. We diagnose incidents and restore agreed cart, order, payment and shipping functions.
We look after your store’s security.
We manage store security and updates. We check compatibility and agreed cart, order, payment and shipping functions following changes to the store.
We help restore your store and its data.
We store backups separately from the store environment. We agree recovery steps that account for new orders and payments recorded since the backup.
We help keep products and content up to date.
We use your included hours for products, content and minor store changes. New features and integrations are quoted separately before work begins.
The same maintenance foundation, different levels of cooperation.Compare store support, purchase tests and contact arrangements.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Billing | from PLN 1800 net / year | from PLN 1200 net / month | Project and ongoing care |
| Change allowance | 3 h / subscription year | 3 h / subscription month | As agreed for the engagement |
| Technical maintenance | Hosting and care included | Hosting and care included | Scope defined in the project |
| Level of cooperation | A stable store and occasional changes | Regular checks and priority | Defined in the project |
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Maintenance scope | An online store | A store with integrations | A store and related systems defined in the project |
| Hosting and administration | Included in the subscription | Included in the subscription | Within the agreed scope |
| Compute resources | Sized for the workload | Sized for the workload | CPU and RAM specified in the design |
| Storage | Capacity suited to requirements | Capacity suited to requirements | Capacity and growth defined in the design |
| Optimisation | Application and cache configuration | Performance and background task monitoring | Tuning across the environment |
| Traffic peaks | Resource expansion by agreement | Campaign and capacity planning | Architecture sized for the workload |
| 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 technology |
| Malicious code | Scanning and protection in Imunify360 | Scanning and protection in Imunify360 | Controls suited to the application |
| Store updates | Store platform, supported modules and theme | Store platform, supported modules and theme | Based on dependencies and the change plan |
| Change checks | Backup and tests suited to the update | Staging and an extended test checklist | Process suited to the architecture |
| Post-deployment test | Cart, order, payment and shipping | Purchase journeys and agreed integrations | Acceptance criteria defined in the project |
| SSL/TLS certificates | Managed within the hosting scope | Managed within the hosting scope | Based on architecture and certificates |
Routine security and functional updates compatible with the accepted environment are included in care. A migration requiring a rebuild or repair of unsupported dependencies is quoted after assessment; a new version number alone does not trigger an additional charge.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Cart and orders | Maintenance of the accepted configuration | Maintenance of the agreed process | Functional scope defined in the project |
| Regular purchase tests | After our changes that affect purchases | Scheduled tests of the agreed journey | Tests based on environment scenarios |
| Payments and shipping | Diagnosis of issues in accepted modules | Connection oversight | Responsibility defined per integration |
| ERP and marketplaces | Scope agreed before onboarding | Care for the agreed integration list | An individually designed data exchange process |
| External service failures | Diagnosis and contact within scope | Priority diagnosis and coordination | Procedures based on dependencies |
| A new feature or integration | Separate quote and approval | Separate quote and approval | Project scope and acceptance |
Every plan includes purchase checks after our changes that affect sales. Business also includes scheduled purchase tests and oversight of agreed integrations. We agree the scenarios and test frequency before ongoing care begins.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Application backups | Daily incremental backup; full backup once a week | Daily incremental backup; full backup once a week | Based on the environment backup plan |
| Order database backups | Based on the backup plan | Frequency suited to order activity | Frequency and scope defined in the project |
| Backup storage | Separate from the store environment | Separate from the store environment | Based on the data protection design |
| Backup history | The latest four weekly full backups and related incremental backups | The latest four weekly full backups and related incremental backups | Retention defined in the design |
| Store and data recovery | Within the accepted care scope | Priority recovery within the agreed scope | According to the recovery plan |
| Recovery targets (RPO/RTO) | Scope confirmed before onboarding | Agreed for the specific store | Objectives and tests defined in the project |
We agree the recovery method with new orders and payments in mind. Before onboarding, we check the recovery path; rolling back the entire database alone could erase new transactions.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Products, content and media | Within 3 h per year | Within 3 h per month | As agreed for the engagement |
| Technical maintenance | Included, outside the change allowance | Included, outside the change allowance | Included in the agreed care scope |
| Additional web 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 |
| Validity of hours | Until the end of the subscription year | Until the end of the subscription month | Terms set out in the offer |
| Carrying hours forward | No carry-over to the next year | No carry-over to the next month | Based on the cooperation terms |
Standard includes 3 change hours per subscription year; Business includes 3 per subscription month. Unused hours expire at the end of that period. Ongoing technical maintenance does not use this allowance.
Diagnosis and agreed recovery are included in the subscription, outside the change allowance. New features and larger changes are quoted before work begins. Fixing our own error does not use the client's hours.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Incident response | Within 4 working hours for critical incidents | Response within 30 min during office hours if the store or a critical function is unavailable | Availability by agreement |
| Office hours | Mon–Fri 09:00–17:00 (Warsaw) | Mon–Fri 09:00–17:00 (Warsaw) | As agreed for the engagement |
| Outside working hours | Subject to availability and agreed work windows | Priority handling, without a fixed response time | Under the agreed arrangements |
| Automated monitoring | 24/7 automated service and resource monitoring | Monitoring of services and agreed functions | Coverage suited to the environment |
| What response time means | Starting work on the issue | Start of handling, not completion of repair | Definition and scope set out in the offer |
Business response starts within 30 minutes during office hours if the store or a critical function is unavailable, for example if customers cannot place or pay for an order. Standard retains a response within 4 working hours for critical incidents. Office hours are Monday to Friday, 09:00–17:00 Warsaw time, excluding Polish public holidays. The clock starts with a monitoring alert or a report through the agreed channel. Response means starting work, not completing the repair.
We acknowledge routine requests by the next business day and agree the delivery date. Outside office hours, Standard is handled subject to availability, while Business receives priority handling without a fixed response time.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| WooCommerce | After reviewing the store and its plugins | After reviewing the store and its plugins | To environment needs |
| PrestaShop | After reviewing the version, theme and modules | After reviewing the version, theme and modules | Version and modules assessed in the project |
| Other platforms | Assessment and scope selection | Assessment and scope selection | Separate technical review |
| Onboarding and migration | Scope and cost after review | Onboarding plan and acceptance test | Migration plan |
| Licences and domains | Separate unless agreed otherwise | Separate unless agreed otherwise | Based on the design and licences |
Our WooCommerce care covers WordPress, the theme and accepted plugins. For PrestaShop, we tailor the update process to the store version, theme and modules. For both platforms, we check change compatibility, purchase functionality and the ability to restore the store.
If an accepted connection fails, we diagnose the cause, restore agreed functionality on the store side and coordinate the support request with the provider. Availability of the external system remains its operator's responsibility.
We take over the store from an agreed, stable baseline.
Resolving an existing infection, pre-existing faults or a larger migration is quoted separately before ongoing care begins.
Before starting, we agree which modules, payments, shipping services and integrations are covered.
Supplier charges remain payable by the customer unless the proposal expressly states otherwise.
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.
Prices are net, plus VAT. Standard is billed annually and Business monthly. Before purchase, we confirm the scope and costs of onboarding, the subscription and required licences.
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.
We review the store platform, modules and order process. We identify work needed before taking over care.
We agree resources, the plan and supported integrations. We confirm costs, backups, tests and incident handling.
We plan access, migration and a purchase journey test. We agree the cutover and how to protect new orders.