Proof
- Up to $0.50 per user per month
- Universal: Apple Silicon and Intel
- Swift via a C bridging header
- Caps compiled into the core
- First 100 devices, no sales call
What you actually get in the download
cr-sdk-macos.zip is a complete package rather than loose files: the universal
dylib, include/cr_sdk.h, a README, verify.sh, checksums.txt, a VERSION
file, and a sample/ directory. The sample is a single C file covering the whole
lifecycle — build it, run it, and a live device appears on your dashboard before
you have touched your own project.
That sample-first order is deliberate. Integrating an SDK into a real app and then debugging why no device appeared is a bad afternoon; proving the library works in isolation first turns it into a five-minute check.
On signing: we do not ship the dylib with an Apple Developer signature. You sign and notarise your own app bundle, embedding the dylib as part of it, which is the correct arrangement — a library signed by someone else does not help your notarisation and would give you a second identity to reason about. The checksums in the package are how you verify what you received.
What it pays
Up to $0.50 per user per month, at per-country rates, with the full rate card in your dashboard from signup.
It accrues daily. A user counts for a day once their device has been sharing for 60 minutes in that day, each qualifying day is worth the monthly rate divided by the days in that month, and the month is the sum of those days. A day under the bar earns nothing.
Devices on hosting, datacenter or VPN IPs are not counted.
The full arithmetic is here, and what each model pays is the honest comparison against ads, subscriptions and in-app purchases.
What runs on the machine
A background task that yields to the app it lives in. When a data cap is reached or the machine is under sustained load, the device opts out of sharing entirely and checks back later rather than continuing at a reduced rate.
The traffic goes to public web data collection: price and availability monitoring, flight and hotel search, SEO and ad verification, market research, and AI training data. A permanent blocklist covers .gov and .edu, banks and financial institutions, card processors, login endpoints, sensitive APIs, any reported-abuse domain, and the user's own local network.
How it works is the full description, and our ethics page covers what we will not do.