One Rust core.
Compiled native, everywhere.
Every Cash Raven SDK, from Electron to Android to Tizen, is the same small Rust engine (cr-core) behind a stable FFI. It has no garbage collector or runtime, and never needs a rebuild when Electron updates. Here's exactly what it does on a device.
- 01 · YOUR APP
SDK inside your app
After the user opts in, the Rust core opens one encrypted tunnel and waits. It can't read app data. It's a bandwidth relay, not a library with hooks into your code.
- 02 · EDGE
Our edge DNS
GeoDNS routes the device to the nearest relay point. Authentication is per developer key, and every cap you'll read below is enforced server-side too, so the device and the relay both say no.
- 03 · FILTER
The gateway & blacklist
Customer requests pass the domain blacklist (.gov, .edu, banks, payment sites, login endpoints, every reported-abuse domain), port denylist and per-customer usage limits before a single byte reaches a device.
- 04 · PUBLIC WEB
A public page loads
The request fetches public web data (a product price, a flight fare, a search result) from the device's residential IP. Nothing is stored on the device and nothing personal leaves it.
The reverse path is identical: response bytes stream back through the same encrypted tunnel. The SDK counts every byte against its caps as they pass.
Hard limits. No API to disable them.
The SDK runs whenever the device can afford it, and what counts as "afford it" isn't ours or yours to loosen. Every guarantee is enforced inside the compiled core.
Bandwidth ceiling
A hard throughput cap per device. Your users never feel their connection change; the relay enforces the same ceiling from its side.
Data volume caps
Daily and monthly limits, with far tighter behaviour on mobile data than on WiFi. The core detects the network type itself.
CPU & RAM budget
A featherweight Rust core inside a strict compute budget. Approach it and sharing pauses before the user could notice.
Your app comes first
The relay is a background task and stays one. It yields to the app it lives in rather than competing with it for the device.
Port & network denylist
SSH, RDP, SMB, databases and every internal IP range are blocked in the compiled core. Additions can only tighten the list, never loosen it.
Nothing personal, ever
Only the IP address and the bandwidth. Never files, accounts, or browsing history.
When a limit is reached — a data cap, or sustained load on the device — the SDK doesn't just throttle. It opts the device out automatically and checks back later. The user can also opt out permanently, any time, from the control your app is required to ship.
One agreement, published from one place.
The consent wording is published centrally by our team and fetched by every SDK, so a Windows tray app and an Android TV show the exact same text. Your users always see the current agreement, not the one compiled into last year's build.
- Theme it freely. Colors, your app name, button labels. No approval needed.
- Add your own paragraphs between ours. Each of our paragraphs carries a content fingerprint, so if the canonical wording changes, your insertion is flagged for re-review instead of silently re-attaching to text nobody approved it against.
- Replace the wording outright — with per-app approval from our compliance team. Opt-in and opt-out remain mandatory either way.
Small enough to forget it's there.
- No runtime, no GC
- native code, deterministic memory
- One codebase, six platforms
- the caps can't drift between platforms
- Stable C ABI
- C · C++ · C# · Swift · Go · Python · Rust · JS
- No Electron rebuilds
- FFI-bound, survives every Electron version
Memory safety isn't a slogan here. It's why we're comfortable running inside your process, on your users' devices.
If an app asked you to share bandwidth
Most people who land here have just been shown a consent screen inside an app they use. To be clear about the money first: through a partner app the app's publisher is paid, not you — that is what lets them keep the app free or ad-free. Building an app? The developer questions are in the docs.
What is Cash Raven, and why did an app ask me about it?
Cash Raven is how the app you are using pays for itself without showing you ads. If you agree, a small, capped share of bandwidth your device is not using is relayed for public web data collection, and the app's publisher is paid for it. You are not charged anything, and nothing is shown to you afterwards. If you decline, the app carries on exactly as before.
What is my connection actually used for?
Collecting publicly available web data: price and availability monitoring, flight and hotel search, SEO and ad verification, market research, and AI training data. A request is made from your IP address, a public page is fetched, and the page comes back. Nothing is stored on your device.
What can Cash Raven see on my device?
Your IP address and the bandwidth it relays. That is the whole list. It cannot read your files, your accounts, your messages or your browsing history — it is a bandwidth relay, not a program with access to what you do. It is not a keylogger, it does not screenshot, and it does not inspect the traffic of any other app.
Will this slow my device or my internet down?
It is built not to. A hard bandwidth ceiling means your connection speed is unaffected, and a CPU and RAM budget means the app you are using keeps priority — the relay is a background task and stays one. If either limit is approached, sharing stops on its own and checks back later.
Does it use my mobile data?
It behaves far more conservatively off WiFi, with much tighter caps on mobile data, and it detects which kind of network you are on itself. If you would rather it never used mobile data at all, opting out is one control in the app you are using.
Is anything blocked?
Yes, permanently and for every customer: all .gov and .edu domains, banks and financial institutions, card processors and payment sites, login and authentication endpoints, sensitive API endpoints, any domain with a reported abuse complaint, and your own local network. The list only ever grows.
Who is buying this, and are they checked?
Consumers and businesses collecting public web data, through Rayobyte — the same company, in business since 2015. We do not claim every buyer is vetted before their first request. Every customer runs under usage limits and alert policies from day one, and tripping one — a suspicious endpoint, an odd request pattern, unusual volume against a single site — forces identity verification through Sumsub before any further traffic.
How do I stop?
Every app that integrates Cash Raven is required to ship a visible opt-out control, and we check for it before the app is approved. Turning it off is immediate and permanent until you turn it back on. The SDK also opts your device out by itself whenever a protection trigger is hit.
Do I get paid for this?
Not through a partner app — the app's publisher is paid, which is what lets them keep the app free or ad-free for you. Cash Raven also publishes its own standalone app on Google Play, and that one does pay the person running it.
Am I old enough to agree to this?
The consent screen asks you to confirm you are at least 18, or that you have a legal guardian's permission. If neither is true, decline.
See it run on your own build.
Sign up free, drop the SDK in, and watch your first devices tunnel within the hour.