live wire
▸AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat Developer▸AI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat Developer▸CLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat Errata▸PLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat Errata▸SECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat Errata▸AI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data Hub▸AI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat Developer▸SECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat Errata▸AI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat Developer▸AI · Red Hat maps silent tool-call failures across agentic pipelinesRed Hat▸API · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrant▸AI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM Research▸JAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errata▸AI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM▸AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat Developer▸AI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat Developer▸CLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat Errata▸PLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat Errata▸SECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat Errata▸AI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data Hub▸AI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat Developer▸SECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat Errata▸AI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat Developer▸AI · Red Hat maps silent tool-call failures across agentic pipelinesRed Hat▸API · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrant▸AI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM Research▸JAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errata▸AI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
newsAI

IBM puts Granite time-series inference inside Confluent Cloud’s streaming SQL

Four compact Granite models enter early access through Flink SQL, keeping forecasts and anomaly detection in the same governed pipeline as Kafka data.

Flink SQL streaming AI with four Granite models in and out of Kafka
Side by side: what changed
By The News Desk· Sep 1, 2026the quick take — two AI hosts, this story only

IBM and Confluent have opened early access to four Granite time-series foundation models inside Confluent Cloud, making forecasting and anomaly detection callable from the same Flink SQL pipelines that process live Kafka data. The IBM announcement says the initial service runs on Confluent Cloud on AWS, with Confluent Platform support for on-premises and hybrid deployments planned later.

What changed

The integration exposes IBM’s models through Confluent’s existing AI_FORECAST and AI_DETECT_ANOMALIES Flink SQL functions. Teams can switch among the supported models without redesigning the surrounding streaming pipeline, while Confluent manages serving infrastructure, scaling and runtime operations.

The early-access set includes PatchTST-FM-r1 for probabilistic forecasts, FlowState-r1.1 for point forecasts, TTM-r3 for efficient processing of many series with control variables, and TSPulse for anomaly detection, classification, similarity search and gap filling. IBM describes the models as ranging from 1 million to 260 million parameters and requiring no GPU.

Inference results are written back to Kafka topics. That lets alerting systems, dashboards, lakehouses and AI agents consume the output without a separate handoff from a machine-learning environment. IBM also says those inference pipelines inherit the platform’s schemas, lineage and access controls, while Kafka’s replayable topics provide a record for audits, troubleshooting and model evaluation.

Who it affects

The immediate audience is data-streaming teams that already use Confluent Cloud and Flink SQL but have treated forecasting as a separate workload. IBM’s examples include scoring payment activity before a transaction completes, forecasting demand across product catalogs, monitoring industrial telemetry and comparing current signals with historical patterns.

The design also matters to platform teams trying to reduce the operational boundary between event processing and model serving. Small CPU-capable models can sit closer to the stream than a general-purpose GPU inference service, although the early-access label means teams should treat the interface and deployment limits as subject to change.

What to do

Confluent Cloud users can enroll in the early-access program and test the SQL functions against non-critical streams. A useful evaluation should compare forecast quality and anomaly sensitivity across the four models, then verify how results, schemas and lineage appear in downstream Kafka topics.

Hybrid and on-premises teams cannot use the announced Confluent Platform path yet. They can still evaluate whether the proposed architecture fits their governance model, but IBM gives no availability date for that support. Production adoption should wait for service-level, pricing and support details that the announcement does not yet provide.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk