Website maintenance after handover: hosting, HIKARI CARE or self-managed care
Aleksander BarczykPublished September 28, 2026
Going live is not the end of the project. Hosting, SSL, backups, updates and responsibility for forms and analytics remain. You can stay on lightweight infrastructure care, move to a subscription with developer hours, or take over the code – what matters is knowing what each path includes and what it really costs.
Why “the site is ready” is only the beginning
On the day your site goes live, everything looks finished: the layout is approved, the form sends mail, the SSL certificate shows green. A week later the operational questions start. Who updates dependencies? Where are backups stored, and does anyone test restores? What happens when the form breaks after a browser update or analytics stop recording conversions?
Website maintenance is not an add-on to graphic design. It is ongoing work on infrastructure, security, and consistency in search. Companies without a technical person often postpone these topics until the first incident costs enquiries from potential clients or hours of stress.
At HIKARI we treat delivery as a product meant to run for years – not a one-off layout handover. After project completion there are no hidden subscriptions or forced plans. You choose the cooperation model that fits your business scale and internal skills.
What business website maintenance actually includes
The technical care checklist looks similar regardless of technology. What changes is how much time each item takes.
Infrastructure and availability
Hosting, SSL, uptime monitoring, and basic incident response. The site should load quickly on mobile, because a slow service costs leads – especially when someone compares three providers in the evening.
Security and backups
Regular backups with restore capability, environment and dependency updates, access control for panels (hosting, DNS, repository).
Content, forms, and analytics
Small section changes, campaign landing pages, CTA tweaks, checks that the contact form and integrations (mail, CRM, bookings) work without disruption. Analytics tools need periodic verification.
Performance and technical SEO
Core Web Vitals, indexing, redirects after URL changes, structured data. You do not need daily obsession, but quarterly metrics review makes sense if the site should drive organic traffic.
Broader context on building a modern business site is on our websites for business page. If you are comparing stacks, the article on Next.js vs WordPress cost is a useful companion.
The hidden cost of no care
Downtime means lost potential clients. A slow site lowers conversion even when the design looks premium. Outdated WordPress plugins are a common attack vector; that is why we deliver websites almost exclusively on Next.js, effectively removing that risk, but you still need to manage hosting, APIs, and deploy processes.
Without an agreed care model, these tasks land on whoever “handles marketing” – and end up on a “someday” list. That is not the team’s fault. It is missing process.
Three paths after project handover
After completion with HIKARI Marketing you have three sensible routes. You do not have to choose forever – the model can change when the company grows or when in-house IT appears.
A. Lightweight infrastructure care (without HIKARI CARE)
For many companies it is enough that the site runs stably without spending internal time on technology. Basic maintenance on our optimised infrastructure – with ongoing stability and security monitoring – starts from a few dozen PLN per month (net, excluding domain and separate services such as paid mail APIs).
This path does not include a pool of developer hours or priority support. You know infrastructure and SSL are handled by a partner who built the project. We quote larger feature work or redesigns separately.
B. HIKARI CARE – subscription with developer hours
When the site should grow with the business – new sections, SEO optimisation, integrations, faster incident response – HIKARI CARE makes sense. It is subscription care for the site and related systems: hosting, updates, security, plus an agreed monthly scope of development work (we describe CORE, GROWTH, and ULTRA on our offer page).
The subscription is often cheaper than endless ad hoc hourly billing because the partner knows the architecture and does not restart every request from zero audit. You can cancel without a long-term contract – billing is monthly.
C. Full code handover and self-managed care
After project payment 100% of intellectual property and source code access transfer to you. We do not use vendor lock-in. If you have a developer, IT agency, or central tech team, you can move hosting, take the repository, and run deployments yourself.
That is real independence and real responsibility. With Next.js, “file hosting” is not enough: you need a release process, dependency updates, environment variables, and incident response. Infrastructure with an external hosting provider for a typical business site usually still costs from a few dozen to around a hundred PLN per month – plus domain and tools (email, analytics).
How to read a care agreement (SLA)
Whether you stay on path A, enter CARE, or move to your own IT, the contract should distinguish:
- Response time (when the partner acknowledges the ticket) from fix time (when the problem is gone).
- What is included in the subscription vs billed separately (e.g. a new booking module vs a typo fix).
- Who holds access to DNS, hosting, repository, and API keys.
- How backup works – frequency, retention, who tests restore.
When which path makes sense
| Situation | Sensible start |
|---|---|
| Brochure site, low traffic, rare changes | Path A – infrastructure |
| Active marketing, SEO, regular releases | HIKARI CARE (e.g. GROWTH) |
| In-house developer or “everything internal” policy | Path C – with option to return to A/B |
| Site critical for 24/7 sales | CARE with higher response priority |
If unsure, start with A. Upgrade to CARE when you run out of dev hours or every change needs a new quote. You can also contact us at any time – we are happy to help you choose a model.
FAQ
Questions and answers
- Do I have to buy HIKARI CARE after handover?
No. CARE is optional. You can stay on basic infrastructure maintenance with your vendor or take the code and host it yourself.
- How much does maintenance cost without a CARE subscription?
Hosting and monitoring on optimised infrastructure with us starts from a few dozen PLN net per month. Add domain (yearly) and any paid external services – e.g. form mail delivery – if you exceed the limits set by the system provider.
- Will I get source code and can I change hosting?
Yes. After project completion, rights to code and design transfer to the client. Moving to another host is possible; plan redirects and a transition period so you do not lose search visibility.
- How is lightweight infrastructure care different from CORE in HIKARI CARE?
Light care focuses on stability, SSL, backups, and monitoring – without a standing pool of developer hours or priority support. CORE in HIKARI CARE adds a monthly package of dev hours, broader scope, and subscription growth of the site. We describe the plans on our offer page.
- Does care include writing blog content?
Not in standard technical maintenance. Marketing copy can be ordered separately or included in a wider CARE scope if agreed in the monthly plan.
Want to align the model after a HIKARI build or move an existing site under our care? Talk to us about maintenance – or review HIKARI CARE plans directly.
