Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.
Conrad Lunderstedt
A buyer guide to IT infrastructure solutions by layer: identity, devices, compute, network, backup, security and the operations layer, with October 2026 list prices for a 50-person company, who should run each layer, questions to ask a provider and what to buy first.
Updated: October 2026
IT infrastructure is easy to price one invoice at a time. Adding up the whole stack is harder: seven layers, from sign-in to backup, each with its own bill and its own owner to pick. Below are the IT infrastructure solutions for each layer, what they cost at October 2026 list prices, and the order to buy them in.
IT infrastructure is the hardware, software and services that let people work: sign in, open files, reach the internet, and get their laptop fixed when it breaks. An IT infrastructure solution is any product or service you pay for to run one piece of it. A firewall is one. So is a Microsoft 365 subscription, a backup plan, or an MSP contract that covers all of the above.
We won't redefine the components here. Our guide to IT infrastructure management covers what each one is and how teams run them day to day. This post is about the buying side: what each layer costs in 2026, and who should own it.
The market is big and getting pricier. Gartner's July 2026 forecast puts worldwide IT spending at $6.37 trillion in 2026, up 14.2% from 2025. Gartner's John-David Lovelock flagged budgets strained by "rising hardware and memory costs." For a small company, that shows up as a higher quote on the next server or laptop refresh.
Sorting the market by layer makes buying simpler, because each layer has one job, one pricing model and one natural owner. Here are the seven that matter for a company between 10 and 250 people.
You'll also see things like an AI help desk, cloud management, virtualization, automation, asset management and AI security sold as separate "solutions." Each of those folds into a layer below. Virtualization is compute. Asset management and automation belong to the operations layer. An AI help desk is ticketing, which is operations too. Sorting them this way stops you from buying two products for one job.
Who can sign in, from where, with what second factor. For a small company this usually means Microsoft Entra ID or Google Workspace, which doubles as the email and file platform. Identity is the layer every other layer trusts. If an attacker owns an admin account, the firewall and the backup don't matter much.
Laptops, desktops, phones and the policies on them: encryption, updates, which apps can install. Device management tools like Microsoft Intune push those policies. Some companies skip physical desktops for part of the team and rent cloud PCs instead.
Servers, virtual machines and file storage. A 20-person office may run nothing here beyond SharePoint. A firm with a line-of-business app from 2012 may still need a Windows server somewhere, on a shelf or in a cloud region.
The internet connection, the firewall, switches and Wi-Fi access points. This is the one layer that stays physical for any company with an office. Somebody has to plug it in.
Copies of your data that survive ransomware, a deleted SharePoint folder or a dead laptop. That means endpoint backup, server backup and a separate copy of your cloud data. A backup only counts once you've restored from it.
Security runs through every layer: multi-factor sign-in on identity, endpoint protection on devices, segmentation on the network, immutable copies in backup. IBM's 2026 report puts the global average breach cost at $4.99 million, a 12% rise on the year and a record high. That number is why security spend sits inside every row of the cost table below, not in one row of its own.
Monitoring, patching, remote access, scripting, inventory and ticketing. These are the tools that keep the other six layers running. It's also where tool sprawl and per-device bills live, so it gets its own section further down.
One solo admin on r/sysadmin posted their full stack for a 100-user company and asked if it still holds up. Count the layers in that list: hyperconverged servers, Active Directory, enterprise Wi-Fi, file and print servers, endpoint security, WSUS patching, firewalls, Microsoft 365, MDM, intrusion detection and two backup products. That's every layer above, run by one person.
Here's what each layer costs at published list prices, read from each vendor's own site in October 2026. These are list prices before partner discounts, taxes and any import surcharges. Your quote may differ, so treat them as the ceiling a small company should expect.
| Layer | Typical options | Pricing model | List price, October 2026 | Who usually runs it |
|---|---|---|---|---|
| Identity, email and files | Microsoft 365 Business Premium (bundles Entra ID P1, Intune and Defender for Business) | Per user, monthly | $22 per user a month paid yearly, $26.40 on monthly billing | SaaS vendor, configured by MSP or admin |
| Identity add-ons, bought alone | Microsoft Entra ID P1, Intune Plan 1 | Per user, monthly | Entra ID P1 $7, Intune Plan 1 $8 per user a month | MSP or admin |
| End-user devices (cloud PCs) | Windows 365 Business | Per user, monthly | $36 to $108.80 per user a month for the sizes on Microsoft's pricing page | MSP or admin |
| Compute and storage | AWS Lightsail virtual servers | Per server, monthly | Windows $44 (4 GB) to $124 (16 GB) a month; Linux $24 to $84 for the same sizes | MSP or admin |
| Network | Ubiquiti UniFi gateways and Wi-Fi 7 access points | One-time hardware | Gateways $129 to $599; access points $99 to $189 each | MSP or local installer |
| Backup and recovery | Backblaze Business Backup for endpoints | Per computer, yearly | $99 per computer a year | SaaS vendor, checked by MSP or admin |
| Security (endpoint) | Microsoft Defender for Business | Per user, monthly | $3 per user a month, included in Business Premium | MSP or admin |
| Operations layer | Action1 patching; OpenFrame | Free tier or per device | Action1 free for the first 200 endpoints; OpenFrame $1 per device a month | In-house admin or MSP |
| Labor | One systems administrator | Salary plus benefits | $99,130 median pay, about $153,614 loaded | In-house |
Vendors named: Microsoft, AWS, Ubiquiti, Backblaze, Action1 and OpenFrame, all list prices as published in October 2026. The labor line comes from the Bureau of Labor Statistics, not a vendor.
Now put a 50-person company through it, with one laptop per person and no cloud PCs. Microsoft 365 Business Premium for 50 users is $13,200 a year. Endpoint backup for 50 computers is $4,950. Two mid-size Windows servers in Lightsail come to $2,976. A UniFi Dream Machine Pro and four U7 Pro access points are $1,135 once. Operations tooling at $1 per device is $600. That's about $22,861 in year one.
One in-house systems administrator costs more than six times that. The BLS median pay for network and computer systems administrators was $99,130 in May 2025. Benefits made up 30% of private-industry compensation in June 2026, which works out to 43% on top of wages. Add hardware, training and recruiting and you reach about $153,614 a year, the same loaded figure we use in our outsourced IT support breakdown.
So labor is about 87% of this company's infrastructure bill. Tool prices get the attention in vendor comparisons. The person running the tools is the line that decides the budget.
The table also leaves a few lines out on purpose, because they don't have a clean list price. Laptops themselves are a hardware refresh every few years. The internet connection depends on your street. Line-of-business software, the accounting or practice-management app your team lives in, is priced per vendor and per seat. Cyber insurance is priced on your controls, and insurers ask about multi-factor sign-in and backups on the application. Add those to your own sheet. They change the total, but they don't change which layer costs the most.
Cloud versus on-premises gets framed as one company-wide decision. It works better as seven small ones, one per layer.
Identity and email are the easiest layers to move to the cloud, and the hardest to justify bringing back. Microsoft 365 or Google Workspace runs the servers, patches them and keeps them up. Endpoint backup and patching tools are cloud-managed by default now too, even when the devices sit in an office.
Network stays on-site, because the cables and access points are in your building. The management console can live in the cloud, as UniFi's does, but the hardware doesn't move.
Compute is the layer that splits. A file share fits SharePoint. An old client-server accounting app may not, and moving it means paying for a cloud server that runs around the clock. A Windows Lightsail server with 16 GB is $124 a month, or $1,488 a year, for as long as you keep it. Compare that to the cost of a small physical server over its five-year life, plus the power and the person who replaces its disks.
That leaves a typical small company hybrid. Identity, email, files and backup in the cloud. Network on-site. One or two servers wherever the app that needs them runs best. IBM's explainer below covers the hybrid model in plain terms.
A cloud server also bills differently from a physical one. You pay every month it exists, whether anyone logs in or not, and data leaving the cloud can carry its own fee. A physical server is paid up front and then costs power, cooling, spare parts and someone's afternoon when a disk fails. Neither one is cheaper in general. The cheaper one is whichever matches how long you'll run the app and how much data moves in and out.
Three questions settle the compute call for each app. Does the vendor of the app offer a SaaS version? If yes, take it and retire the server. Does the app need low latency to devices in the office, like a label printer or a scanner? If yes, keep it on-site. Will you still run it in five years? If not, a monthly cloud server you can switch off beats hardware you'll have to write down.
Hybrid also means two places to monitor. If you run servers on a shelf and in a cloud region, you need one view across both. Our guide to infrastructure monitoring covers what to watch on each side.
The second decision per layer is who runs it. There are three answers: your own staff, a managed service provider, or the SaaS vendor itself. Company size decides more of this than any feature list.
At 10 people, nobody on staff should be the IT person by accident. Identity, email and backup go to SaaS vendors, and a small MSP plan or a per-hour contractor configures them. There are no servers to run, so there's nothing that needs a full-time admin.
At 50 people, the math gets close. A fully managed MSP plan at the $165 per user midpoint from our outsourced IT support breakdown costs about $99,000 a year. That's roughly $55,000 less than one loaded systems administrator, and it usually includes 24/7 coverage, patching and endpoint protection. At that rate, the provider stays cheaper than one admin up to about 78 employees. Past that, a hire starts to make sense.
A single in-house admin also brings a risk that the price comparison hides. One person means one set of hands for vacations, sick days and the 2 a.m. outage. Everything that person knows about your firewall rules and backup schedule lives in their head unless someone writes it down. If you go in-house at 50 to 80 people, budget for documentation and an MSP on call for cover, or the savings disappear the first week your admin is out.
At 250 people, you have an in-house team. The question shifts to which layers you hand off. Co-managed IT fits here: your team owns identity, devices and the operations layer, and an MSP takes after-hours monitoring, security assessments and one-off projects.
Here's how ownership usually shifts by company size:
| Layer | 10 staff | 50 staff | 250 staff |
|---|---|---|---|
| Identity, email and files | SaaS vendor, set up by MSP or contractor | MSP or first IT hire | In-house team |
| End-user devices | MSP | MSP or in-house admin | In-house team |
| Compute and storage | None, SaaS only | MSP | In-house, MSP for projects |
| Network | Local installer | MSP | In-house team |
| Backup and recovery | SaaS vendor, checked by MSP | MSP | In-house, MSP for restore tests |
| Security monitoring | Bundled in MSP plan | MSP | Co-managed with MSP or MSSP |
| Operations layer | MSP's tools | MSP's tools or your own | Your own tools |
The row that moves the most is the operations layer. At 10 people you use whatever tools the MSP brings. At 250 you want to own them, so your device history and scripts stay with you if the provider changes.
That split matches what IT managers report. In a September 2026 r/ITManagers thread on when outsourcing makes sense, the top answer pointed at project work that comes up rarely, such as hypervisor or email migrations, plus security assessments where you want outside eyes.
Per-user MSP plans grow with every hire, while one salary stays flat until you need a second person. Our post on managed IT services pricing breaks down the per-user, per-device and tiered models, so you can check which one your quote uses.
Servers, cloud and network get most of the attention in infrastructure planning. Patching, remote access and ticketing are easier to overlook, yet every other layer depends on them.
The operations layer is also where small stacks grow by accident. A typical small-company setup ends up with one tool for monitoring, another for patching, a third for remote access, a ticketing system, a documentation wiki and a script folder on somebody's laptop. Each one has its own login, its own agent on every device and its own renewal date.
Two costs follow. The first is the bill: separate per-device or per-technician fees that add up across five or six products. The second is time. Every ticket starts with opening three consoles to find out which machine it is, what's installed and whether last night's patch landed.
So when you price IT infrastructure solutions, count the operations tools as a layer of their own. Ask how many agents run on each laptop, how many consoles a technician opens per ticket, and which tool holds the device inventory everyone else trusts. If the answers are "four", "five" and "nobody's sure", that's the layer to consolidate first after identity.
You can audit this layer in an afternoon. Open the software list on one managed laptop and count the management agents: RMM, patching, remote access, endpoint protection, backup. Then list every console your admin or MSP logs into during a normal week, and the renewal date and per-device price of each. Last, pick five random devices and check whether every tool agrees on what they are, who uses them and when they last patched. Where the tools disagree, the inventory nobody trusts is costing you time on every ticket.
OpenFrame, an open, AI-native infrastructure layer for IT and security, runs scripts across a fleet and keeps the device inventory for $1 per device a month, with a 14-day free trial (see pricing); backup and endpoint protection stay separate rows in your budget.
A provider quote usually lists services. It rarely lists what happens when you leave, who holds the keys, or how the price moves when you hire. These are the questions that surface it:
The credentials question is the one that saves the most pain later. A provider that keeps sole global admin over your tenant holds every card at renewal time, whether it means to or not. For a wider vetting checklist, see our guide to IT management for small businesses.
You can't buy every layer at once, and you shouldn't. Fix them in the order an attacker or an outage would find them.
Multi-factor sign-in for everyone, separate admin accounts, and conditional access if your license covers it. Business Premium includes Entra ID P1, so a company already on Microsoft 365 often pays only the difference between plans. This is the cheapest layer to fix and the one with the biggest blast radius.
Back up endpoints, servers and cloud data, keep one copy the attacker can't delete, and run a test restore. Endpoint backup at $99 per computer a year is small next to a single lost week of work.
Get patching, inventory and remote access into as few tools as possible. You can't secure devices you can't see, and you can't patch what isn't in the inventory. This is also where your admin's or MSP's hours go, so it's where consolidation frees up the most time.
Replace the consumer router, split guest Wi-Fi from the office network, and keep firmware current. The hardware is a one-time cost, so plan it into the budget year it's due.
Move what fits to SaaS, then decide on the rest one app at a time. Servers come last because they're the slowest and most expensive to change, and the first four layers protect them while you decide.
Put the result into a yearly plan with a line per layer. Our IT budget template has the rows already set up.
IT infrastructure solutions come down to seven decisions. Price each layer, name its owner, decide cloud or on-site per layer, and buy in order: identity, backup, operations, network, compute. For a 50-person company, the tools are about $22,861 a year at list price. The person or provider running them sets the budget, so put the most effort into that choice.
Read next: our breakdown of small business IT costs for the support side of the same budget.
Solution Architect
I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.
Still deciding?
Ask Mingo answers from our docs and customer stories.
Still deciding?
Ask Mingo answers from our docs and customer stories.