In a managed IT service, the day-to-day running of your IT passes to an outside team under a defined contract. Some people look for this service under the name IT outsourcing, but outsourcing is the wider idea: it also covers supplying staff or handing a whole department to another firm. In a managed service, the provider takes on the work written in the contract rather than supplying a set number of people. For the general definition, see What are managed IT services? This page describes how ARGE ICT sets the service up.
When you need it
- Your IT depends on one employee or one outside firm, and only that person knows the passwords, the network layout, and the license details.
- Nobody checks alerts, updates, and backups on a regular schedule.
- You have an IT team, but most of its time goes to user requests and little is left for improving the infrastructure.
- You need monitoring outside office hours, but you do not want to build an on-call rotation.
- The number of branches has grown, and each one gets support from a different firm.
- An audit or the technical measures under the Personal Data Protection Law (KVKK) require your backup, logging, and access arrangements to be documented.
If only one or two of these apply to you, you may not need the whole managed service. Some companies need only monitoring and backup; others hand over everything from user support to security. We decide that with you at the first meeting, once we know how your environment is set up.
Components of the service
The service is made up of the work below. Which parts go into the contract depends on the company, and each part is described in detail on its own page.
- Infrastructure and security monitoring. We watch alerts from servers, the network, backups, and security tools on a single panel and rate them by severity. Monitoring hours and the scope of response are written in the contract.
- Backup. We keep backups in the isolated backup zone and restore a chosen system to a separate environment to show that the backup works.
- Firewall and endpoint. We review firewall rules on a schedule and run endpoint protection (EDR) on computers and servers.
- Security information and event management (SIEM). We gather logs from servers, network devices, and applications in a central log system and assess the alerts.
- Identity and access. Multi-factor authentication (MFA), roles and permissions, and account changes when people join or leave.
- Microsoft 365. Email, Teams, and SharePoint structure, the license plan, and security settings.
- User support and maintenance. Help desk, scheduled updates, inventory, license and warranty tracking, and a periodic report.
- Virtual CIO. A vendor-neutral view for management on the IT roadmap, the budget, and supplier decisions. Optional.
- ARGE Cloud. If your servers move to ARGE Cloud, we run that infrastructure too.
You do not have to take every component. You can hand over only monitoring and backup and keep user support with your own team. To add a component later, we update the scope of the contract together with the inventory. How often each component is reported is also written in the contract.
An IT maintenance agreement covers day-to-day upkeep and support: monitoring devices, updates, running backups, the help desk, account changes, and license and warranty tracking. Managed IT services add SIEM, firewall and endpoint operation, identity and access management, Microsoft 365, and an optional virtual CIO on top of that, and bring all of it under one contract.
What is in scope and what is not
| Area | In scope | Out of scope |
|---|---|---|
| Infrastructure | Monitoring servers, network, and security devices; scheduled patches and updates; capacity tracking | Devices missing from the inventory and the contract; hardware cost |
| Backup | Running backups, restore tests, and reporting the test result | The software's own data corrections and functional operations |
| Security | Firewall rules, endpoint protection, SIEM alerts, account and permission changes | The decision on which risk to accept; separate audit work such as penetration testing |
| User support | Help desk, opening and closing accounts, faults on devices in the inventory | Personal devices that are not in the inventory |
| Business applications | The servers, database, and network under software such as ERP | The software's license, installation, and functional support, which come from the software vendor or the firm you bought it from |
| Projects | Operating work covered by the periodic fee | New system builds, migration projects, hardware and license cost, all quoted separately |
| Advisory | The IT roadmap and budget plan, if a virtual CIO is added | Legal advice and legal interpretation of license terms |
Monitoring does not prevent a failure or an attack; it only helps you notice early and start the response. The service also does not remove management's responsibility.
Handover steps
We take over the running of your IT in these five steps, in order. How long each step takes depends on how many systems you have and how quickly access is granted.
- We list servers, network devices, licenses, warranties, and accounts, and note an owner and a location for each. This inventory also sets the scope of the contract.
- We end the situation where administrator knowledge rests with one person. Each of our engineers gets a separate account, and we grant access with multi-factor authentication and only to the systems in scope. We write into the contract that actions are logged and that no shared administrator account is used.
- We list what the current backups cover and where they sit, then restore a chosen system to a separate environment to show that the backup can be used.
- We add the systems in the inventory to the monitoring panel and, where needed, to the SIEM. We set alert thresholds and who is notified together with you.
- The first periodic report shows the inventory, open risks, the backup test result, and the work ahead. How often later reports arrive is written in the contract.
If you would first like to see the current state in writing, you can start with an IT Health Check.
In-house IT team, IT maintenance agreement, and managed IT services
| In-house IT team | IT maintenance agreement | Managed IT services | |
|---|---|---|---|
| Who does the work | Your own employees | An outside team; servers, network, and user support | An outside team; infrastructure, security, identity, and user support |
| Preventive work | Depends on the time of whoever takes it on | Maintenance tasks named in the contract | Monitoring, backup tests, and security alerts written into the contract |
| Security monitoring | Your own tools and on-call rotation | If written into the contract | A component of the service |
| Strategy and budget | The IT manager or management | Out of scope | With the optional virtual CIO |
| Dependence on individuals | Knowledge can be lost during leave or a departure | Inventory and documents tied to the contract | Inventory and documents tied to the contract |
| Cost | Salaries and related expenses | A periodic fee | A periodic fee that changes with the number of components |
| When it fits | IT is the company's core business, or the team is large | Basic server and user support is enough | Security, identity, cloud, and continuity will also be managed from outside |
You do not have to pick one of the three at the start. In a co-managed setup, your IT team runs the business applications and the user relationship, and we take on the monitoring, backup, and security layers. The model can be changed later.
In the cloud, in your own environment, and across branches
On ARGE Cloud: Your servers run on our own infrastructure in a data center in Istanbul, in a virtual private cloud (VPC) set aside for you, and we run that infrastructure as well. In your own environment: The servers stay in your server room, and we set up the monitoring, backup, and security layers there. Together: Some systems can stay with you while backups and some applications run on ARGE Cloud.
If you have a head office and branches, the way they connect also affects the scope of the service. An MPLS line from your internet service provider (ISP) links the sites without sending traffic over the internet; if the same line is extended to ARGE Cloud, the systems there are reached over the private line too. Branches without MPLS connect through an encrypted IPsec tunnel over their existing internet line, using a router with SD-WAN support and a firewall. The details are in the head office and branch connectivity section.
What sets the price
We do not publish prices on the site; the fee is written in the quote once the scope is clear. These factors change it the most:
- The number of users and how heavy user support is
- The number of servers and network devices, and whether they are physical or virtual
- The number of branches and how they connect
- The need for monitoring and response outside office hours
- Compliance needs such as KVKK technical measures, and log retention periods
- The components in the contract: SIEM, Microsoft 365, virtual CIO, and similar
- How well the current environment is documented
At the first meeting, it is enough to tell us what you expect on fees and service hours.
Frequently asked questions
Is a managed IT service the same as IT outsourcing? It is close, but not the same. IT outsourcing covers a wide range, from supplying staff to handing a whole department to another firm. A managed IT service is one defined form of it: the provider takes on the work written in the contract, and a periodic report shows what was done.
How is it different from an IT maintenance agreement? An IT maintenance agreement covers day-to-day upkeep and support: monitoring devices, updates, running backups, the help desk, account changes, and license and warranty tracking. Managed IT services add SIEM, firewall and endpoint operation, identity and access management, Microsoft 365, and an optional virtual CIO on top of that, and bring all of it under one contract.
Can we use the service if we have our own IT team? Yes. In the co-managed model, your team runs the business applications and the user relationship, and we take on defined layers such as monitoring, backup, and security.
How do you get access to our systems? Each of our engineers gets a separate account, and we grant access with multi-factor authentication and only to the systems in scope. We write into the contract that actions are logged and that no shared administrator account is used. We can set up remote access with ARGE ZTNA or an SSL VPN.
What happens when the contract ends? Exit and handover are written into the contract. We hand documents, administrator accounts, and configurations to you, and because the inventory is already with you, moving to another provider is possible.
Does using the service remove our responsibility? No. Your management decides which risks to accept and how much budget to set aside. Monitoring does not prevent a failure or an attack; it only helps you notice it early.