Pusher releases products into Beta to prepare for General Availability. We use the Beta period to gather feedback from developers, add new features, and validate that there is demand for the product. Our product in General Availability is the Pubsub Messaging Gateway, products in Beta include Feeds and Chatkit.
By creating an account and using any products released in Beta, you agree to be bound by the General Availability terms as modified or supplemented by the Beta terms of service below. In the event of any conflict between the Beta terms, and the General Availability terms of service, the Beta terms will take precedence in relation to Beta products to the extent only of such conflict. The Beta terms will not apply to General Availability products. These Beta terms and conditions are subject to change at any point without notice to you; it is your responsibility to ensure you have read and understand the terms that apply to Beta products at all times.
1. Release time period
There is no set time limit for the Beta release period. Products released in Beta may not ever be released into General Availability, but we will keep the product available as long as there is sufficient demand for the service.
2. Service uptime
Although we make a best effort to maintain uptime for products released in Beta, we cannot guarantee 100% uptime. Products released in Beta may experience more issues than a product released in General Availability. We’ll post status updates to the appropriate channel for a Beta product when an issue arises.
Products released in Beta do not share a Support policy with those released in General Availability. Because we are gathering feedback for Beta products, we have some realtime mechanisms such as Slack channels. We will not provide support for products in General Availability through these channels.
4. Data storage
Unlike the Pubsub Messaging Gateway, the Beta products can store historical data both of the Customer and the End User and any references to data being transitive in the Terms and Conditions for the Pubsub Messaging Gateway do not apply to the beta products. Our Customers store any data of End Users in the Beta products at their own risk, and are solely responsible for notifying their End Users should they require, for the purpose of international data compliance regulations they may need to fulfil.
If the product does not make it to General Availability, we will give the app developer at least two months advance warning to backup their data before the service is terminated and the data is deleted.
5. Recommended use
While products are released in Beta, we do not recommend relying on them for software projects already released in production. We also do not recommend using products released in Beta for highly sensitive data.
6. Service abuse
We reserve the right to limit activity of apps that cause issues. While products are released in Beta, we will proactively manage system-wide usage to ensure that usage by one Customer does not affect service availability system-wide. We will proactively communicate this to the app developer by email if an issue arises.
During the Beta release period, it is free to use the product. We reserve the right to change this in the future.
8. Service limits
We reserve the right to apply systemic limits such as a rate limiting, throttling, and plan limits to products released in Beta. We also reserve the right to change the data size limits of messages allowed on a service in the future. The Quotas policy for products in General Availability does not extend to products released in Beta. For Feeds, each instance is limited to 10k items. In case of Chatkit, the policy is outlined here.
9. Product updates
Products that are released in Beta are likely to change more frequently than those in General Availability. This includes changes to APIs and SDKs that could result in breaking changes for developers using the service. We will communicate known breaking changes to users actively using Beta products by email.
For anything not covered by this list, refer to our Legal section or contact us at firstname.lastname@example.org.
10. Reporting Vulnerabilities
Although we make security a top priority, products that are released in beta have not been tested for security vulnerabilities at the level that products released in general availability are tested. While we encourage users to voice concerns about a product to us during the beta period, the reward for our Report Vulnerabilities programme is not offered for products released in beta.