PLAN NOTES

The WebSocket add-on runs on its own calendar

Base plans bill by the month, the raw WebSocket add-on in 30-day blocks. Start them together with matching lengths or renewals drift.

The raw WebSocket add-on and the plan it rides on do not share a calendar. Base plans bill by the month, in monthly, three-month and six-month terms, while the add-on is quoted in 30, 90 and 180-day blocks at $99, $297 and $594, as the pricing page lists them, checked 2026-10-23. Bought on the same day with matching lengths, the two renew together and stay readable. Bought on different days, they drift, and the drift is where renewal surprises come from.

Two calendars, one subscription

The month labels and the day counts look interchangeable and are not. A 30-day block renews about twelve times in a year, a monthly plan twelve times, but a three-month term and a 90-day block can part by a day or two immediately, and the gap widens with every cycle.

The estimator on the pricing page states the assumption behind its totals directly: they hold when the selected terms start together, and they are not a quote for adding streaming halfway through an existing subscription. Mid-cycle purchases go through the account dashboard, and any proration there is not a published figure.

What drift actually costs

The money is the smaller part. The larger cost is accounting fog: two renewal dates, two reminders, and a pair of terms that never quite line up when you compare what you paid against what you used. A 90-day block bought three weeks after the plan it complements renews three weeks off the plan for the rest of the subscription.

There is also a decision cost. The renewal review, the one quiet check of whether the plan still fits, works on the term that is ending. Two staggered calendars turn one review into two half-reviews, each missing half the picture.

The alignment rule

Start them together. The day you attach raw frames to a plan is the day both clocks should start, and the block length should match the term: 90 days of add-on against a three-month term, 180 days against six months. The arithmetic cooperates, since $99 times three is the $297 block and times six is the $594 block, so matching lengths costs nothing extra.

Adding the add-on mid-cycle instead? Expect the dashboard to handle the first period on its own terms, then bring the calendars together at the first renewal where a matching block exists. The plan guide picks the base plan; this is the habit that keeps the add-on attached to it readable.

When the question never comes up

Two cases skip the whole issue. The SSE drop alerts plan is not an eligible base for the add-on, and neither are trial keys, per the WebSocket add-on page, checked 2026-10-23. And a REST setup that never needs raw frames never buys the add-on at all. The calendar question starts exactly on the day raw frames enter the cart, and the answer is the same every time: same day, same length, one renewal.