What is your experience regarding pricing and costs for ELK Elasticsearch?

I am not directly involved with pricing or setup costs. While I know a portion is open-source, a paid version might be necessary.

I would rate the pricing a seven out of ten, with one being high price and ten being low price. It could be cheaper for certain use cases, but since it gets the job done, no complaints for the pricing.

I would rate the pricing an eight out of ten, with one being cheap and ten being expensive. It is not very costly, but it is not cheap either.

we are using a licensed version of the product.

I use the community version. The premium license is expensive. I rate the tool’s pricing an eight out of ten.

I rate Elastic Search's pricing an eight out of ten.

Elastic Search is open-source, but you need to pay for support, which is expensive.

Elastic Search is a bit pricey, especially for individuals or small learners interested in cybersecurity. It could be more affordable for personal use, making it accessible to a broader audience learning about network security and traffic monitoring.

I use the free version. We use the free version for some logs, but not extensive use.

The tool is an open-source product.

I'd advise people to involve a team with people from different departments in order to predict the correct scale.

The developer and tester licenses are one thing that is not hurting us. However, the deployment license cost is very, very high for Elastic.

I do not have any details about the cost or licensing. That said, the cost is public, and likely, someone can search for the approximate costs online.

The solution is affordable. Previously, we wasted a lot of time by building our own system, which we could have avoided by moving to Elasticsearch earlier.

We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more. I rate the price of Elastic Enterprise Search a three out of five.

The solution is less expensive than Stackdriver and Grafana.

Since it is open-source, we don't pay licensing fees. In the development and QA environment, we don't pay anything. We, however, have to pay for all the software, subscription, pre-protection and protection.

As I use the cloud, all of the costs for me are based on customer needs. There is a fascinating calculator published in Elastic. That there is not a specific starting cost. It can move from $10,000 US Dollars per year to any price based on how powerful you need the searches to be and the capacity in terms of storage and process. That said, you can start with a small budget, implement the use cases, and start growing slowly.

The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive.

The solution is not expensive because users have the option of choosing the managed or the subscription model.

There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version.

The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have.

Although the ELK Elasticsearch software is open-source, we buy the hardware.

It's a bit too expensive, however, it's not as expensive as Splunk, which is a good thing. It's okay. There are cheaper products that we know, however, this is a very rich product, and it's got a very wide functionality, and a wide range of functionalities which I don't see in the other products, especially not in the cheaper ones.

The price could be better.

We are using the free open-sourced version of this solution.

We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition.

The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine. If you are building any cluster and you are paying €6,000 per machine, that is expensive.

The basic license is free, and it comes with a lot of features that aren't supposed to be free! With a Gold license, we get Alerting (called Watcher) and some modest enterprise features. Note that if alerting is a must feature for you, you can install open-source alerting plugins like Open Distro Alerting or ElastAlert and avoid the Gold license cost. Active Directory integration, SAML, SSO, Machine Learning etc. come with Platinum license. The licensing is per-node and per-annum basis for an on-premise installation and for Cloud Elastic-managed service the cost is baked into the hourly pay-as-you-go fee. Kibana does not have a license, so it's free. If you don't want alerting, Active Directory or LDAP integration and are good with native authentication, the basic license will suffice. The basic license also comes with many internal stack features, which are free. For example, data segregation into hot and warm storage, automatic configuration, and rolling over the index after achieving a certain size limit. SIEM (Security Information and Event Management) app is free. Also is another cool app called Uptime that helps us monitor the uptime of servers and web services. We can do this without any third-party licensing cost. Just turn on the apps, ingest data using Beats and the apps will start thriving. Over time they become mission critical to your business. For example, the SIEM app will automatically populate the dashboards and allow us to monitor network traffic, successful logins, unsuccessful login attempts, and anomalous security events. All that comes off the shelf and is free. You'll pay a lot, on the other hand, for a traditional SIEM like ArcSight or LogRhythm. Another free app called Infrastructure (formerly known as Metrics) helps monitor the server infrastructure by configuring light-weight data collectors called MetricBeats (for Windows systems) and AuditBeats (for Linux systems). The Beats will start pumping in all the system performance metrics into the stack and help monitor the memory, CPU and disk utilization.

We are using the open-source version. We are not looking into the subscription because it's on-premises in-house.

This product is open-source and can be used free of charge.

It can be expensive. When managed by AWS you have different options and features that are locked and not available to you on the Kibana and security levels. You cannot use the full X-Pack feature set when you go through AWS.

We are currently using the Open Source version, so we didn't need to offset any licensing. For now, it's just the cost of maintaining the server.

The pricing of this solution is not clear.

For the next project, we might buy the license, but we don't use it now. I don't know exactly what the license fee for Elasticsearch is currently.