OneNet Admin Static
€100
net/month
- Hours of work
- 1 hour a month
- Staging environment
- not included
- Response time
- up to 24 h (working hours)
Websites · Maintenance
A website without a content management system removes half of the usual worries: there is no admin panel to take over, no plugins to update and no database that could be stolen. The risk of a break-in falls, and so does the hosting bill. The rest remains: the libraries used to build the website get security fixes, the certificate expires, the form stops sending messages, and every text change is made by the developer, because there is nowhere you could make it yourself. Above all, this plan gives you time for such changes.
Pricing
I bill all three monthly, with no fixed term. They differ in the hours of work, a staging environment before changes go live, the change log and the response time to your requests.
Configurator
€100
net/month
€200
net/month
€300
net/month
Plans for websites without a CMS: static and custom-coded websites. I maintain web applications and integrations under an individual maintenance agreement. All prices are net, excluding VAT. The offer is for businesses only.
When I build a website without a CMS for you, the first 3 months of OneNet Admin Static Plus are included in the project price. The website then goes live with monitoring, backups and hours of work, and the first fixes after launch cost nothing extra. I describe the terms of the build on the website design page.
Plan comparison
The first six rows cover what usually decides the choice, and one click opens the full comparison. Items without a tick are not part of that plan, but you can order them separately.
| What is included | OneNet Admin Static €100 net/month | OneNet Admin Static Plus €200 net/month | OneNet Admin Static Max €300 net/month |
|---|---|---|---|
| Hours of work per month | 1 hour | 2 hours | 4 hours |
| Uptime and SSL certificate monitoring | every 5 minutes | every 5 minutes | every 5 minutes |
| Spam blacklist monitoring | included in the plan | included in the plan | included in the plan |
| Dependency updates and security fixes | included in the plan | included in the plan | included in the plan |
| Backups of the repository, content and configuration | included in the plan | included in the plan | included in the plan |
| Upkeep of forms and integrations | included in the plan | included in the plan | included in the plan |
| Ongoing implementation of requested changes | not included in the plan | included in the plan | included in the plan |
| Image optimisation | not included in the plan | included in the plan | included in the plan |
| Performance and Core Web Vitals check every 30 days | not included in the plan | included in the plan | included in the plan |
| Staging environment before going live | not included in the plan | not included in the plan | included in the plan |
| Code versioning and a change log | included in the plan | included in the plan | included in the plan |
| Website check after every deployment | not included in the plan | not included in the plan | included in the plan |
| Advice on developing the website further | not included in the plan | not included in the plan | included in the plan |
| Priority handling | not included in the plan | not included in the plan | included in the plan |
| Support channels | email and Trello | email, Trello and phone | |
| Response time to requests (within working hours) | up to 24 h | up to 12 h | up to 6 h |
Plans for websites without a CMS: static and custom-coded websites. I maintain web applications and integrations under an individual maintenance agreement. All prices are net, excluding VAT. The offer is for businesses only.
Scope of work
The work covers content changes, monitoring, security fixes, backups and loading-time checks, and you send every change to one person.
When a price, a service description, a team photo or your opening hours change, you email me the new version. I change it in the code and publish it. Depending on the plan, you have one, two or four hours a month for this.
Every 5 minutes a monitoring service checks the website address and alerts me when the website stops responding or responds too slowly. Separately, I keep track of the expiry dates of the SSL certificate and the domain, because to a visitor an expired certificate or domain looks like an outage, with a browser warning instead of the website. I also check whether the domain has appeared on spam blacklists.
A website without a CMS still runs on other people’s code, from the generator that builds it to the libraries behind galleries, maps, form validation or video. Their authors publish fixes, and some of them close real security holes. I check reported vulnerabilities, update the versions and rebuild the website to see whether everything still works.
I keep the code in a repository with its full history. I also store a package with the published files, photos in their original resolution and the server settings for redirects, headers and cache rules. Restoring the website with another hosting provider then takes a quarter of an hour rather than days of guessing where each setting was.
A website without a database still handles quote requests, newsletter sign-ups and messages to the company inbox. Behind each of them is an external service or a small server script, which can stop working after an access key changes or when it hits a limit. I send a test enquiry and check that it arrives and does not end up in the spam folder.
With OneNet Admin Static Plus and OneNet Admin Static Max, I measure loading times and Core Web Vitals once a month and compare the results with the previous measurement. Static websites start out very fast, but they can lose that speed. It only takes a few uncompressed photos added with a content change, or a new script for an advertising campaign.
Every change is a separate entry in the code history, linked to your request. With OneNet Admin Static Max, I also keep a readable change log and a staging environment, so rolling back any change comes down to telling me which point you want to go back to.
Process
This is how a single change goes from your message to the entry that closes the task. The third step applies to OneNet Admin Static Max only. With the other plans, I publish straight after the estimate.
You write what should change and attach the text, the photo or the file with the price list. I do not need a specification or file names. It is enough to point to the place on the website and describe how it should look afterwards.
I reply with how long the task will take and how many hours you will have left that month. If the request goes beyond them, you get a separate price to approve before I start. Unused hours do not carry over to the next month, because the plan pays for my availability.
This step is part of OneNet Admin Static Max only. The change first appears at a test address, where you view it in your browser and approve it or send it back with comments. In the two lower plans, I publish the change within the time frame of your plan, without a separate review round.
I rebuild the website, upload the finished files to the server and clear the cache. Then I check the part that changed: I open the page on a computer and a phone, click the links and send a test enquiry if the change affected a form.
The task ends with an entry giving the date, a description of the change and the code version number. Six months later, you can still see when the price list changed and what the previous one looked like, and if a change goes wrong, I go back to the previous state without restoring anything from a backup.
Outside the plans
The plans on this page are for websites that present a company. Software that processes data carries different risks and needs a different way of working, so I maintain it on separate terms.
For a calculator that prices quotes by your company’s rules, an order panel for your sales staff or a connection to a stock management or recruitment system, I offer an individual maintenance agreement. I price the agreement after reviewing the code and the services the software depends on. The price depends on the number of connections to external systems, the required availability, the agreed support hours and whether I keep a standby environment for you. I describe how I build such solutions on the WordPress plugins and API integrations page, and you will find examples in the case studies.
Other services
Maintenance is the last stage: first comes a website, a shop or an add-on written for a specific need. Each of them has its own page with the scope and the process.
Company websites, including multilingual ones, built with WordPress or as static sites. Design, development, go-live and transfer of the content from the old website. Quote after a short brief.
Online shops built with WooCommerce, with payment methods, shipping and integration with your inventory system. Sales modules coded for your industry. Quote after a short brief.
Custom plugins and connections between WordPress and other systems such as CRM, stock management or applicant tracking, with data import and synchronisation. Quote after a short brief.
You will find all website services on the website development page. If your website runs on WordPress after all, the right offer is WordPress maintenance: those plans include weekly updates of WordPress and plugins, which do not apply here.
FAQ
What owners of websites built without a content management system ask about, from costs and content changes to what they receive when the cooperation ends.
A static website needs less maintenance than one with an admin panel, but it still needs some. Updates to a CMS and its plugins fall away, and with them the most common way attackers get in. The libraries the website is built with still get security fixes, and the certificate and the domain still expire. The service behind the contact form can fail, the hosting has its outages, and the content goes out of date. Most of all, you need someone you can reach, because without an admin panel every change needs a person who knows the code.
You send the change by email or, depending on the plan, as a card in Trello. Describe it in your own words, attach the material, and I reply with a date. I make corrections within the time frame of your plan, and larger ones on a date I confirm in advance. If the content changes every week and the hours regularly run out, I will work out with you whether adding a simple content editor to the website would cost less.
There is no minimum term. I bill maintenance monthly, with no cancellation fee, and a move to a higher or lower plan applies from the following month. For some businesses, the right plan depends on the season. When a company has many new projects to show in spring, OneNet Admin Static Max pays off for a few months, and in autumn the smallest plan is enough again.
Yes, after a review of the code. I check what the website is built with, whether I can build it on my own computer, how it gets published and what it depends on. I quote the review separately, and at the end I recommend one of three options: taking the website on as it is, taking it on after a clean-up, or not taking it on at all. The review comes first because I do not take responsibility for code I have not read.
If your website runs on WordPress, you need WordPress maintenance, which centres on weekly updates of WordPress, the theme and plugins, malware protection and database backups. The plans on this page are for websites without a CMS, which have no admin panel and no database. Instead, I take care of security fixes in the libraries the website is built with. Both lines cost the same, and the Plus and Max plans include the same number of hours of work. If you run both kinds of website, I combine plans from both lines on one invoice.
I charge it at an hourly rate once you have approved the amount, and I never add extra hours to an invoice without asking. For larger tasks, such as a new page or a rebuild of a section, I quote a fixed price so that you know the cost before I start. If jobs like these come up every month, I suggest a higher plan, because it costs less than separate charges.
You get the repository with the full history of the code, the latest package of content (published files, photos in their original resolution and server settings) and a description of the deployment. It explains how the website is built, where the files go and what handles the forms. Nothing stays with me, because the website runs on your hosting account, and a new developer has everything needed to take it over in a day.
Yes, when the type of data and work requires it or when the contract with your company provides for it. During maintenance I have access to personal data, for example enquiries sent through the website’s forms or server logs. The agreement is made under Art. 28 GDPR, or Art. 28 UK GDPR for companies in the UK, and includes the list of sub-processors and the technical and organisational measures.