ProFor.Pro Profor.Pro
— field notes since 2008

IT infrastructure
that just works.

We run servers, networks, and databases for SMBs. Backups that actually restore. 1C that doesn't fall over on payroll day. Information security without the noise.

How we work
18
years running
8+
avg tenure with client
24/7
monitored
// approach

What a typical client infrastructure looks like

Not the brochure-ware server dream. The real stack: a couple of physical hosts, a hypervisor, a handful of VMs, backups in two geographic locations. We monitor what matters, we leave the rest of the system alone.

A page from the engineering journal: Proxmox / VMs / Backup diagram with handwritten notes
— typical setup: hypervisor · workloads · backup

If you've never restored from a backup, you don't have a backup.

operational principle · profor.pro · 2008–2026
// field note

An entry from the engineering journal

Real incidents we document — sometimes they become blog posts, sometimes they stay internal notes.

2026-04-12 incident #41 severity: medium

Postgres logical replication during an office move

The client was relocating between two sites. Main database downtime over half an hour was unacceptable — three legal entities ran their 1C on it. The fix: stand up a replica at the new site in advance via pglogical, wait for the full sync, switch the connection string during the accounting team's lunch break. Actual downtime — 4 minutes 18 seconds, mostly DNS cache.

→ full write-up on the blog
— write us a note

Tell us about your task

We reply within one business day. No bots, no auto-responders. If you have a specific pain — write us, we'll talk through how we've handled it before.