About
Open Horizons
IT outsourcing company focused on 1C, VMware, Proxmox and Bitrix24.
Audit first
Every project starts with an audit. We review backups, servers and remote access — and quantify the risks in money.
Transparent plan
Scope and SLA are fixed in the contract. Clear pricing, no hidden rates.
Fast response
We respond within an hour on critical incidents. The problem won't wait — neither do we.
Long-term partnership
We don't just fix things — we help build infrastructure that grows with your business.
Team culture
Why we genuinely enjoy this
Infrastructure isn't a "set it and forget it" kind of thing. Every system evolves, picks up workarounds, and eventually breaks at the worst possible time. That's exactly what we enjoy: figuring out why something isn't working the way it should, finding the actual root cause, and making sure it doesn't happen again — not because a checklist says so, but because we're genuinely curious.
We keep learning
1C gets updated, VMware changes its licensing terms, Proxmox ships a new release that quietly changes cluster behavior — if you're not tracking this weekly, in six months you're recommending yesterday's solutions. We read release notes, dissect other people's incidents, and get certified not to pad a resume but so we're not guessing when something breaks in production.
We verify, not take it on faith
"Backups are configured" and "backups actually restore" are two different claims, and the gap between them costs real money during an incident. Before recommending anything to a client, we test it on our own setup first — deploy it, break it, see what happens under failure, and only then propose it as a solution. It's slower than copying someone else's guide off the internet, but it doesn't fail you when it matters.
We look for what could be better
Working isn't the same as optimal. We regularly revisit what's already configured for clients — is there now a more reliable backup scheme, is it worth switching virtualization platforms, can incident response time be shortened. Infrastructure that simply "works" is, for us, a reason to ask whether it could work better.
We enjoy the payoff
The best part of this job is the moment a hard problem finally gets an actual explanation instead of a list of guesses. When a server that was "mysteriously slow" starts behaving predictably. When a client stops thinking about their infrastructure because it just works. That's the whole point.
We don't claim to know everything — in IT infrastructure, that's simply not possible. But we do know what a properly tested solution looks like, and we're not willing to hand clients anything less.