05 · Websites and software
Hosting and care
Your site kept fast, secure and up to date, with someone looking at it every day.
In short
Most sites get slower and less secure after launch, not because anything big happens, but because nobody is looking. Care means someone is.
I host the sites I build on servers I run, and I watch them with the same dashboards I use for my own products.
What's included
Hosting
Docker deploys on my own servers through Coolify, with Cloudflare for DNS, caching and protection.
Security
HTTPS, security headers and a strict Content Security Policy on every response, and the software underneath kept up to date.
Backups
Database backups on a schedule and daily CMS snapshots, any of which can be restored.
Monitoring
Index status, traffic, broken links and failed scheduled posts, with an alert when something needs attention.
Maintenance
Dependency updates, small changes and fixes, made in a branch, tested and then deployed.
Support
One email address and a person who knows the site, in English or Polish.
How I run it
Take over
An inventory of the site, its hosting, domains and accounts, and a first scan.
Move
If needed, a move to my servers, planned so the site stays up and the redirects are checked.
Baseline
Lighthouse, the checklist and monitoring set up, so later changes have something to compare with.
Routine
Weekly rescans, daily checks, updates and backups.
Report
What changed, what was fixed and what I recommend next.
Content Monitor · Site Scanner · Polaris CMS
Run on my own tooling
Care is mostly watching. This is what watches your site.
Site Scanner
A 98-item launch checklist, a crawler and Lighthouse
A rescan every 7 days
The crawl, the 98-item checklist and Lighthouse run again every week, and new findings are listed.
Fixes from findings
Each finding becomes a ready prompt for an AI coding agent, so a fix starts from the exact page and problem.
Content Monitor
The dashboard every live site is run from
Alerts on Telegram
A failed post, a broken link or a site with nothing scheduled raises an alert, held during quiet hours.
Your own login
A login that shows only your sites, and a personal API token if your own AI agent should read the data.
Support inbox
Support email in the same dashboard, next to the site it is about.
Polaris CMS
My own CMS, this site included
Backups in the CMS
Every save keeps the previous version, a full snapshot is taken daily and any snapshot can be restored.
Infrastructure
Docker on my own servers, behind Cloudflare
Coolify and Cloudflare
Docker images deployed through Coolify, Cloudflare in front, server backups and a strict Content Security Policy.
Proof
- Project Grzybolog Astro and Node in Docker on my own server through Coolify, with forecast jobs running twice a day.
- Project Olfaria Next.js on Coolify behind Cloudflare, with the edge cache purged after every deploy and Turnstile on the forms.
- Project Yolkday Permanent HTTPS redirects and security headers on every response.
Questions
Can you take over a site someone else built?
Yes. I start with a scan and an inventory, and tell you what I find before taking anything on.
Do I have to host with you?
No. The scanner and the monitor work from the outside, so I can look after a site on your hosting. Hosting it myself just means I can fix more, faster.
What if we part ways?
The site is a Docker image with its data in Postgres, so it can move to any server that runs Docker. You get the image, the data and my notes.
Related services
All services →Tell me what you need
A few lines are enough: what you want to build, fix or automate, and any date that matters. I reply in English or Polish.