Streamrise FAQ

No. We never ask for your password, OAuth token, or account access of any kind. The only thing we need is your public channel URL, because our delivery reaches your stream through the same public endpoints any viewer uses.

If a growth service ever asks for your login, treat it as a warning sign — there is no technical reason to need it. Keep two-factor authentication on, exactly as you would normally.

Median time to first viewer is 47 seconds after an order goes live. Standard orders begin ramping within 1–3 minutes; scheduled orders start at the exact slot you chose.

We ramp gradually rather than dropping the full count at once, because a natural-looking curve matters more than raw speed. You'll see the count move in your dashboard in real time, so you always know where delivery stands.

We support Twitch and Kick for viewers, followers, and chatters, plus VOD and clip views on Twitch. YouTube live viewers are in limited beta for existing customers.

Each platform has its own delivery profile because Twitch, Kick, and YouTube measure concurrency differently. If you stream somewhere we don't list yet, message support and we'll tell you honestly whether we can deliver safely.

Yes — for concurrent viewers and chatters, your channel must be live, because the traffic attaches to an active stream. Start your broadcast first, then place or schedule the order.

Followers and clip or VOD views are the exceptions: those can be delivered whether or not you're currently streaming. If you schedule a viewer order, line it up with your go-live time so the ramp begins as you start.

Yes, new channels can order, but we recommend starting small. A channel that's two days old jumping to 800 concurrent viewers looks abnormal, so for accounts under 30 days we cap the suggested ramp and spread it over a longer window.

This pacing protects new channels because platform review systems weigh sudden spikes more heavily on young accounts. Our setup guide includes a recommended first-order profile for new streamers.

By default, viewers raise your concurrent count without chatting. If you want visible activity, add chatters as a separate option — they post context-aware messages at a natural ratio.

We keep the two products distinct because not every streamer wants chat movement, and over-chatting a small stream looks less natural than a quiet, steady audience. You choose the mix when you order.

In our delivery history of 410,000+ orders, fewer than 0.4% of customers reported any Twitch enforcement action, and we refund in full when our delivery is the proximate cause.

We can't promise zero risk — no honest service can, because Twitch updates its policies and detection independently. What we can say is that our delivery is engineered to avoid the data-center signals platform fraud systems weigh most heavily. Read how we think about safety in our delivery SLA.

Delivery arrives over rotating residential IPs rather than data-center subnets, spread across regions and ramped in gradually rather than all at once — the way a real audience builds. This reduces, but cannot eliminate, exposure, which is why our refund covers any delivery-caused action on your channel.

47 seconds. That's the median measured across the last 90 days of live orders, from the moment an order activates to the first viewer registering on your count.

The full ramp to your target number takes longer by design — typically 3–10 minutes depending on the count — because a gradual climb reads as organic discovery rather than a spike. We publish this figure monthly and adjust our claims to match measured reality.

Yes. Every order lets you choose a ramp curve instead of an instant fill. You can spread the climb over 5 to 60 minutes, hold a steady plateau, and add a gentle taper at the end.

Gradual ramps are the default because a stream that goes from 4 to 600 viewers in one second looks engineered, while a steady climb mirrors how real discovery feels. Schedule recurring orders to build a believable week-over-week pattern.

Concurrent viewers contribute to the average-viewer metric Twitch uses for Affiliate and Partner review, but we're deliberately careful here.

We can't guarantee the platform will credit any specific session, because Twitch evaluates eligibility holistically and changes its criteria without notice. Our Affiliate-Safe tier is tuned to a conservative concurrent band for exactly this reason. Treat bought viewers as a supplement to real growth, not a shortcut around the requirements.

Delivery is distributed across 12 regions by default, weighted toward North America and Western Europe. You can request a geo-shaped profile — for example, a Top-3 city weighting matched to your real audience — because viewers concentrated in one unexpected country can look off against your existing analytics.

Geo-targeting is included on Premium orders. If you stream to a specific regional audience, tell support and we'll shape the mix to match.

If your stream drops, delivery pauses automatically and your remaining time is preserved. Viewers can't attach to a stream that isn't live, so rather than burning your order, we hold the balance for you to resume.

When you go live again within the order window, delivery picks up where it left off. If the interruption breaks the order entirely, our refund policy covers the undelivered portion.

Yes, within limits. You can raise the target mid-order at any time, and we'll ramp the additional viewers gradually. Lowering the count is also supported, but we taper down slowly rather than dropping instantly, because a sudden cliff in viewers is more noticeable than a soft decline.

Changes apply from your dashboard and take effect within about a minute.

Short dips of a few percent are normal and intentional. Real audiences fluctuate as people tab away and return, so our delivery breathes slightly instead of holding a flat line, because a perfectly static number is itself an unnatural signal.

A dip under 10% that recovers within minutes is expected behavior. If you see a sustained drop below your ordered level, that counts as a drop-off — see refunds & drop-offs for the refill window.

Bought viewers don't generate ad revenue or subscriptions themselves, so they don't directly inflate your payout — real income still comes from real fans.

The relevant risk is eligibility, not the payment math: if a platform review attributes inorganic concurrency to your channel, status can be affected. Our Affiliate-Safe tier exists to keep delivery within a conservative band for this reason. We can't guarantee payout outcomes, because those are governed entirely by Twitch's own terms.

Affiliate-Safe is a delivery profile tuned to conservative concurrent-viewer bands, gradual ramps, and residential-only routing. It trades peak numbers for a pattern that stays closer to believable organic growth, because the goal on an Affiliate-track channel is durability, not a vanity spike.

It's the recommended tier for anyone working toward or maintaining Affiliate or Partner status. The technical differences are summarized in our delivery SLA.

They can contribute to your average concurrency, which is one of Twitch's Affiliate criteria, but we're careful not to overpromise. Twitch reviews eligibility across several signals and updates its thresholds without notice, so no service can guarantee the requirement is met by purchased viewers alone.

We tune Affiliate-Safe orders to a steady, modest band that supplements genuine viewers rather than replacing them. Combine it with consistent streaming for the best outcome.

Partner channels face more scrutiny simply because they're larger and more visible, so we apply a more conservative profile by default. The mechanics of our delivery are identical; what changes is the recommended band and ramp.

A 30,000-follower Partner drawing a sudden inorganic spike stands out more than a small channel would. If you're a Partner, talk to support before your first order so we can shape a profile that fits your baseline.

Yes — our Channel Promotion program pairs scheduled Affiliate-Safe delivery with a 30-day growth plan and a concierge contact. It's built for streamers who want pacing handled for them rather than placing orders manually.

We're explicit that it improves your conditions for review without guaranteeing status, because eligibility is Twitch's decision alone. See setup guides or message support to scope a plan.

Price is a function of viewer count multiplied by duration, quoted as a clear per-viewer-hour rate. A 100-viewer order for one hour starts at $2.94, which works out to about $0.029 per viewer-hour.

Larger and longer orders lower the per-unit rate. There are no hidden recurring charges on one-time orders — the number you see at checkout is the number you pay. Full rate tables live on our pricing page.

Standard prioritizes reach: higher peak counts at a lower per-viewer rate, suited to one-off hype moments. Affiliate-Safe prioritizes pattern safety: conservative bands, gradual ramps, and residential-only routing for channels on the Affiliate or Partner track.

Affiliate-Safe costs more per viewer-hour because the routing and pacing are more expensive to deliver. If you're unsure, default to Affiliate-Safe — durability matters more than a one-night peak.

Both. One-time orders are the default and carry no recurring charge. If you stream on a fixed schedule, a subscription delivers a set profile automatically — for example, every Monday, Wednesday, and Friday — which also builds a more believable week-over-week pattern than sporadic spikes.

You can pause or cancel a subscription anytime from your dashboard, effective at the end of the current cycle.

We accept major credit and debit cards, plus several cryptocurrencies for customers who prefer them. Card payments are processed through a PCI-compliant gateway, so your card details never touch our servers.

Refunds return to the original payment method. If you need an invoice for a business or reseller account, request one from support and we'll issue it.

Yes — the smallest order is 100 viewers for one hour, starting at $2.94. We set a floor because very small orders aren't worth the delivery overhead, and a handful of viewers rarely moves the needle for a stream.

There's no maximum for standard accounts; large orders are paced over a longer ramp. Reseller accounts have separate volume tiers via our API.

Displayed prices are exclusive of VAT and local sales tax, which are calculated at checkout based on your billing country. As an EU-registered company, we collect VAT where required and show the exact amount before you pay, so there are no surprises.

Business customers can enter a valid VAT ID to apply reverse-charge where applicable. Your receipt itemizes any tax collected.

If delivery stops short of what you ordered, you're covered two ways: automatic refill within the 30-day window, or a refund for the undelivered portion. Our system monitors every active order, so a break is usually detected and refilled before you notice.

If a refill isn't possible, we refund the unfulfilled share to your original payment method. The full terms, including what counts as a break, are in our refund policy.

Refund requests take three steps:

1. Open the order in your dashboard and select Request refund.
2. Choose the affected portion — full order or a specific drop-off.
3. Submit; you'll get a confirmation and a ticket reference.

Most refund decisions are made within one business day. You can also message support with your order ID. Terms are in our refund policy.

The refill window is 30 days, not 14. If viewers, followers, or chatters drop below your ordered level within 30 days of delivery, we top them back up at no charge.

We chose 30 days because drop-off can happen gradually and a short window would leave customers uncovered. Refills are automatic for monitored orders; for anything we miss, request a refill from your dashboard and it's processed the same day.

Approved refunds are issued to your original payment method within 5 business days. Card networks then take their own time to post the credit — typically 2–5 additional business days depending on your bank.

Crypto refunds settle faster, usually within a few hours of approval. We send a confirmation the moment the refund leaves our side, so you can track it against your statement.

Normal fluctuation is a dip under 10% that recovers within a few minutes — we build that breathing room in on purpose, because a flat line is itself unnatural.

A drop-off is a sustained fall below your ordered level that doesn't recover. Drop-offs are covered by the 30-day refill window; routine fluctuation isn't a fault and isn't refunded. If you're unsure which you saw, send support your order ID and we'll check the delivery log.

Yes. If an order hasn't started delivering, you can cancel it from your dashboard for a full refund, no questions asked. Once delivery has begun, refunds apply to the undelivered portion rather than the whole order, because the delivered part has already been fulfilled.

Scheduled orders can be cancelled any time before their start slot. See the refund policy for the cut-off details.

Chatter messages are generated from curated, context-aware templates rather than typed live by staff, and we're straightforward about that. They're designed to fit your stream's category and pace so chat feels active without flooding.

We don't claim they're live humans, because that would be misleading — what they are is a believable layer of movement you control. If you want genuine conversation, pair chatters with your real community, not in place of it.

Yes, within guardrails. You can set a tone, supply keywords or phrases tied to your content, and block terms you never want to appear.

We don't allow chatters to post links, @-mentions of other channels, or anything that could harass a real viewer, because that would put your channel at risk rather than help it. Configure the message profile when you order, and adjust it mid-stream from your dashboard.

A ratio near 1 chatter per 10 viewers reads as natural for most categories. Real chat is mostly lurkers, so over-chatting a stream — say, half your viewers all talking — is more conspicuous than a quiet, steady room.

We default new orders to roughly 1:10 and let you tune it by category, since fast-paced games sustain more chat than relaxed ones. When in doubt, less chat looks more real.

We engineer chatter behavior to stay clear of the patterns spam detection looks for — no repeated identical messages, no link drops, no rapid-fire bursts from many accounts at once.

Per Twitch's chat guidelines, the strongest spam signals are repetition and coordinated timing, so we vary phrasing and pace messages irregularly. This lowers risk but can't eliminate it, which is why our messages stay conservative and link-free by default.

Partly. Chatters react to the category and broad context you configure, and to pacing cues, but they don't watch your video or understand specific moments, so they won't reference a play that just happened.

We're honest about this limit because promising real-time awareness would set a false expectation. Treat chatters as ambient movement; your real viewers are the ones who'll react to the actual moment.

Median first reply is 8 minutes during staffed hours. That figure is measured monthly across chat and email, and we publish it because a reply-time claim we can't honor would violate consumer-protection rules.

Outside staffed hours, messages are answered first thing when the team is back online. Complex delivery investigations take longer than a first reply, but you'll always get an acknowledgment and a ticket reference quickly.

Three: live chat on the site, email at support@stream-rise.com, and Telegram. All three reach the same team and the same ticket history, so you can switch channels without repeating yourself.

Chat is fastest during staffed hours; email suits detailed order questions; Telegram is handy if you're mobile. The contacts page lists business and reseller routes separately.

No. Every message is answered by a person on our delivery and support team — no chatbot triage, no auto-close, no canned-template wall.

We do this because growth-service customers usually have specific, technical questions that a scripted bot handles badly. You may get a fast reply, but it's a human reading your actual order, not a macro. That's a deliberate commitment, not a marketing line.

Staffed hours are 09:00–23:00 UTC, seven days a week, including weekends and most holidays. Within those hours, median first reply is 8 minutes.

Messages sent overnight are queued and answered at the start of the next staffed window, in the order received. If you have a time-sensitive order, send it during staffed hours so the team can act on it immediately.

Yes. Tell support your streaming days, your category, and your current baseline, and we'll suggest a delivery profile and ramp that fits, free of charge.

We do this because a well-paced schedule outperforms sporadic spikes for channels working toward Affiliate or Partner status. For hands-off pacing, the Channel Promotion program manages the schedule for you. Start with our setup guides if you'd rather plan it yourself.

Yes. Our REST API lets resellers create, monitor, and refill orders programmatically, with the same delivery engine our site uses. Authentication is per-account API keys, and every order endpoint mirrors the retail options — count, duration, ramp, geo, and tier.

Resellers get volume pricing and webhook callbacks for order events. Request access and docs from our contacts page; approval typically takes one business day.

API pricing is volume-tiered and runs below retail, scaling with committed monthly volume rather than per-order. You prepay a balance and draw against it, so there's no per-transaction card fee eating your margin.

Tiers and exact rates are shared under NDA during onboarding, because reseller pricing is account-specific. There's no setup fee; you commit to a monthly floor and the per-unit rate drops as the floor rises.

Yes. Every reseller account gets a sandbox key that mirrors the production API exactly but doesn't deliver real traffic or charge your balance. Use it to build and test integrations, validate webhook handling, and confirm error paths before going live.

Sandbox responses match production schemas field-for-field, because an integration that works in sandbox should work in production unchanged. The docs include a full sandbox walkthrough.

Yes. You can register webhook endpoints to receive events for order created, delivery started, refill triggered, drop-off detected, and order completed. Each callback is signed so you can verify it came from us, and failed deliveries retry with backoff for up to 24 hours.

Webhooks let your dashboard reflect order state without polling. The event schema and signature reference are in the API docs.

The default limit is 600 requests per minute per API key, which is generous for order creation and status polling alike. Bursts above the limit receive a 429 with a Retry-After header rather than a hard block, so a brief spike won't break your integration.

If your volume needs a higher ceiling, we raise it per account on request. Use webhooks instead of tight polling loops to stay well within budget.