About AffiliateRails

Affiliate infrastructure should explain its decisions.

AffiliateRails is being built for product and operations teams that need more than links and a dashboard. The platform treats attribution, commissions, refunds and payouts as durable business operations.

01

The operating problem

Referral programmes cross several trust boundaries: anonymous links, authenticated customers, provider purchase events, affiliate identities and money-moving operator actions.

When those boundaries are compressed into one marketing script, retries and refunds become manual reconciliation work. AffiliateRails keeps them explicit.

02

The design stance

Stable identities, conditional writes, immutable evidence and balanced journals are core product behavior rather than implementation detail.

The aim is a programme an operator can inspect and a developer can integrate without guessing what happens after a timeout.

03

How we communicate

We publish claims only when the product, contract and evidence agree. Pricing, security and payout statements remain gated when their underlying decision is unresolved.