Docs · Ambassadors
Get paid for amplifying indie projects
A complete guide to being an ambassador on Raws.dev — joining, sharing, earning, climbing the tier ladder.
How to join a project
- Direct invite. The project owner sends you an invite — accept from /my/ambassadors or via the in-app notification.
- Public application. When a project's program is open, apply at
/p/<slug>/become-ambassador. The owner reviews and approves. - Email invite. If you don't have a Raws.dev account yet, the link in your invite mail signs you up and adds you in one shot.
The welcome tour
The first time you visit a project's ambassador hub after being approved, you're auto-redirected to a one-page welcome tour: your referral URL with a copy button, the media kit, the open missions count, and the group chat link. Once dismissed, the redirect never fires again — but the page stays accessible at /p/<slug>/ambassadors/welcome if you want to revisit.
Your referral link
Every project gives you a personal short link: raws.dev/r/<slug>/<your-handle>. Visits, signups, tips and conversions arriving via this link are credited to you.
Depending on the project, the link either lands on the Raws.dev project page (with a 30-day attribution cookie) or redirects directly to the builder's external SaaS (with utm params identifying you as the source). Either way you get full credit.
Tier system: Bronze / Silver / Gold
Auto-promoted from your cross-project contribution. The medal badge shows on your profile, in the public ambassador directory, and on every project board you support.
| Tier | Requirement |
|---|---|
| Bronze | ≥1 active ambassador role |
| Silver | ≥100 cross-project visits OR ≥1 approved mission |
| Gold | ≥500 visits AND ≥3 approved missions |
Recomputed when you join, when a mission is approved, when a role is revoked, plus a daily cron sweep for users crossing thresholds via accumulated traffic.
Claiming missions
Missions are specific tasks the project would love help with. From /p/<slug>/ambassadors/missions:
- Claim a mission you want to tackle. This locks it to you (others can still see it).
- Do the thing — write the post, record the video, publish the article.
- Paste the public URL of your work + click "I shared it". This submits the mission for review.
- The owner approves (counts toward Gold tier) or rejects (with optional reason — you can re-do).
Share templates
Some projects offer pre-written posts you can fire with one click. Open the Templates tab — for each template, you'll see the body with your referral link already substituted, plus a "Post on {platform}" button that opens the right composer (X, LinkedIn, Reddit, Hacker News, Bluesky) with the text prefilled. For platforms without a share intent (Mastodon, blogs), copy the text.
Getting paid
Two revenue streams, both paid via Stripe Connect transfer:
- Tip commissions. When a tip lands on a project via your referral link, you earn the project's configured percentage (0/30/50/80%). Settled the moment the tip succeeds.
- Per-signup payouts. When a referral of yours signs up on the project's external SaaS, you earn the configured fixed amount.
Stripe Connect onboarding is required to receive payouts. If you don't have it set up yet, your earnings stay in pending — they settle automatically the moment you finish onboarding (no manual claim step). Onboard from Settings → Tipping & payouts.
Cross-project dashboard
/my/ambassadors aggregates everything: lifetime visits driven, upvotes referred, tips generated, missions approved, current tier, plus a per-role breakdown of last-30-day stats. Pending invites and pending applications surface here too.
A weekly digest email lands every Monday morning with your last-7-days summary across every project you ambassador for, plus a per-project pulse (new devlogs, open missions). Toggle on/off in profile settings via the email digest opt-in.
Vetting projects before you commit
Before joining a project that pays per-signup, check the /p/<slug>/become-ambassador landing — it shows the configured payout, last 30-day conversion count, "last paid signup" age, and a red warning if the project has had ≥100 ambassador visits in 30 days but reported zero conversions.
That last warning means the builder either has a broken integration or isn't honouring payouts. The system can't force them to fire conversion events on their own server — but it does surface the discrepancy publicly so you can vote with your time.