Skip to main content

Announcement: Changes to Stream Templates after November 3rd, 2025.

  • October 30, 2025
  • 2 replies
  • 72 views
Everton Colling
Expert ⭐️⭐️⭐️⭐️
Forum|alt.badge.img

Hi everyone,

As we prepare for the General Availability (GA) release of Records in CDF, we're implementing important changes based on learnings from the Private Beta. These changes will take effect on November 3rd, 2025.

What's Changing

Stream Limits per CDF Project:

  • Active streams: reduced from 10 to 3
  • Soft-deleted streams: reduced from 100 to 30

Stream Templates: We're streamlining from 6 private beta-phase templates to 3 templates:

  • ImmutableTestStream - for experimentation only
  • BasicArchive - for perpetual data storage (immutable)
  • BasicLiveData - for production usage (mutable)

The following beta templates will no longer be available for new stream creation:

  • ImmutableDataStaging
  • ImmutableNormalizedData
  • ImmutableArchive
  • MutableTestStream
  • MutableLiveData

If you're using ImmutableTestStream, note that the template capacity has been significantly reduced. The maximum total records decreased from 5B to 50M, and the maximum total data volume decreased from 500GB to 50GB.

Existing streams will retain their current profiles, but you will not be able to create new streams using beta templates starting November 3rd. If you currently have more than 3 active streams, you'll need to reduce to 2 or fewer active streams to create new ones. You can delete streams at any time, as long as you stay under 30 soft-deleted streams per project.

In H1 2026, we'll be introducing additional stream templates with higher limits as part of different service tiers, giving more flexibility for larger deployments.

    2 replies

    J
    Seasoned ⭐️⭐️⭐️
    • Jan Dolejsi
    • Seasoned ⭐️⭐️⭐️
    • October 30, 2025

    Fewer options (stream templates) is going to make the product come across better. Easier to grasp for newcomers.
    But 100x less capacity (50M records) is most likely disqualifying Streams for the first use case that we started testing it for. We would not fit the data structure we planned to store. Will see if we can downscale it first, but downscaling (i.e. grouping+aggregation queries) was a good promise Streams were making, so shame we could not use Streams for what it is strong at.

      Everton Colling
      Expert ⭐️⭐️⭐️⭐️
      Forum|alt.badge.img
      • Everton Colling
      • Author
      • Expert ⭐️⭐️⭐️⭐️
      • November 3, 2025

      Hi Jan,

      Thank you for the feedback! I completely understand your concern about the capacity reduction impacting your use case.

      To clarify: the limits announced for GA represent the baseline limits that will be available to all CDF projects starting November 3rd. These are designed to support the majority of use cases while we work toward a more scalable pricing and service tier structure.

      However, we do recognize that some customers have requirements for significantly higher data volumes, and that was one of the reasons why the Records service was created. If your use case requires higher capacity and you're planning to use the Records service after the GA release, please reach out to your Cognite representative (for SLB, that would be ​@Aditya Kotiyal) with more details on what are the limits you would need.

      As long as your requirements align with the limits we extensively tested during the Private Beta (hundreds of millions of records for mutable streams or billions of records for immutable streams) we should be able to enable higher limits for your specific CDF project on an exception basis.

      As I mentioned above, later in H1 2026 we'll be introducing additional stream templates with higher limits as part of different service tiers, giving customers more flexibility for larger deployments.

      Given your mention of needing to store large data structures with aggregation capabilities, I'd encourage you to connect with your account team to discuss your specific requirements. We want to make sure Records can still work for use cases like yours.

        Terms & ConditionsAccessibility statement