Pusher Lab

At Pusher we pride ourselves on providing reliable and stable services you can trust. We maintain support for our APIs and protocol versions for as long as reasonably possible so users don’t have to frequently deal with breaking changes that will impact their applications.

However at Pusher we also want to continue to innovate and keep bringing our users cutting edge features and technologies to help solve complex problems as seamlessly as possible. This means we will sometimes release new features or APIs that will go through an Experimental or Beta phase.

Working with our developer community we may make changes or deprecate Experimental or Beta functionality at short notice so you should be sure not to rely on these in a production environment. Where practical the timelines below set out or expectations for changes to Experimental or Beta features.

Experimental program

Experimental features could change at any time, however depending on the nature of the change we will endeavour to communicate changes to users at least 24 hours in advance.

Typically experimental features will remain experimental for no longer than one business quarter after the last update (subject to review), and will either be progressed to a Beta or Generally Available state or be deprecated.

Experimental features

ProductFeatureLast updateReview dateResourcesStatus
ChannelsHTTP publish API info18 Feb 202118 Apr 2021Active

Beta program

Beta features should be more stable than experimental features, but could still change at any time. However depending on the nature of the change we will endeavour to communicate changes to users at least a week in advance.

Beta features

None in progress

Communication

Update to users

When we make updates to experimental or beta features we will communicate these via:

Feedback from users

The success of our experimental or beta programmes depends on feedback from our developer community. If you have a feedback on any of the programmes above you can do so via: