How does this work start?
Tell us which system you rely on: a site, an application, or the servers it runs on. We look at that with you. You do not need a finished specification on the first call.
Cybersecurity and managed IT
We look after sign-in, backups you can restore, and the servers you rely on. We do not promise a system cannot be breached, or an uptime percentage.
What we build with you
Care for the systems you already rely on
We do this for a small company, a startup, an educational institute, an online shop, or a team that runs a web application or its own servers. The worry is practical: who can sign in, what is left open, whether yesterday's work can be restored, and who notices when the service stops answering. We take on that care with you.
A plain account of what we found
We review access, exposure, and backups, and we tell you what we found in words your team can act on.
We fix what we agreed
We repair the weaknesses we agreed to fix. We do not hand you a certificate, and we do not claim the system cannot be breached.
Someone watching the service
We watch the servers and the application you named. When it stops answering, we work to restore it. We do not quote an uptime percentage.
We start from the system you rely on
You do not need a finished specification on the first call. We start from the system you rely on.
-
You show us the system
A site, an application, or the servers it runs on. You tell us what has to keep working.
-
We review access and exposure
Who can sign in, what is reachable, and which copies of your data exist. We report what we found. We do not invent an audit seal.
-
We fix what we agreed
Tighter access, a backup that can be restored, and the weaknesses in the system you asked us to repair.
-
We stay with the running system
Monitoring and the day-to-day care of those servers stay part of the work. You keep a clear way to reach us when something changes.
The care we take on
- A review of access, exposure, and backups
- Watching the servers and the application you named
- Who may reach each part of the system
- Repair of the weaknesses we agreed are in scope
We will not invent a guarantee
- A certificate, an audit seal, or a compliance badge
- A promise that the system cannot be breached
- An uptime percentage
- A list of security products we have not agreed to use
We stay with the system after the care is in place
We look after the system you named, and we stay with it. When you add an application or change who should have access, you tell us and we adjust that part with you. The same company also trains people on this work. The first conversation can start with the one system you cannot afford to lose.
The courses are on our courses page. To tell us which system you rely on, use the contact form.
Questions we are glad to answer
Do you certify the system or promise it cannot be breached?
No. We review access, exposure, and backups, we tell you what we found, and we fix the weaknesses that are in scope. We do not issue a certificate, and we do not promise that a system cannot be breached.
What do you watch after it is live?
The servers and the application you asked us to look after. When something stops answering, we work to restore it. We do not quote an uptime percentage.
What is a backup in this work?
A copy of what you cannot afford to lose, kept so it can be restored. We check that a restore works. A copy that has never been restored is not yet care you can count on.
Do you train people on this as well?
Yes. The same company trains people on this kind of work. If you want to learn it instead of commissioning the care, start with our courses and we will help you find the path.
We would be glad to hear about the work
Tell us the step your team repeats. We will talk it through on a call or by email. If you want to learn this work instead, the same company trains people on these systems.