Four environments, four very different tasks—on the same foundation
The four environments below are real, completed projects. For each one, we describe the starting situation, what had to be solved, and which technical decision determined the outcome. Wedo not publish client names—the task we solved is the main subject.
4 environmentsfrom the media provider to the isolated research lab
20+ yearsof enterprise IT operations experience behind them
1 client = 1 networkall four environments run on a dedicated segment
2 sitesdata centers in Budapest, independent of each other
The four environments at a glance
A media service provider, a research lab, a financial services provider and several commercial companies do not ask for the same thing. The table below shows where the tasks differ—the detailed description of each follows further down.
A live nationwide service in an existing environment that had to be taken over and migrated.
Building the entire internal network, web and data infrastructure, with migration and ongoing operations.
Parallel build and test migration, on a redundant 2×10 Gbps backbone.
02Biotechnology research lab
Research workloads with large data volumes, on data that must not be exposed to the internet.
Fully isolated IT infrastructure, not reachable from the internet.
Private subnet on its own switch, dedicated VPN endpoint, out-of-band management.
03Financial services provider with a nationwide branch network
An outward-facing public interface and the most sensitive data in the same system.
A two-tier, segmented application stack.
The database and application layer sharply separated from the public services.
04Commercial and service companies
A system running for years, but undocumented, resting on a single colleague's knowledge.
Outsourced operation of web, file and directory environments.
Takeover with documentation, monitoring, stabilization, daily backup checks.
The four environments in detail
Each case follows the same structure: what the situation was, what we did, and what the key point is. The technical details can be expanded, and the links lead to where each solution is also described in general terms.
We replaced the infrastructure under a live nationwide service
The job was to build and operate the entire internal network, web and data infrastructure—but not from a blank slate. The system was running, with nationwide coverage, and it had to keep running during the move. For a provider like this, downtime is not an operational inconvenience: it is a service outage.
So the new environment was not built in place of the old one, but alongside it. It was fully up and running before anything was moved onto it; the live cutover came only after a test migration, in an agreed time window, with a rollback plan. The workload is resource- and storage-intensive, so the backbone here, too, is the redundant 2×10 Gbps build—losing one uplink or one switch does not mean losing the service.
The project did not end with the cutover: we have operated the environment ever since, including monitoring, backup and documentation.
The migration succeeded if viewers never even noticed it happened.
An environment with no route leading to it from the internet
Research workloads handling large volumes of data, on data whose nature does not allow internet access. In this case the question is not whether the firewall rule is strong enough, but whether there is any rule at all that could be misconfigured.
The solution is a fully isolated infrastructure: a private subnet on its own virtual or physical switch, with no published services. There is no route into the environment from the internet—not because it is blocked, but because there is nothing to block. Access goes through a dedicated VPN endpoint, and the management interface sits on the out-of-band management network, which is not reachable from outside either.
Today this is not a plan for us but working practice: this is how the environments of our clients who handle sensitive data run.
Here isolation is not a setting but topology. A setting can be misconfigured; topology cannot.
Hardware level: iDRAC and iLO: the server can be managed even if the operating system does not boot
03Segmented application stack
Financial services provider with a nationwide branch network*
Two tiers, so there is no path from the public side to the data
At a financial services provider, the most exposed point and the most sensitive point are the same system: the public interface has to be reachable from outside, while the data has to be as protected as possible. On a flat network, the two are one hop apart.
That is why the stack has two tiers: the database and application layer is sharply separated from the public services. In front of the environment stands a dedicated gateway per client, with its own firewall, NAT and VPN rules, and its own public IPv4 address from our address range—so the IP reputation of the service and of its email does not depend on what another client does.
The practical consequence is simple: if a component of the public layer falls, the loss stays limited to that one component. It does not open up the database.
The question is not whether an attacker ever gets onto the first machine. It is how far they get from there.
The system worked. It was just that only one person knew how
This fourth case is not a single large project but several companies in the same situation: a web, file and directory environment that has been running for years, but undocumented. The knowledge is in one person's head, nobody knows for sure whether the backup can be restored, and nobody has known for a long time who has access to what.
In these cases a takeover does not start with a move but with an assessment: what is running, what it runs on, what is missing. Then comes documentation, the rollout of monitoring, and then stabilization—fixing the gaps uncovered: missing updates, backup gaps, outdated permissions. Only after that does the system become a continuously operated environment, with regular reporting.
Where the hardware has to stay on-site—because a production control system, a measuring instrument or a data-handling rule ties it there—we do not move it. We bring the same procedures to the site.
A key-person dependency does not come to light while the colleague is at work. It comes to light when they are not.
The four tasks are very different from each other, but the foundation is not. It is not an option on a price list, but the baseline every environment starts from with us—everything else is customization on top of it.
That is why you don't need to order a separate “security package”: the foundation is not an extra charge, it is the starting point. The details are on the Technologyand Security pages.
What you get on paper
A project is only worth something if, at the end, things not only work but are also written down. The documents below were produced the same way in all four environments—these are the ones that matter in an audit, when changing providers, or after an incident.
Document
What it contains
When it is produced
Status assessment and risk list
Servers, network, workstations, licenses, backup and the risks uncovered—specific, not estimated.
Before the decision. The assessment is not a commitment.
Target architecture, RPO and RTO
Defined per system: how much downtime and how much data loss is acceptable.
Before the quote.
Migration plan and rollback plan
Schedule, sequence, test migration—and also what happens if we have to roll back.
Before the cutover. A critical system is never moved live without preparation.
Service level agreement (SLA)
Availability, response time, maintenance windows, backup and retention rules—in writing.
When the service starts.
System documentation
A transferable description of the running environment. This is the point where the knowledge leaves a single person's head.
At takeover, then continuously, with change tracking.
Restore report
Whether the system really starts from the backup—in an isolated test environment, with a rating.
After the restore test, as a standalone service.
Operations report
What happened in your environment, and what to prepare for in the coming period.
During operations, on a schedule.
Why we always start with an assessment
In none of the four environments was our first step to send a quote. First we have to map what runs today, what it runs on, what is missing, and what could break tomorrow morning. Without that, the quote would be an estimate, and the migration plan guesswork.
servers, applications, data volume, network and the actual resource needs
the real state of the backups—not whether they start, but whether they restore
the permission structure and a record of access rights
RPO and RTO per system: how much downtime and how much data loss is acceptable
This rarely comes up when requesting a quote, yet it is the best measure of how transparent an IT operations provider is. With us, the environment is documented and transferable, permissions are recorded, and the recoverability of backups is proven with a written report.
up-to-date system documentation—not in the operator's head
change tracking: what changed in the environment, when and why
access and escalation paths written down
the data is always yours—we provide storage and operations services for it
These are the sentences we hear most often during assessments. Behind each of them is the same thing: a risk that everyone in the company knows about, but that just happens to be nobody's job. The link on the right takes you to where we have already solved it.
What you see today
What it means
Where we have looked at this before
“It works, but only one colleague knows how.”
Key-person dependency. The knowledge is not documented, so it cannot be handed over either.
If several rows in this list sound familiar, that is not unusual: in most environments they go together. The FAQ page has short answers to the most common questions—including who has access to your data.
What we deliberately left off this page
On a case study page, the easiest thing to do is overpromise. So we also state what we do not write down—that is as much information as everything else.
We don't publish client names
For an IT operations provider, who its clients are is information in itself—about where a given company's infrastructure is, and who holds the keys to it. We don't put that on a website. If you need a reference for your decision, ask during the assessment: we will see what we can share with the consent of the client concerned.
We don't publish numbers we haven't measured
There are no hours saved, percentage speedups or achieved availability figures on this page. Every number that does appear here—20+ years, two data center sites, 2×10 Gbps—can also be found on the other pages of this website. Committed availability and response times belong in the service agreement, not in a case study.
A case study is not a price list
The solution described was built for that specific environment. We don't sell templates: we tailor both the infrastructure and the operations service to the specific needs, so what worked at a similar company does not, by itself, determine your quote.
We don't claim every project went smoothly
In a migration, something always turns out differently than planned. That is exactly why it comes with a rollback plan, and why we never try anything in production first. The difference is not that there are no surprises, but that there is an answer to them.
* The four environments above are real, completed projects. We do not publish our clients' names—neither here nor anywhere else on this website. For an IT operations provider, who its clients are is in itself information about where a given company's infrastructure is; we do not make that public. The descriptions therefore name the sector and the task solved, not the company. For the same reason, this page contains no measured performance, size or savings data. The figures on theAbout us page—20+ years of experience, two Budapest data center sites, a redundant 2×10 Gbps backbone—refer to our own infrastructure, not to our clients' environments.
The fifth case could be yours
Let's start where we started with the other four: with an assessment. At the end, you get a documented snapshot of where things stand and a risk list—even if you don't continue working with us.