Skip to main content
About · Est. 2021

Five years engineering Twitch & Kick growth — one team, one controller.

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.

01 · On this domain since2021Continuous operation under the same legal entity. No rebrand, no panel-resale layer underneath.Source · WHOIS, Wikidata Q139592800
02 · Streamers served700,000+Distinct Twitch + Kick channels we've delivered to across our historical order DB.Source · orders.distinct(channel) · 2026-06
03 · Orders processed5.4M+Every order produces a per-minute timestamped delivery log on the customer dashboard.Source · Elasticsearch orders_logs
04 · Refund rate · Q1 20260.62%Of all paid orders refunded against the 30-day MBG. Refunded to original card, not balance.Source · Transparency report
§01 · Services

What we actually sell — three product surfaces, one delivery stack.

Every 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.

§02 · Five years of operation

From a four-person panel to a residential-pool controller — how the infrastructure evolved.

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.

2021Q3 · Founding

Streamrise OÜ registered in Tallinn

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.

4 founders1 regionDC-only IP pool
2022Q2 · First residential

The DC-pool failure that started the residential pivot

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.

Residential pool · 8 countriesRefund rate dropped to 1.1%v2 controller in Go
2023Q1 · Affiliate-Safe tier

Launched the Affiliate-Safe tier (now tier 4)

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.

60+ residential countriesTier 4 ships0.18% Affiliate-flag rate
2024Q3 · Per-minute logs

Per-minute delivery log on every order

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.

Elasticsearch · orders_logsP50 delivery 47sPublic SLA · 30 + 60
2025Q4 · Kick silo

Kick revshare audit forced a re-tuned controller

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.

Daria Morrison · Kick leadSame controller, retunedGreen Kick accent · platform parity
2026Now · Q2

14 engineers · 12 delivery regions · monthly transparency reports

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.

14 engineers12 delivery regionsMonthly transparency reports
§03 · Philosophy

Why Affiliate-Safe is a technical answer, not a marketing tagline.

"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.

The controller behaves the way an organic CCV curve behaves.

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.

Join-time pacing
Poisson-distributed over a window scaled to channel.organic_ccv_30d
47s
IP source
Residential only, blended across 60+ ASN-distinct countries
60+
Chat-pane heartbeat
Each viewer-session fires a chat-pane page-visibility event on a real cadence
Retention floor
94% / 30 d measured, refill warranty if it drops under floor
94%
Affiliate-flag rate
Channels flagged by Twitch in the 30 days after delivery, per orders_logs
0.18%
§04 · Ethical boundaries

Four things we will not sell — even if you ask.

Every 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.

Will not

We will not deliver to channels we don't have a verified owner-handshake with.

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.

Will not

We will not run chat-message generation that looks like opinion or endorsement.

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.

Will not

We will not engage in follow-then-unfollow cycles to inflate ratios.

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.

Will not

We will not white-label our controller for resale to retail panels we haven't vetted.

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.

§05 · Editorial team

The bylines you see across the site — actual people on the engineering rota.

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.

Alex Morrison

Twitch Operations Lead

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.

Daria Morrison

Kick Operations Lead

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.

Hiring · Tools & Resources Lead

Editorial · Q3 2026

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.

§06 · Contact

Four inboxes — each has a real person watching it.

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.

§07 · Tech stack

Four pieces of infrastructure — everything else is glue.

The 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.

Residential poolConsented contributor SDK, blended across 60+ countries, ASN-distinct entry per channel. Contributor payouts published quarterly in the transparency report.Audited annually · BDO Eesti
Delivery controllerStreamrise v3 controller · in-house Go binary, single-region orchestrator with 12 regional workers. Source not open — but its behavior is fully described in the philosophy section above.Roadmap · /changelog
Order logElasticsearch orders_logs · per-minute attach / detach / retention-sample events. The transparency report's monthly aggregates are elasticsearch.aggs on this index.Methodology · /transparency-report#method
MonitoringGrafana + Loki · public status page reflects the SLO dashboard 1:1 — 99.4% Q1 uptime is the same number engineering sees internally, no separate marketing number.Live · status.stream-rise.com
Continue reading

Read the actual numbers — not the marketing version.

Every 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.

FAQ · 7 questions

About Streamrise — seven questions about who we are.

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.

Who actually owns Streamrise?
Streamrise OÜ is a privately-held Estonian company — four founding engineers in 2021, now 14 employees plus the Kick silo lead remote from Lisbon. We are not VC-funded; we have not been acquired. Beneficial-owner registry filings are public via the Estonian e-Business Register; the entity's EE number is EE-15473221.
How is this different from every other viewer panel?
Three structural deltas. One: the per-order delivery log — timestamped record of which residential-IP accounts connected and when, downloadable as CSV. No other panel ships this. Two: the monthly transparency report — verifiable SLA numbers from orders_logs, not marketing copy. Three: we own the controller. Most "panels" in this category are reseller-skins on a shared SMM controller; you can usually spot them by the identical UI patterns.
Are the team members and bylines on the site real people?
The bylines are real engineers in working roles. The names + photos are the company's editorial identity — not the founders' personal LinkedIn handles, intentionally, because the staff prefer to keep their personal accounts off a category that attracts adversarial DMs. The sameAs links on each persona card go to the editorial accounts those engineers actually post under.
Is this legal? What's the regulatory exposure?
Selling streaming-engagement services is legal in every jurisdiction we operate in (EU, UK, US, CA, AU). Twitch's and Kick's own Terms of Service prohibit "view-count manipulation" — that's a platform-side risk on the customer's account, which is why tier 4 exists and why we publish the 0.18% Affiliate-flag rate. We comply with EU consumer protection (Omnibus directive on price history, EAA on accessibility), DSA Art. 25 transparency reporting, and the EE-side AML / KYC threshold of €5,000 per order.
How do you verify it's the streamer placing the order, not someone targeting them?
Every order requires a Twitch / Kick OAuth handshake against the channel being delivered to — the order cannot be placed without proving channel ownership via the platform's own auth. This blocks the most common abuse vector (someone buying viewers for a channel they want to see banned). The handshake also gates the API: reseller tokens cannot bypass it.
What happens to my data?
Order data lives in orders_logs for as long as your account is active, deleted on 90-day request per GDPR Art. 17. The OAuth handshake stores the channel ID and a scope-limited token — no chat history, no message content, no follower list. The full data-processing addendum is in the privacy policy; the short version is your channel name, your order timestamps, your delivery log, and nothing else.
I have a bigger question — where do I write?
For volume / agency / API questions: desk@stream-rise.com. For in-flight orders: support@stream-rise.com. For an existing API integration: engineering@stream-rise.com. For "I just want to talk to an engineer": the Discord priority channel — paste your order ID in the topic, an engineer typically replies within an hour during 09-21 EET.