Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content

What is the ELK Stack? Self-hosted logging for MSPs and IT teams

Open Source
Open Source MSP
September 29, 2026
540 views
What is the ELK Stack? Self-hosted logging for MSPs and IT teams

What the ELK stack is and how it differs from the Elastic Stack and OpenSearch, how the architecture fits together, a five-step Docker install, why the license changed twice, what self-hosting and Elastic Cloud cost, and a side-by-side with OpenSearch and Grafana Loki.


Updated: November 2026

Every server, firewall and laptop you manage writes logs, and nobody reads them until something breaks. The ELK stack is the open-source toolkit teams reach for to pull those logs into one place they can search. Here's what each piece does, what running it yourself costs an MSP or a small IT team, and when OpenSearch or Grafana Loki is the better fit.

What is the ELK Stack?

The ELK stack is a log management platform built from three open-source tools: Elasticsearch, Logstash and Kibana. Elasticsearch stores and searches the data. Logstash collects logs from many sources, cleans them up and sends them on. Kibana is the web interface where you search, filter and build dashboards. Together they turn scattered log files into one searchable record.

The name stuck, but the stack grew. Elastic added Beats, small agents that ship data from each machine: Filebeat for log files, Metricbeat for metrics and Winlogbeat for Windows event logs. With Beats in the picture, Elastic now calls the whole thing the Elastic Stack. Search results still say ELK, and so does everyone on a help desk.

What each letter does

ComponentWhat it doesWhere it runs
Elasticsearch (E)Stores every log line and indexes its fields so searches come back in secondsOne or more server nodes
Logstash (L)Collects, parses and enriches logs before they are stored; optionalA server between the agents and Elasticsearch
Kibana (K)The web interface for searching logs and building dashboardsA server your techs open in a browser
Beats or Elastic AgentShips logs and metrics from each machineEvery server, PC or VM you watch

Newer installs often swap the separate Beats for Elastic Agent, one agent per host that collects logs, metrics and security data. You manage those agents from Fleet, an app inside Kibana, instead of editing a config file on every machine. Beats still work and still ship to Logstash or Elasticsearch, so older guides stay useful.

All four parts share one version number. Elasticsearch 9.5.6, released on 2 November 2026, is current as of this update, and Kibana, Logstash, Filebeat and Elastic Agent ship as 9.5.6 too.

ELK Stack vs Elastic Stack vs OpenSearch

Three names, two codebases. ELK and Elastic Stack are the same product from the same company, and OpenSearch is the fork.

NameWhat it isWho runs itLicense
ELK stackThe original three: Elasticsearch, Logstash and KibanaElasticAGPL, SSPL or Elastic License
Elastic StackELK plus Beats and Elastic Agent, and the official name todayElasticAGPL, SSPL or Elastic License
OpenSearchA 2021 fork of Elasticsearch 7.10 and Kibana, with OpenSearch Dashboards in place of KibanaOpenSearch Software Foundation, part of the Linux FoundationApache 2.0

So when a guide says ELK and another says Elastic Stack, they mean the same thing. When it says OpenSearch, the APIs look familiar, but versions, plugins and licenses have drifted apart since the split. The license story below explains why the fork happened.

What ELK means for MSPs and IT teams

For an in-house IT team, ELK usually means one cluster for the company's servers, firewalls and Windows event logs, owned by whoever knows Linux best. For an MSP, the first design question is how to keep each client's logs apart. A cluster per client is simple to reason about and costs more to run, while one shared cluster needs index names and access roles planned per client from day one.

How the pieces fit together

Think of it as a pipeline with four stops. A Beat on each server reads the logs and ships them. Logstash, if you use it, parses them, so a raw firewall line becomes fields like source IP, port and action. Elasticsearch indexes those fields so a search across millions of lines comes back in seconds. Kibana sits at the end, where a tech types a query or opens a dashboard.

Logstash is optional for simple setups. Beats can send straight to Elasticsearch, and teams often add Logstash later, once they need to reshape messy sources like syslog from network gear. That's the trade: Logstash is flexible, and it's also one more service to run and patch.

This three-minute explainer from May 2026 walks through the same flow, one component at a time.

ELK Stack architecture

Under the pipeline sits a cluster. Each Elasticsearch server is a node, and nodes join into a cluster that shares the data. Logs land in indexes, usually one per day or per source. Each index splits into shards, and each shard can have a replica copy on another node, so losing one server doesn't lose the data.

A small team can start with one node and live with the risk. For a cluster that survives a failed server, plan for three nodes: the cluster needs a majority of its master-eligible nodes up to keep working, and three is the smallest number where one can fail. These are the default ports you'll open between the parts.

PortServiceWho connects
9200Elasticsearch HTTP APIKibana, Logstash, Beats, your scripts
9300Elasticsearch transportOther Elasticsearch nodes in the cluster
5044Logstash Beats inputBeats agents sending to Logstash
5601Kibana web interfaceTechs in a browser

Keep 9200 and 9300 off the internet. An exposed Elasticsearch API is how clusters end up in data-leak headlines.

What small IT teams use it for

The first use is plain troubleshooting. When a service fails across 30 servers, searching one Kibana screen beats SSH-ing into each box and grepping. You filter by host, time window and error level, and the pattern shows up in minutes.

The second is security. Failed logons, new admin accounts, blocked connections: once Windows event logs and firewall logs sit in the same index, you can see them side by side. Elastic ships a security app on top of the stack, so a team can grow from log search toward SIEM-style detection without starting over.

The third is keeping records. Plenty of audits ask how long logs are retained and whether anyone can change them. A central store with a written retention policy answers that better than logs rotating off individual machines.

Is it still the default choice? This December 2025 r/devops thread asks exactly that. Replies say ELK is still actively developed and widely used, especially at scale, while teams on managed Kubernetes often lean on their cloud provider's log tools and newer setups move toward OpenTelemetry.

Free to run, complicated to license

You can download and self-host it at no cost. What changed over the years is whether it counts as open source, and the history matters if you care about that.

Elasticsearch and Kibana started under the Apache 2.0 license. On 14 January 2021, Elastic announced that from version 7.11 both would move to a dual license: the Server Side Public License (SSPL) and the Elastic License. Neither is an open-source license by the usual definition. The move was aimed at cloud providers selling Elasticsearch as a service.

AWS answered by forking the last Apache-licensed version into OpenSearch in 2021. On 16 September 2024, the Linux Foundation launched the OpenSearch Software Foundation, and AWS handed the project over. OpenSearch stays under Apache 2.0.

Then Elastic moved again. On 29 August 2024, founder Shay Banon wrote that Elastic would add AGPL as a third license option, so "Elasticsearch and Kibana can be called Open Source again." The older licenses stay available alongside it.

For a small team self-hosting for its own use, any of these licenses works. The difference shows up if you plan to offer the stack as a service to others, or if your policy only allows OSI-approved licenses.

What running it yourself costs

The software is free. The hardware and the hours are not, and that's where small teams get surprised.

Elasticsearch indexes the fields of every log line so searches come back fast. That speed costs disk and memory. Log volume grows with every server you add, and the index grows with it, so storage fills faster than the raw log files would suggest.

Then there's upkeep. Someone has to size the Java heap, plan shards, set retention so old indexes get deleted, turn on authentication and TLS, and run version upgrades without losing data. None of this is exotic. All of it lands on whoever set the cluster up, usually a tech with other tickets.

A retention policy is the single cheapest fix. Decide how long each log type needs to live, write it down, and let Elasticsearch's index lifecycle management delete the rest on schedule.

Hosted ELK, where someone else runs the cluster

If upkeep is the blocker, you can pay to skip it. Elastic Cloud Hosted runs the Elastic Stack for you on AWS, Azure or Google Cloud, and Elastic Cloud Serverless drops cluster sizing altogether and bills by data instead.

Per Elastic's published Serverless pricing, read on 4 November 2026, the Logs Essentials tier starts at $0.07 per GB ingested and $0.017 per GB retained each month, and the first 50 GB of egress each month is free. Hosted bills grow with log volume, so the retention policy above saves as much money in the cloud as it does on your own disks.

The other common managed route is Amazon OpenSearch Service, which runs OpenSearch, the Elasticsearch fork covered below, with OpenSearch Dashboards in place of Kibana.

How to install the ELK Stack

The quickest test drive is Elastic's start-local script. Running curl -fsSL https://elastic.co/start-local | sh starts Elasticsearch and Kibana in Docker on localhost ports 9200 and 5601, with a one-month trial license. Elastic's own docs say not to use it for production.

For a single-node test you control, Elastic's Docker guide comes down to five steps.

  1. Create a network with docker network create elastic.
  2. Start Elasticsearch with docker run --name es01 --net elastic -p 9200:9200 -it -m 1GB docker.elastic.co/elasticsearch/elasticsearch:9.5.6. On first start it prints the elastic user's password and a Kibana enrollment token, once, so copy both.
  3. Start Kibana with docker run --name kib01 --net elastic -p 5601:5601 docker.elastic.co/kibana/kibana:9.5.6, open the link it prints, paste the token and log in as elastic.
  4. Ship logs from one server: install Filebeat and point it at Elasticsearch, or set up Fleet with a Fleet Server and enroll Elastic Agent.
  5. Add an index lifecycle policy that deletes old indexes, say after 30 days, before you add a second source.

Give Docker Desktop at least 4 GB of memory for this. Elastic labels the single-node setup for development and testing. A production cluster needs more nodes, backups (Elasticsearch calls them snapshots) and a plan for upgrades, which is the upkeep described above.

ELK vs OpenSearch vs Grafana Loki

Three open options come up again and again for self-hosted logs. They split on license and on how much they index.

ELK (Elastic Stack)OpenSearchGrafana Loki
LicenseAGPL, SSPL or Elastic License (your choice)Apache 2.0AGPLv3 (since April 2021)
What it indexesEvery field of every log lineEvery field (Elasticsearch-compatible)Labels only; log text is compressed and stored
Storage costHigherHigherLower, uses object storage
Search speedFast full-text searchFast full-text searchFast by label, slower when scanning text
GovernanceElastic, a single companyLinux FoundationGrafana Labs, a single company

Loki is the one that changes the math. Grafana relicensed it to AGPLv3 in April 2021, and it indexes only labels like host and app, not the text inside each line. That makes it cheaper to run and slower when you search for a word nobody labeled.

If Loki sounds like your fit, our Grafana Loki review covers it in depth.

In this r/devops thread, a team handling 50 to 100 GB of logs a day asks whether to move from Elasticsearch to Loki. The top answer, from someone who has run both, would pick Loki for a new build today. Another explains the trade: Elasticsearch pre-indexes everything so searches are quick, while Loki's object storage is cheaper but slower to query.

Which one fits

Pick ELK if your team searches free text often, wants Kibana's dashboards, and has someone who can own the cluster. Guides and community answers are easy to find, and Elastic's security app gives you a path toward detection later.

Pick OpenSearch if you want the same search model under a license run by a foundation rather than a vendor. Its interface, OpenSearch Dashboards, is a fork of Kibana, so the workflow feels familiar. It's also the base of AWS's managed service, which matters if you ever want someone else to run it.

Pick Loki if cost and simplicity come first and your team already lives in Grafana. Label your logs well, and most searches never need full-text indexing.

If the real goal is security events rather than general logs, look at a purpose-built open-source SIEM instead of building one. Our Wazuh comparison walks through that route.

If what you want is endpoint logs from every client in one place, without running a cluster, OpenFrame, the open, AI-native infrastructure for IT and security that Flamingo builds (Flamingo also runs OpenMSP), includes a logs and alerts module. It gathers events from its own agent, Fleet and osquery, and remote access sessions into one searchable Logs screen across customers, and Mingo, its IT operations agent, flags risks such as open RDP or a disabled firewall as incidents. It is a log store with early AI detection rather than a full detection SIEM. Pricing is $1 per device per month with 10M AI tokens included, or $0.80 billed yearly with 25M, with a 14-day free trial.

Start with one log source

The ELK stack is a solid, well-documented way to put every log in one searchable place, and it's free to run yourself. The bill comes in disk, memory and upkeep, so decide what you'll keep and for how long before you turn it on.

Start small: ship Windows event logs from a handful of servers, set a 30-day retention policy, and see which searches your team runs. For the lighter alternative, read our Grafana Loki review.

Kristina Shkriabina

Content Marketing Lead

Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.

Related Content

Frequently Asked Questions

/blog/what-is-elk-stack

Loading related content and questions