Overview
Crogl is AI for the enterprise SOC. It investigates every alert. It documents every action. Your analysts review the evidence and make the call.
Free and Enterprise
This AMI carries no software license charge. Free is for one user and remains free. It includes all connectors, unlimited skills, unlimited audit trails, username and password access, and direct access to Crogl engineers in the community Slack. You bring your own LLM provider credentials, and your model provider bills that usage. Enterprise is for SOC teams running Crogl around the clock. The paid annual plan adds unlimited users and investigations, autonomous investigation and threat hunting, single sign-on, role-based access control, and audit log export. It also covers use of your enterprise LLM service and dedicated support with agreed service levels. Pricing is custom and team based. No per-alert, per-investigation, or per-user fees. Free and Enterprise run the same core platform. The plan determines the features and access available to your team.
What an investigation looks like
An alert lands. Crogl pulls the host and identity context, queries your EDR for process lineage, and checks the authentication record. It pivots to your data lake for anything the SIEM did not retain, then reads the relevant threat advisory. It writes down every query it ran and every result it got back. Your analyst opens the investigation, sees the reasoning, redirects it, and decides what happens next. Crogl handles the investigation. The analyst makes the call. Crogl records the work in your ticketing or case management system. Auditable, repeatable, inspectable. Every investigation is an artifact you can hand to an auditor, a regulator, or your board.
Works where the data lives
Crogl queries your SIEM, EDR, identity, cloud, data lake, ticketing, and threat intelligence sources in their native formats, without schema normalization. There is no pipeline to build and no index to populate first. You can build connectors and skills for your own tools and workflows. You bring your own model. Crogl runs against the LLM service you choose and host, including models that stay inside an air-gapped boundary.
Deployment
This AMI runs on Amazon EC2 in your AWS account. You control the deployment, its connections to your tools, and its connection to your model services. Most teams reach their first investigation within minutes of first login. Crogl also runs on premises, in private cloud, and in air-gapped environments. Contact Crogl for those options.
In production today
One defense organization runs Crogl against 60,000 alerts per month across 100TB of data, three SIEMs, and two SOARs, at an impact equivalent to six full-time analysts. Crogl is built for the hardest security environments.
Request Enterprise pricing
Enterprise is purchased through a private offer on the Crogl - AI for Enterprise Security solution in AWS Marketplace. That solution includes this AMI and Crogl Annual Production Support. Open that listing and select Request private offer, or contact Crogl at sales@crogl.com . Licensing and support terms are specified in your Enterprise agreement. AWS infrastructure and model services are billed separately.
Highlights
- Investigates every alert. Documents every action. Crogl pulls host and identity context, queries your EDR, pivots to your data lake, and reads the advisory, writing down every query and result. The analyst reviews the reasoning and makes the call.
- Works where the data lives. Crogl queries your SIEM, EDR, identity, cloud, and data lake in their native formats, without schema normalization. No pipeline to build. Bring your own model, including one hosted inside an air-gapped boundary.
- Free is for one user and remains free: all connectors, unlimited skills, and community Slack access to Crogl engineers. Enterprise adds unlimited users, autonomous investigation, SSO, RBAC, and dedicated support. Request pricing on the Crogl solution.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
There are no refunds available for using this product.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
2.16.0 Crogl 2.16.0 connects AWS OpenSearch and Wiz, reaches Sentinel and Log Analytics in Azure Government, and runs your models through OpenRouter. Reading a conversations transcript moves to its own endpoint, so update anything that scripts it before you upgrade.
Bug Fixes A crogl command whose cached token the server rejects signs in again and retries once. A custom API connector can authenticate with the OAuth2 password grant, and an OAuth2 connection test tells a refused token request from a failed one. A connector reply that is not the JSON it expects is reported as the failure it is, and what it quotes back is bounded. A scheduled run whose agent container cannot start for want of capacity is retried before it fails. The Kubernetes page now covers sizing a cluster so agent pods have room. Outstanding dependency vulnerabilities are remediated.
Additional details
Usage instructions
Retrieve Initial Credentials: After the first boot completes, Crogl writes a one-time credentials file containing the admin password and the startup key. SSH into the instance to retrieve them:
ssh -i your-key.pem ubuntu@<public-ip> sudo cat /root/installation-artifacts.txt
Access the Crogl UI: Open https://<public-ip-or-dns>:4043 in your browser. Accept the self-signed certificate warning (or install a CA-signed certificate). Log in with the admin username and password retrieved from the installation-artifacts.txt file. On initial login, the Crogl UI will guide you through configuring an LLM provider and at least one connector. Have your LLM API key and connector credentials ready before proceeding.
Support
Vendor support
Users of Free can get help and support through the Crogl Community. Sign up for the community here: <www.crogl.com/community >
For Enterprise users, support options are available with the purchase of an enterprise license. Enterprise is purchased through a private offer on the Crogl - AI for Enterprise Security solution in AWS Marketplace. That solution includes this AMI and Crogl Annual Production Support. Open that listing and select Request private offer, or contact Crogl at sales@crogl.com . Licensing and support terms are specified in your Enterprise agreement. AWS infrastructure and model services are billed separately.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Customer reviews
Layered security has protected our nonprofit websites and gives ongoing assurance against attacks
What is our primary use case?
My primary use case is that I run two websites on a single AWS EC2 instance. They're both based on WordPress. I'm using Crogl basically for security for that website. This includes the WordPress sites, plugins as an application layer security. I have EngineX and I get data from AWS Inspector. Then I have it all going into a single Splunk instance. Crogl is getting its data only from Splunk at the moment. I'm using it to protect that website because the website constantly gets attacked from bot traffic and from different adversaries all over the world.
I have security in depth, so in different layers. The first one is at a network layer inside of AWS itself. On the outside, I protected it that way. The second one is through different rules I have configured on my web server itself. Then I have to run WordPress. I also have different plugins that are installed that give me another application layer of security. In particular, it's called Wordfence. That's what I use as an addition. I use a combination of all of those things to protect it.
Geographical or sovereign rules don't really apply to me because I'm based in the US and I don't have anything regarding any necessarily rules or regulations that I have to follow regarding a different region. I do have Cloudflare in place. I get data from that as well.
How has it helped my organization?
I noticed a lot of traffic with a lot of bots attacking the site at once. My concern was making sure that no plugins or files were installed on the server because from what I can tell on Splunk, that's what they were looking to do—basically infect my server with malware or malicious plugins inside of WordPress. Within minutes I had it installed and within seven minutes, I had an answer that says I was secure.
The skill itself is what I go back to now. Only on occasion will I go and look at my actual Splunk instance. The skill will constantly look at the data that Splunk has and just reassure me that I have everything I need and that it's secured.
What is most valuable?
Crogl tells me if my layers are properly configured. First of all, it confirms whether I have security in depth with the different layers. The second thing I appreciate is that I now have a skill built within the platform that gives me ongoing assurance that my sites remain protected. I did a one-time assessment with it using all the data I have in Splunk, but now that I have a skill configured, I can go back to that and it lets me know that I'm still protected. For example, that recent PHP vulnerability that came out a week or two ago was a perfect test for my skill. I upgraded my PHP on my Linux server, but then I reran the skill to make sure that everything was still secure and I had an answer right away. To have that available is invaluable.
I was able to get a report. I did mine in markdown so I had it to document it. I just used Crogl's interface to generate it for me. I didn't do anything special.
What needs improvement?
The only downside that I've seen so far regarding Crogl were two things. The install process has already been corrected from their earlier versions. You do have to be a developer that understands Docker and how to get that set up. It's not a downside for me personally, but that's one thing. The other thing was when you set up a connector, you can only set up a single connector to one Splunk instance. For me personally, I don't feel it's an issue, but for others that are using multiple Splunk instances, they may need multiple connectors to different instances, not just a single Splunk instance.
For how long have I used the solution?
I started the review process roughly five months ago last summer.
What do I think about the stability of the solution?
I haven't experienced any stability issues when I used Crogl. Keep in mind my usage is pretty low. I don't tax it because I have a small Splunk instance and for a single site. My source is Splunk even though it's aggregating all my data.
What do I think about the scalability of the solution?
Because it's a microservice, I would expect it to be scalable. I'm only running a single instance in Docker, but I'm sure it's supported on Kubernetes.
How are customer service and support?
I used the community site that they have on Slack. It was fine. Anytime I needed support, I got an answer fairly quick, especially it being a community site and it was from somebody at the company. I'd rate Crogl a nine.
Which solution did I use previously and why did I switch?
I've seen Crogl work in different ways, but for me to have it installed locally and not the data in the cloud, that's different for me.
How was the initial setup?
Crogl tried to do too much, assuming that non-developers might attempt to use it when I think you're going to have some basic background. Anybody that uses it is going to have a background in Docker and how to configure it and run basic containers and services. I think they now just state their prerequisites ahead of time and then you just run the product within Docker. They tried to do too much before and I don't think it was overkill. They just state the prerequisites with it now and everything goes smooth.
It wasn't difficult at all. The documentation is embedded, but only after you do the install. Once you have it installed, then the documentation is available. I've actually submitted a request to make that documentation more public after the fact. It was self-explanatory because the documents run you through it. When I was building my skill, for example, I used the documentation to do that.
What's my experience with pricing, setup cost, and licensing?
I'm using the free version of Crogl right now.
Which other solutions did I evaluate?
I applied for other non-profit licenses to be used with other vendors' products. I wasn't able to get that license. Others I have, Splunk gave me a non-profit license to use.