this post was submitted on 04 Apr 2026
13 points (71.0% liked)

Selfhosted

56957 readers
479 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hey everyone,

I’ve been working on a self-hosted affiliate tracking tool after running into a common issue with existing solutions like Rewardful or FirstPromoter.

Most of them require full read-access to your billing provider (Stripe/Paddle) and operate as closed, managed services. That means handing over sensitive financial data and trusting a black-box system for attribution.

I wanted something different:

self-hosted transparent privacy-first

So I built RefearnApp — a self-hosted affiliate tracking engine.

🧠 Why this approach No third-party data access → everything runs on your own infrastructure **Transparent attribution logic **→ affiliates can verify how tracking works **Full data ownership **→ all relationships and logs stay in your database **No forced subscriptions **→ you can run it without ongoing costs ⚙️ Deployment Docker-ready Works with Coolify or any VPS Lightweight enough to run alongside existing services 🔓 Open source model

The core engine is AGPL-3.0 and fully self-hostable.

I’m following an open-core approach:

core functionality is free and open optional paid features support ongoing development 🔗 Repo

https://github.com/ZAK123DSFDF/refearnapp

I’d really appreciate feedback from people here — especially around:

setup experience architecture decisions anything missing for a self-hosted workflow

you are viewing a single comment's thread
view the rest of the comments
[–] one_old_coder@piefed.social 7 points 10 hours ago

God no, that's insulting.