Services
The layer nobody notices, until the day it falls over.
Servers, certificates, updates, backups, monitoring and a phone somebody answers. It is not the layer anyone gets excited about — it is the one that decides whether you sell on a Sunday night.
What you get
Hosting in your name
The account and the domain belong to your business; we hold access. Moving never has to be asked for as a favour.
Updates tested first
Dependencies, security fixes and platform upgrades go through staging before they reach the public. Not an auto-update that breaks the basket one morning.
Backups that have been restored
Daily file and database backups, off the machine itself, with a retention window. And a tested restore — a backup nobody has ever restored is not a backup.
Monitoring and alerts
Uptime, certificate expiry, response times, errors and failed payments. We hear about it first, not one of your customers on the phone.
Security at the basics
HTTPS and certificate renewal, security headers, rate limits on forms, separate keys per environment, and no access shared over chat.
Changes inside the month
Small changes — a line of copy, a banner, a new page — happen within the maintenance. Not a quote for every half hour.
How we work
Maintenance is not an insurance premium
The usual maintenance contract is paid every month and does nothing visible until something bad happens. Treating it as dead cost is a reasonable reaction.
So ours contains work you can see: the small changes get made, the updates get run, and every month you know what happened. If a month needed nothing, we say so — we do not invent tasks to fill a report.
Auto-updates: the most common way an eshop goes down
On most Greek eshops we take over, updates are either automatic or non-existent. Automatic ones break the checkout without warning; non-existent ones leave vulnerabilities open for years.
The middle path is dull and it works: update in staging, check the critical paths, release, keep the ability to roll back. Security fixes go first.
One person who knows the project
The difference between ten minutes and two days is usually whether whoever answers already knows the system. A ticket in a queue learns it from scratch every time.
We are a small team, and here that is the advantage: whoever answers wrote the code. We reply within one working day, as we promise everywhere else on this site — and far faster than that when something is down.
What happens if you leave
The repository, the domain, the hosting account and the backups are yours. Handing over to someone else is access changing hands, not a negotiation.
We write it here because it is the most common fear: a site that cannot move is not a service, it is a hostage.
Process
Mapping
Two hours with you, one week in your data. It ends in a written account of what is wrong.
Plan & price
Scope, timeline and cost per layer. No open-ended invoices.
Build
We work in weekly cycles. You get a staging environment from week one.
Maintenance
Monitoring, updates, a monthly report and one person who knows your project.
Fit
A good fit
- Eshops where an hour down is lost orders, not an inconvenience.
- Businesses with nobody technical, currently phoning whoever built the site three years ago.
- Anyone who cannot say when the last backup ran — or whether it has ever been restored.
Not a good fit
- Businesses with their own technical team who want control of the infrastructure. There is no sense paying twice.
- Anyone needing 24/7 support with guaranteed response times. We are a small team and will not promise what we cannot keep.
- Anyone who only wants hosting at the lowest price. There are providers who do that more cheaply, and we will say so.
Questions
Will you take on a site you did not build?
Yes, after a review. We look at what it is built on, which updates are missing and what stabilising it will cost. If something cannot reasonably be maintained, we tell you before taking it on, not after.
What counts as a “small change”?
Copy edits, images, prices, a banner, a new page within the existing design. New functionality or new design work is a project and priced separately — and we say so before it starts, not on the invoice.
How fast do you respond if the site goes down?
Monitoring tells us before you can call, and an outage comes before everything else that day. For everything else, the one working day we promise everywhere applies.
Where is the data hosted?
On infrastructure with EU servers, and the backups likewise. It is a choice, not a detail: where data sits is part of compliance, and the privacy policy has to be able to say it.
What does it cost?
Monthly, depending on what is running and how critical it is. Ask for a quote below and you get a written price within one working day.
Quote
What would it cost you?
Every business is priced on its own numbers. Tell us yours in a minute and get a written offer, not a price list.
Quote request
- A person reads every request and writes the offer. Nothing is sent automatically.
- Ad budgets are separate: you pay Google, Meta or OpenAI directly, from your own card.
- No calls unless you ask for one.
Related
- WebsitesWebsites written in Next.js: fast on mobile, a CMS you can edit yourself, technical SEO from day one, hosting and maintenance after launch. Athens.
- EshopCustom eshops in Next.js with a headless CMS, Greek payments and couriers, a fast mobile checkout, Google Shopping feeds, and maintenance after launch.
- Analytics & trackingGA4, server-side tagging and Consent Mode v2 for Greek eshops: measurement that agrees with the till and survives the cookie banner.