we are using a licensed version of the product. 

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 pricing structure depends on the scalability steps. It begins as quite affordable and maintains affordability for a while. However, there's a turning point where it transitions from being reasonably priced to becoming notably expensive.

The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower. 

However, if you're dealing with high volumes, you'll need to reconsider the cost-effectiveness. If there are no challenges or bottlenecks in buying a service from a cloud service provider, that might be a viable option. 

But if you're concerned about price or issues like exposing your data to the public cloud, then deploying on-premises and conducting stress testing becomes important. It’s a part of the learning and development process, not just a deployment for production. 

You need to pass through testing processes in the development environment and then move to staging and production. This involves various tests to understand user access patterns, data push, and performance assessment. Deploying on your own requires considering all these factors. On the other hand, if you use a cloud service, many of these concerns aren't your responsibility.

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. 

I'm not sure of the exact licensing costs. I don't deal with that aspect of the solution. 

The price we pay for Elastic Enterprise Search is very high. We have a complicated banking project with a lot of components, developers, and features. 

On a scale of one to 10, with one being very cheap and 10 being very expensive, I would rate this solution an nine. Their pricing system is highly complex. 

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.

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

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 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.

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 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.

This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic.

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

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 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 started with the open-source version and the price increases as you add nodes because it's node-based. The price kept increasing, so we decided to buy a license to get all the features and manage the clusters more efficiently. The price of Elastic Enterprise is very, very competitive. I think it was around $700. It was very cheap for our budget. We have other solutions from other vendors that are way more expensive.

The beauty of Elastic Search is that it's based on an open-source solution, so even if you don't want to keep your license, you can just switch it off and go back to the open-source version. You'll lose some of the features, but your data will still be there, and you'll still be able to manipulate it.

You can scale the pricing up and down, which is great flexibility for us because we are a government organization. When it comes to invoicing and payment, the government is a little slow. For example, we found that our license expired on December 31st, but the vendor still hadn't been paid, so they would not issue us a new license. We switched our license off and went back to open source mode until we were able to get our license again and switch back to Enterprise.

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

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.

To access all the features available you require both the open source license and the production license.

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 tool is not expensive. Its licensing costs are yearly. 

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 solution is not expensive because users have the option of choosing the managed or the subscription model. 

The price could be better.

ELK has been considered as an alternative to Splunk to reduce licensing costs.

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

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.

We are using the open-source version. 

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

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.

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

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.

The solution is free.

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. 

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

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.

The pricing of this solution is not clear.

The pricing and license model are clear: node-based model. 

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