Arc is peer-to-peer software that improves websites' performance and profitability. Websites embed Arc's widget () to generate revenue and reduce costs with Arc's decentralized Content Delivery Network (CDN)1.
The proceeds from Arc's reliable, low-cost CDN are paid out in proportion to the time spent by users on each Arc-powered site. The more users and the longer they stay on a site with Arc's widget, the more that site earns.
Websites receive a minimum of 50% of the CDN proceeds generated by their audience. Websites that also rent Arc's CDN earn up to 60%. In the future, websites will earn up to 75% with referral bonuses and from users who donate or spend their share of earnings on their favorite Arc-powered sites.
For contributing to Arc's people-powered network, users receive 10% of their devices' proceeds in the form of Arc rewards. The more time they spend on Arc-powered sites, the more rewards they earn.
In the future, Arc rewards will work like airline miles that users can donate to charities of their choice or spend on websites to unlock paid content or special privileges. In the meantime, user earnings are collected and donated, on their behalf, to Wikipedia in support of a free and open Internet.
Arc's widget never affects the user experience or device performance. Ever.
To ensure such, Arc's widget strictly adheres to the following golden rules:
Mobile devices (phones, tablets, etc.) only join Arc's peer-to-peer network when plugged into power.
Devices only share bandwidth on Arc's network when connected to a LAN or Wi-Fi.
Available bandwidth is closely monitored to ensure Arc never impairs a device from optimally performing user tasks.
Arc's widget must be displayed on every page it powers so users can always learn more about Arc, opt out/back in, or contact us.
Arc tracks the absolute minimum information necessary to pay websites, reward users, and bill CDN customers:
No other data is captured. No software is installed, no private browsing data is collected, and personal user files remain inaccessible. User and website privacy is inherently preserved.
Getting started is easy.
Append Arc's widget to the
<head> tag on every page you want to
monetize and/or power with Arc's CDN.
<!doctype html> <html> <head> ... <!-- Insert Arc's widget here. --> <script async src="https://arc.io/widget.js/[YOUR_WIDGET_ID]?CDN=False"></script> </head> </html>
That's it. Arc is now a passive revenue generator for your website.
To also enable Arc's CDN to improve your website's performance and save money, continue with Steps 4 and 5 below. Charges will apply1.
CDN= flag to
True on every page you wish to accelerate
with Arc's CDN.
<!doctype html> <html> <head> ... <!-- Insert Arc's widget here. --> <script async src="https://arc.io/widget.js/[YOUR_WIDGET_ID]?CDN=True"></script> </head> </html>
Enter your credit card information on the Billing page. CDN charges are billed monthly, on the first day of each calendar month.
You can disable Arc's CDN at any time by setting the
CDN= flag to
Revenue scales based on three variables:
Let's go through a hypothetical example.
Last month, Sarah spent 100 hours browsing three Arc-powered websites: wikipedia.org, nytimes.com, and reddit.com.
While Sarah had any of these sites open in her browser, she shared some surplus bandwidth with Arc's community (as did other visitors on these sites).
Arc was able to aggregate and rent Sarah's shared bandwidth to independent websites via Arc's CDN for a total of $10 in revenue that month.
This $10 is then distributed as follows:
The $6 website portion of Sarah's total device revenue is then paid to the three Arc-powered websites she visited in proportion to the time she spent on each. Let's say of the 100 hours Sarah spent browsing,
Website revenue is calculated daily and paid out weekly, bi monthly, or monthly.
While cached assets (video, audio, images, etc.) are fragmented, encrypted, and invisible to users, out of respect for the community, Arc limits CDN access to reputable websites only.
Prior to gaining access to Arc's CDN, websites apply and undergo review. If found suitable, they're approved. Sites with content deemed illicit, illegal, or inappropriate for a universal audience (e.g. pornography, gambling, etc.) are declined.
When Arc's CDN is enabled with
Arc's widget starts
Worker that waits for network requests for cacheable, static
/kitty.png). A network
request is determined cacheable if
bmp, bpg, eps, gif, ico, jpeg, jpg, pict, png, svg, svgz, tif, tiff, ttf, webp
3g2, 3gp, amv, avi, drc, f4bogv, f4p, f4v, flv, gifv, m2v, m4v, mkv, mov, mp2, mp4, mpe, mpeg, mpg, mpv, qt, webm, wmv
aac, aiff, f4a, flac, m4a, m4p, mid, midi, mogg, mp3, oga, ogg, opus, ra, rm, wav, webm
doc, docx, otf, pdf, ppt, pptx, ps, xls, xlsx
Once a network response is deemed cacheable, in the background, Arc's servers independently retrieve, fragment, encrypt, and securely cache a mirrored copy of that asset across Arc's distributed network. Once cached, every Arc widget watches for future requests and automatically retrieves that asset from Arc's peer-to-peer network instead of the more expensive origin server (over WebRTC instead of HTTP).
Assets are cached reliably across Arc's network, which automatically and expeditiously scales an asset's availability and redundancy as it becomes more popular. Traditional CDNs degrade the more users they have; Arc's gets better.
Additionally, to guarantee 100% availability and optimal performance while Arc's distributed network scales, all assets are redundantly cached on Google Cloud's CDN. If for any reason Arc's peer-to-peer network becomes degraded, requested assets are instantly and transparently served from our Google Cloud backup instead.
Arc is designed with security in mind and adheres to security industry best practices.
All data cached on devices is encrypted with bank-grade 256-bit AES.
All data in transit to and from Arc's infrastructure is encrypted over HTTPS/TLS.
All data in transit across Arc's peer-to-peer network is encrypted over DTLS.