Skip to content

Commit

Permalink
Merge pull request #278 from MoralisWeb3/streams-pricing-announcement
Browse files Browse the repository at this point in the history
streams pricing announcement
  • Loading branch information
salisbury88 authored Oct 11, 2023
2 parents e87b88d + 7024c5a commit 8950b91
Showing 1 changed file with 23 additions and 0 deletions.
23 changes: 23 additions & 0 deletions blog/2023-10-11-upcoming-change-to-streams-pricing.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
title: "Upcoming changes to Streams Pricing"
slug: "upcoming-change-to-streams-pricing"
authors:
name: Filip Martinsson
tags: [Streams API]
---

Up until now, Streams and API pricing has been separate. And all accounts on Moralis have had a certain number of Stream records included in their plan.

Today we're announcing the streamlining of Streams and API pricing. Both Streams and API moving forward will be priced in Compute Units.

Each Streams record will have a fixed price of 15 Compute Units. Which means that the amount of Streams records included in your plan will be a lot higher than today for the vast majority of clients.

The change will go live on October 16th. For all Streams user it will be a seamless transition without the need for any action on their side.

As an example, a Pro plan user who solely uses Streams would go from having 50,000 records included in their plan to have over 660,000 records included.

A business plan user who solely uses Streams would go from having 50,000 records included to have over 2.3 million records included.

Any separately purchased Streams plan will be compensated with the same amount of Compute Units being added to their Moralis plan.

If you have any questions about this transition please contact our 24/7 support at [email protected].

1 comment on commit 8950b91

@vercel
Copy link

@vercel vercel bot commented on 8950b91 Oct 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.