Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.bright-sdk.com/llms.txt

Use this file to discover all available pages before exploring further.

No. The service is engineered to be non-intrusive. It works silently in the background, only using small “packets” of your users’ unused connection that wouldn’t be used otherwise. We’ve implemented continuous system monitoring to ensure that our background tasks always yield to their streaming, gaming, or browsing. Because the service is designed to stay within strict, safe thresholds, it will not  materially adversely affect their device or network’s behavior or performance.
No, Bright SDK does not use any space on your hard disk.
No. CPU is only used when Bright SDK sends traffic, which happens only when the device resources are available, so the user never feels it.
No. Only minimal CPU resources, as explained in How much CPU does Bright SDK use?
No. Nothing is left on your user’s device.
Very little. Upon your users’ explicit consent, our service utilizes a small portion of their outbound bandwidth for data transfer. To maintain their network’s integrity, we employ automated safeguards that prevent the consumption of excessive data. Our “Fair-Usage” algorithm ensures that the service remains a background process that does not compete with the system resources. We actively monitor all traffic to ensure our usage remains well below levels that would impact their connection’s stability or the functionality of other installed software.Your users will never see 100% CPU or experience any slowdown in apps!
Short answer: Yes. Although the probability of that scenario is not too high.See this article to understand the payment terms of such case.