Compare shred-feed prices on one basis

30 days and 1 destination make quotes comparable

The price comparator puts provider quotes on a 30-day, per-destination basis. It includes recurring price, quoted term, setup charge, included destinations, required add-ons, traffic allowances, overage, and customer-paid infrastructure.

The shredstream.sh reference row is fixed: $100 for one IP and port destination for 30 days, raw UDP from Frankfurt. It does not infer that another provider offers the same wire format, coverage, support, or landing path.

Price normalization is arithmetic. Product equivalence is a separate judgment.

Method

For a quote with recurring amount R over q days:

normalized_recurring = R * 30 / q

For a one-time setup fee S spread over a periods:

amortised_setup = S / a

For measured monthly traffic V, included traffic I, overage rate E, and separately billed traffic rate T:

overage_TB = max(0, V - I)
traffic_cost = overage_TB * E + separately_billable_TB * T

The normalized total is:

total_30_day = normalized_recurring
             + amortised_setup
             + traffic_cost
             + required_addons
             + customer_infrastructure

Per-destination price is total divided by active destinations only when the quote permits that simultaneous fanout. A plan with one movable endpoint is not a five-endpoint plan.

The default traffic input is 17.6 TB per 30 days, derived from the measured 54.3 Mbps feed. Users can replace it when a provider supplies a filtered or different stream.

Worked example

Provider A quotes $180 for 31 days, includes one destination and 10 TB, then charges $2 per additional TB. It also requires a $30 monthly decoder add-on. There is no setup fee. Use the unrounded measured volume of 17.60320512 TB.

normalized_recurring = 180 * 30 / 31
                     = 174.19

overage_TB = 17.60320512 - 10
           = 7.60320512

traffic_cost = 7.60320512 * 2
             = 15.21 rounded

total_30_day = 174.19 + 15.21 + 30
             = 219.40

The shredstream.sh reference is $100 for the same 30-day and one-destination basis. The arithmetic difference is $119.40 for this hypothetical quote.

That does not prove the $100 service is the better purchase. Provider A might include decoding, multiple regions, replay, support commitments, filtering, submission, or a contract the buyer values. The comparison table requires those differences beside price.

Capture every quote date

Provider prices change. Each row stores source URL or document, capture date, currency, taxes, billing unit, and any sales conversation assumptions. A price without an as-of date becomes misleading.

If a quote uses monthly without defining the month, the user selects calendar month, 30 days, or provider billing period. The normalized figure displays that assumption. Currency conversion uses a user-entered rate and date rather than a hidden live value.

Annual commitments should show cash timing and cancellation separately. Dividing an annual prepayment by twelve is useful for unit comparison but does not make it monthly cancellable.

Compare scope before totals

Raw UDP differs from decoded transactions, gRPC, websocket, block replay, and transaction submission. Frankfurt-only differs from a multi-region network. One destination differs from fanout. No retransmission differs from replay or guaranteed delivery.

The component asks for protocol, source regions, destination count, data scope, filtering, historical access, delivery guarantees, support, setup work, and contract term. Unknown remains unknown. It does not translate an absent fact into a favorable value.

Latency claims also need matching boundaries. Leader-to-provider, provider-to-receiver, packet-to-decoded event, and event-to-land are different measurements. A vendor minimum with no percentile or date cannot be compared with a receiver p99 as if they were the same statistic.

Include customer infrastructure

One provider may send raw data that requires a decoder. Another may include structured events. Add the buyer's receiver compute, storage, engineering, monitoring, and network middleboxes only when they differ between options.

Avoid valuing the same employee twice. Use an expected monthly engineering allocation or a one-time implementation amount amortized over a stated period. Keep it editable because team costs vary.

Cloud ingress may be free while load balancers, cross-zone traffic, NAT, packet mirrors, and storage are billed. Map the actual path. A generic internet-egress price is not automatically charged to the receiver.

Limitations

The tool compares entered facts. It does not verify competitor quotes, availability, performance, support quality, or contractual language. Users should attach dated primary sources and review current terms.

A lowest normalized cost can be wrong for a strategy. Regional reach, loss handling, decoding, submission access, and operational support can dominate price. The component presents trade-offs but cannot assign one universal value to them.

The default 17.6 TB is a measured mean projection for this feed as of 2026-08-31. Another provider's filtered data can have different volume. Taxes and currency effects depend on the buyer.

Export every scenario with its assumptions, capture dates, original currency, normalized period, destination count, and volume. Two saved scenarios can then be compared without relying on a current webpage or a remembered sales statement. Unknown fields stay visible in the export.

The reference plan is one destination for 30 days. Additional destinations are separate product choices and should not be inferred from the $100 row. Compare only the exact quantity the desk needs.