Alex Morrison
Twitch Operations LeadLead on the Twitch silo since the v2 controller rewrite in 2023. Owns the Affiliate-Safe tier's pacing distributions and authors the monthly transparency-report methodology section.
Streamrise is a 14-person company in Tallinn, EU. We sell viewer-hour delivery, follower batches, and chat presence for live streamers — and we publish the per-order log that proves what we shipped. No outsourced controller, no white-label resold panel, no overnight rebrands.
orders.distinct(channel) · 2026-06orders_logsEvery service routes through the same per-order controller and the same Elasticsearch-backed delivery log. The product surface differs; the underlying infrastructure does not. Each line below links to its money page where the per-1K pricing, retention curve, and SLA live.
Residential-pool viewers attached to your live channel, paced over your stream's actual schedule. Retention windows from 7 to 45 days. The flagship product since 2021.
Real-profile followers paced over 24-72 hours so the ratio doesn't trip the Affiliate-track follower-velocity audit. Comes with a 60-day refill on drop-off.
Lurker presence on tiers 3+, curated chat lines on tier 4. Bring-your-own bot bridge available for studios that already run a content-mod pipeline.
Same controller binary as the Twitch silo — re-tuned for the Kick revshare audit's quarterly review. The Daria Morrison silo since the platform's revshare announcement.
Recorded-segment views for clips up to ~60s and VOD views with a 30-day retention floor. Instant-burst or paced-over-window presets. Useful for highlight-reel campaigns.
Bring-your-own-panel: idempotent REST endpoints + webhooks, 60 req/s trial bucket, OAuth-issued tokens. The same controller you use through the dashboard, behind your own UI.
We did not ship the residential pool in week one. We started on the same datacenter-IP stack every other 2021 panel ran on — and rebuilt it piece by piece as the Twitch detection floors moved. The honest version of that timeline, with the events that forced each move.
Four founders, one shared rented cabinet in a Hetzner Helsinki DC, a Vue 2 panel held together with backend cron. First paying customer: a German Variety streamer running once-a-week three-hour sessions. The product was viewer-hours, the controller was a shell script, and the delivery log was a CSV mailed nightly.
March 2022: a Twitch detection update flagged a quarter of one week's deliveries as DC-origin. Refund rate spiked to 3.4% — survivable but unacceptable. We started routing tier-3 traffic through a small consented-residential pool that summer; by the end of the year it was the default for any order over $40.
A year of conversations with Affiliate-track streamers who'd lost partner-track applications over viewer-bot flags made the next product obvious: a tier specifically tuned to look like organic CCV growth — natural ramp, chat-pane events, no uniform join timestamps. Tier 4 has been the most-purchased tier for 14 of the last 18 months.
We replaced the order-level aggregate with a downloadable per-minute log: each batch attach event, each detach, each retention-tail sample. Customers stopped asking "did it deliver?" because the answer was a CSV they could open. This is the same log the transparency report draws its quarterly aggregates from.
Kick's quarterly creator-payout review behaves differently than Twitch's — slower, more spreadsheet-driven, with a heavier weight on chat-ratio anomalies. We didn't ship a Kick service until Daria Morrison's silo could match the controller's behavior to that audit. Same binary, retuned pacing-interval distributions.
Today: 14 engineers in Tallinn plus the Kick silo lead remote, 12 residential delivery regions, monthly published transparency reports against actual order-log numbers. The 2026 roadmap is reseller API hardening and a creator-side panel rewrite — neither will change what's already shipped under the SLAs above.
"Affiliate-Safe" is the name of tier 4, but it's also a list of fairly boring engineering decisions about how viewer-attach events should look from Twitch's side of the wire. None of these are secrets; the only differentiator is that we actually implement them.
Twitch's anti-bot system looks for the shapes that real viewers don't make. Uniform join-times, single-AS bursts, zero chat-pane interaction, sub-second concurrency curves, ASN clusters that don't match the channel's organic geo distribution. The Affiliate-Safe tier's controller is tuned not to produce those shapes.
The shorthand: natural ramp + chat-pane heartbeat + AS-distribution that mirrors the channel's organic 30-day floor. Each delivery is a per-minute conversation with the controller, not a one-shot batch attach. That's why a 47-second P50 still feels organic from Twitch's side.
It also costs more to operate, which is why tier 4 is priced at $9.40/1K — roughly 2.3x the DC-only floor on tier 1. The price difference is what residential bandwidth, contributor payouts, and the chat-pane heartbeat actually cost. Not margin theatre.
channel.organic_ccv_30d60+ ASN-distinct countriespage-visibility event on a real cadenceorders_logsEvery viewer-service operator says they're ethical. The shorter, more useful list is the one of things we've turned down. These four come up most often in support tickets; they're not on the price list because we won't ship them.
Buying viewers for someone else's channel is the most common abuse vector in the category. Every order requires a one-click owner-handshake against the channel's Twitch / Kick auth; we do not ship without it, even for resellers using the API.
Curated lines on tier 4 are utility cues — "sub goal hit", "first time chatter", lurker-presence tokens. No political content, no product reviews, no anything that looks like a human voicing a view they did not voice.
Follower batches are one-direction: paced over 24-72 hours, retained on the 60-day refill, no reversal cycles. The "200 follows then drops" pattern other panels use is what every platform's velocity-audit catches first; we don't ship it.
The API is open for vetted reseller partners with a real signed contract and a per-channel handshake flow. We turn down the panel-of-panels middlemen — they're the source of the "viewers from a service I never signed up for" support tickets that hurt the whole category.
The article and page authors here are working engineers — same people who answer Discord priority tickets and write the transparency-report methodology. Not stock-photo "head of growth" types. Below is the persona-card index for the public-facing bylines.
Lead on the Twitch silo since the v2 controller rewrite in 2023. Owns the Affiliate-Safe tier's pacing distributions and authors the monthly transparency-report methodology section.
Joined to lead the Kick silo at the platform's revshare announcement. Retuned the Twitch controller's pacing-interval distribution for the Kick quarterly creator-payout audit; remote from Lisbon.
Open role: lead author for the free-tools index and the reseller API documentation rewrite. We will publish the byline here when the role closes — no stub-personas in the meantime.
Pick the inbox that matches what you need. Reply SLAs are the median on the last 90 days of tickets, not aspirations. Live chat on the dashboard is faster for in-flight delivery questions; everything else routes by email.
Volume rate cards, agency program (5K+/mo commits), tier-5 onboarding, and EU invoicing questions. Reply median 3h business-hours.
desk@stream-rise.comSLA · 4 business h02 · Support & deliveryIn-flight orders, refund requests, refill-warranty claims, balance questions. The first place to write for anything order-numbered.
support@stream-rise.comSLA · 4 business h03 · API & integrationsReseller API onboarding, webhook signatures, rate-limit increases, error-payload questions. Faster than support if your question has a request-ID.
engineering@stream-rise.comSLA · 6 business h04 · Live · DiscordDiscord priority channel for paid customers — paste your order ID in the topic, an engineer typically replies within an hour. Tier 4 & 5 get the named channel.
discord.gg/streamriseSLA · 1h · 09-21 EETThe stack is deliberately small. Each row links to either a methodology section or a status page where you can see the live numbers. Vendor names are listed so you can audit dependencies; we don't run a stealth-vendor controller behind the scenes.
60+ countries, ASN-distinct entry per channel. Contributor payouts published quarterly in the transparency report.Audited annually · BDO Eestiorders_logs · per-minute attach / detach / retention-sample events. The transparency report's monthly aggregates are elasticsearch.aggs on this index.Methodology · /transparency-report#methodEvery metric on this page is published, methodology-documented, and refreshed monthly in the transparency report. The April 2026 issue covers 412,000 orders, the per-service delivery SLA, and the four refund-reason buckets.
Things that come up before purchase that aren't actually price-or-product questions. If yours isn't here, the contact section above has four inboxes and a Discord channel.