<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Stroomworks blog</title>
    <link>https://www.stroomworks.com/blog/</link>
    <atom:link href="https://www.stroomworks.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>New Stroom features, notable fixes, and what is coming next.</description>
    <language>en-gb</language>
    <item>
      <title>How we built the security dashboard on this website</title>
      <link>https://www.stroomworks.com/blog/building-the-security-demo/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/building-the-security-demo/</guid>
      <pubDate>Wed, 30 Sep 2026 09:00:00 GMT</pubDate>
      <category>How I use Stroom</category>
      <description>The Security Operations dashboard in our screenshots is a real Stroom instance fed synthetic events. Here is how it is put together, and the four things that caught us out.</description>
    </item>
    <item>
      <title>What is coming in Stroom 7.14</title>
      <link>https://www.stroomworks.com/blog/whats-coming-in-7-14/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/whats-coming-in-7-14/</guid>
      <pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
      <category>Upcoming</category>
      <description>S3 storage, a rebuilt processor task system, traces as documents and JSON logging are all landing in the 7.14 betas. Here is what is ready, and what is still experimental.</description>
    </item>
    <item>
      <title>Ask Stroom AI: from a chat panel to a function you can call</title>
      <link>https://www.stroomworks.com/blog/ask-ai-functions/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/ask-ai-functions/</guid>
      <pubDate>Thu, 03 Sep 2026 09:00:00 GMT</pubDate>
      <category>AI</category>
      <description>Ask Stroom AI started as a table-summary preview in 7.11. In 7.14-beta.1 you can call a model from XSLT and StroomQL, and add AI summaries to reports.</description>
    </item>
    <item>
      <title>Two fixes in 7.14-beta.1 worth knowing about</title>
      <link>https://www.stroomworks.com/blog/processor-filter-skipped-streams/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/processor-filter-skipped-streams/</guid>
      <pubDate>Thu, 03 Sep 2026 09:00:00 GMT</pubDate>
      <category>Bug fix</category>
      <description>Processor filters could leave a stream permanently unprocessed, and bitmap-lookup ran its values together. Both are fixed in 7.14-beta.1.</description>
    </item>
    <item>
      <title>Plan B fixes in the 7.13 betas</title>
      <link>https://www.stroomworks.com/blog/plan-b-reliability-fixes/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/plan-b-reliability-fixes/</guid>
      <pubDate>Mon, 17 Aug 2026 09:00:00 GMT</pubDate>
      <category>Bug fix</category>
      <description>Histograms and metrics no longer double count after an interrupted merge, queued data survives a restart, and sends retry through a network blip.</description>
    </item>
    <item>
      <title>Signing in through an authenticating edge proxy</title>
      <link>https://www.stroomworks.com/blog/edge-authentication/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/edge-authentication/</guid>
      <pubDate>Wed, 05 Aug 2026 09:00:00 GMT</pubDate>
      <category>Feature</category>
      <description>From 7.13-beta.10, Stroom can sit behind an AWS ALB with Cognito or NGINX with oauth2-proxy, and let the proxy handle sign-in.</description>
    </item>
    <item>
      <title>Content that lives in Git</title>
      <link>https://www.stroomworks.com/blog/git-backed-content/</link>
      <guid isPermaLink="true">https://www.stroomworks.com/blog/git-backed-content/</guid>
      <pubDate>Wed, 04 Mar 2026 09:00:00 GMT</pubDate>
      <category>Feature</category>
      <description>Stroom 7.11 adds Git-controlled folders, a Content Store for standard packs, and a Credentials feature to hold the secrets both of them need.</description>
    </item>
  </channel>
</rss>
