Awaitful vs Kickbacks
Kickbacks and Awaitful both pay developers 70% through Stripe. The differences are a lower first payout and how far you can verify what runs on your machine.
Awaitful is the one whose safety you can verify yourself: source you can read, a manifest of every field that leaves your machine, a CI test that fails the build if the client ever contacts an unlisted host, and an in-app panel that shows what leaves, live.
The short version
Kickbacks is the product this category benchmarks against. The same operator rebuilt it at kickbacks.dev and raised the developer share from 50% to 70%, so on the headline number Kickbacks and Awaitful are matched, and both cash out through Stripe.
That makes this a comparison about the things underneath the split: how soon you reach your first payout, how many places the line can show, and whether the privacy promise is something you can check.
Side by side
Every row checked against kickbacks.dev on July 11, 2026. A tag marks each row where Kickbacks leads.
| Feature | Awaitful | Kickbacks |
|---|---|---|
| Developer share | 70% | 70% |
| First payout minimum | $5, then $10 | $10 minimum |
| Payout method and reach | Stripe, United States at launch | Stripe Connect |
| Where the line shows | Four: thinking line, terminal, status bar, chat banner | Not detailed |
| Agents | Claude Code, multi-surface; Cursor and Codex path | Claude Code and CodexKickbacks leads |
| Privacy you can verify | Source-available, egress manifest, CI egress test, in-app panel | Source-available client |
| Distribution | VS Code Marketplace and Open VSX | Not stated |
| Stage | Live on both marketplaces | Live |
What Kickbacks does well
Kickbacks supports Codex alongside Claude Code, runs a block auction, and its older kickbacks.ai property reports the only real traction numbers anyone in this category shows ($51,284 paid, 100M ads, both self-reported and unverified). Its client is source-available. It is a credible, established build.
Where Awaitful is different
The same source-available start, taken further
Kickbacks publishes its client source, which is the right start. Awaitful adds a published egress manifest, a CI test that fails the build if the client talks to an unlisted host, and an in-app panel that shows what leaves your machine, so the promise is enforced end to end, not just readable.
A lower bar to your first payout
Awaitful clears your first payout at $5, then $10 after. A lower first bar means the first real money arrives sooner.
The line, in four places
Awaitful shows the sponsored line in a patched thinking line, the terminal, the status bar, or a chat banner, over one surface-agnostic backend. You pick what fits how you work.
Kickbacks runs two properties: the kickbacks.dev rebuild at 70%, compared here, and the older kickbacks.ai at 50%. Figures checked 2026-07-11.
Is anything here out of date or wrong about Kickbacks? These pages are only worth publishing if they stay true. Tell us and we will fix it.
The best comparison is running it.
Every claim on this page about Awaitful is something you can open and check. Install takes one command, and you keep 70% of what an advertiser pays for a line shown on your machine.