Scattered information
Website details spread across spreadsheets, hosting dashboards, documentation and people’s memories.
Website infrastructure intelligence
Know what you’re running. Know what’s at risk.
Managing dozens of websites across different servers, hosting providers and technology stacks?
SiteKeeper is an early-stage concept exploring a better way to understand your website estate, identify potential security exposure and keep track of what needs attention.
An early concept from Ainley Digital. No product available yet.
The moment that started it
A vulnerability is disclosed. What happens next?
On 21 October 2026, a critical PHP vulnerability was disclosed, and developers everywhere started reviewing the PHP installations they were responsible for.
For us, the first question was simple: which of our websites could be affected?
Because we keep a current record of which site runs on which server, and which PHP version each one uses, that question had a quick answer. We knew which servers to review, which sites to update first and how to confirm each one afterwards. It was a controlled response rather than a scramble.
That worked because the estate was manageable and the records were up to date. Plenty of teams can’t say the same, and that isn’t a criticism. It’s what happens when websites build up over years, across clients, servers and people.
Now imagine you’re responsible for 75 websites spread across six hosting providers.
- How quickly could you work out which websites might be affected?
- How confidently could you confirm that every one had been reviewed?
- Disclosure · 21 Oct 2026
A critical PHP advisory is published.
- Scoping
Current records show which servers run the affected versions and which client sites sit on them.
- Updating
Servers are updated in a sensible order, starting with the sites that matter most.
- Confirming
Each site is checked afterwards, so “done” means verified, not assumed.
Sound familiar?
The information exists. It’s just everywhere.
Outdated records
A PHP version recorded months ago may not reflect what’s running today.
Reactive investigation
When a vulnerability appears, teams spend valuable time reconstructing their technical estate.
Difficult accountability
Tracking affected websites, responsibility and remediation can become a manual exercise.
It’s not about replacing your spreadsheet. It’s about making the information useful when you need it.
The idea
One clearer picture of every website you look after.
These are proposed capabilities, not features you can use today. We’d like to know which of them would genuinely help, and which wouldn’t.
Technical inventory
A single record of your websites, clients, hosting environments, runtime versions, frameworks and owners, starting from the spreadsheet you already have.
- clients
- servers
- PHP / Node
- CMS & frameworks
- owners
Infrastructure visibility
Where supported integrations allow, SiteKeeper could check what’s actually running and flag changes or gaps, so records don’t quietly drift out of date.
- version drift
- new unknowns
- last verified
Vulnerability intelligence
Relevant security advisories could be matched against the components you’re known to run, highlighting websites that may need investigation.
- advisories
- affected versions
- may need review
Remediation tracking
Record who is investigating, what was done and how it was verified, building a useful history for your team and your clients.
- assigned
- actions taken
- verified
- client summary
A matched version is a reason to look, not proof that a site is vulnerable or compromised. Automatic checks would only be as good as the data a team chooses to connect, so SiteKeeper would never claim to confirm a site is secure on its own.
A spreadsheet tells you
what somebody recorded.
SiteKeeper aims to tell you
what is actually running, what has changed and what needs attention.
How it could work
From vulnerability disclosure to a clear plan of action.
- 1
Know your estate
Import existing website records and connect supported infrastructure sources.
- 2
Identify potential exposure
Match applicable security intelligence against known technologies and versions.
- 3
Take action
Investigate, assign responsibility and record remediation.
- 4
Demonstrate ownership
Understand outstanding risks and communicate verified actions to clients.
Help us understand the problem
Is this something you’d actually use?
We’re exploring SiteKeeper because this is a problem we’ve encountered firsthand.
But experiencing a problem doesn’t automatically mean there’s a product worth building.
Before committing to development, we want to understand how other agencies and developers manage their websites, what already works and what remains frustrating.
Whether you love the idea, already have the perfect system or think we’re solving the wrong problem, your perspective would help.
Only interested in early testing? Register your interest at the end of the questionnaire.
Share your experience
There’s a problem with your answers
Thank you. That’s genuinely useful.
Your response has been recorded. Every answer helps us decide whether SiteKeeper should exist, including the ones that say it shouldn’t.
Your response has been recorded, and you’ve said we can get in touch. Here’s what happens next:
- Simon will read your answers personally.
- If it looks like a good fit, he’ll email you to arrange a short, informal conversation.
- No newsletter, no sales sequence.
Know someone else who looks after lots of websites? Sharing this page would help a great deal.
Who’s behind it?
Born from experience, not a feature wishlist.
SiteKeeper is an early-stage product concept from Ainley Digital, an independent software development business specialising in senior-led technical delivery.
The idea grew from managing real websites, maintaining real infrastructure and responding to real security incidents.
We’re exploring whether those experiences reflect a wider problem worth solving.
- StageConcept validation
- ProductNot built yet
- Looking forHonest opinions and early testers
- Based inHuddersfield, UK