No monitoring
You learn about an outage from your customers. Monitoring and alerts tell you earlier that a disk is filling up or a service has stopped responding.
04 / DevOps
We make sure your systems run stably, fast and securely, around the clock. We configure servers, watch over backups and updates, set up monitoring and alerts, and bring order to how applications are deployed.
You learn about an outage from your customers. Monitoring and alerts tell you earlier that a disk is filling up or a service has stopped responding.
A backup only makes sense if you can restore from it. We set up backups and regularly check that restoring works.
A repeatable deployment process with automated tests and the ability to quickly roll back changes.
System and software updates planned so that they do not break anything.
Server hardening: key-based access, firewall, least privilege, up-to-date patches.
A review of resources and costs, right-sizing, dropping what nobody uses.
Preparing Linux servers, services, networking and access. For your applications.
Docker and orchestration where it makes sense: repeatable environments, easy deployments and updates.
Automated building, testing and deployment of applications.
Metrics, logs and notifications about problems. A dashboard that shows the state of your systems.
A backup plan, automation, storage in a separate location and restore tests.
Tuning services, databases and resources so they run faster and cheaper.
Regular patches, configuration review, management of access and secrets.
Alfresco, n8n and custom applications run with us as their permanent caretaker.
Below are the specific areas and tools we work in. If you are stuck on one of them, write to us.
Linux (Debian / Ubuntu)
Installation, configuration, disks and LVM, service management with systemd.
SSH and access
Key-based access, passwords disabled, bastion host, least privilege.
Firewall and protection
ufw/nftables, fail2ban, automatic security updates.
Bash and task automation
Scripts, cron and systemd timers.
Docker and Compose
Images, volumes, networks, healthchecks, resource limits.
Kubernetes / k3s (when needed)
Orchestration where scale requires it.
Image registry
Private registries and image scanning (e.g. Trivy).
nginx as a reverse proxy
Routing traffic to services, limits, security headers, compression.
TLS and Let’s Encrypt
Certificates issued and renewed automatically.
WireGuard VPN
Secure access to the infrastructure from outside.
DNS and Cloudflare
Records, proxy and protection against excessive traffic.
Prometheus and Grafana
Metrics, dashboards, exporters for servers, databases and applications.
Alertmanager
Alerts by email or messenger before a user notices the problem.
Logs (Loki / ELK)
Collecting and searching logs in one place.
Uptime checks
External availability checks of services.
restic / Borg
Encrypted, deduplicated backups with retention and off-server storage.
Database backups
Consistent PostgreSQL / MySQL dumps and point-in-time recovery.
RPO / RTO and restore tests
We agree on acceptable data loss and recovery time, then verify them.
GitHub Actions / GitLab CI
Building, testing and deploying after every change.
Ansible and Terraform
Repeatable configuration of servers and cloud resources defined in code.
Deployments with rollback
Versioned releases and fast rollback.
Hetzner and other clouds
Resource selection, private networks, snapshots, costs.
If you are trying to set this up yourself and got stuck on one of the points above, tell us where you are. We will point you in the right direction, or do it for you.
We check what you have: servers, applications, backups, access. You get a list of risks in order of importance.
We set priorities: first whatever threatens data loss or downtime.
We put in place backups, monitoring, updates and automated deployment.
Documentation and instructions, so you do not depend solely on us.
If you wish, we stay on as caretaker of your systems under an agreed model of cooperation.
Yes. We work in your infrastructure and get access limited to the minimum needed for the task. We can also prepare new infrastructure if you need it.
Both models are possible. We often start with a review and clean-up (a project), then, if it makes sense, move to ongoing care.
Yes. We plan the migration to limit downtime and to have a fallback plan.
The scope of support, hours and response times are set in the contract, depending on how critical your systems are.
Yes. We test restoring from backups, because it is the only way to be sure.