About Virling
Virling is open-source revenue attribution. It joins every website visit to the payment that followed, so you can see which channel brings paying customers, not only visitors.
Who builds it
Virling is built and run by Stacklance Infotech LLP in Surat, Gujarat, India. The code is public under the AGPLv3 on GitHub, and every change, release and fix is in the open, including the changelog.
Why it exists
Traffic numbers do not pay the bills. Founders want to know which channel brought the customers who paid, and most analytics tools answer with visitors. Virling reads your payments from Stripe, Dodo Payments, Polar and LemonSqueezy with a key and joins each one to the visit before it, so a launch, a post or a newsletter is judged by what it earned.
How it is built
One Rust binary with embedded storage. There is no Postgres, ClickHouse or Redis to run, and a backup is copying one folder. You can self-host it for free, or use the hosted beta at beta.virling.com, which is open to everyone with no application.
What it does with data
Visitor IP addresses are never stored. The script sets one first-party cookie, or none in cookieless mode. The privacy policy lists every processor, what is kept and how to have it removed.
Where it is today
Virling is in early development. Releases are on GitHub and run on your own server now, the hosted beta is open, and paid hosted plans are not available yet. See pricing for the founding price and what is free.
Contact
General questions and requests: hello@virling.com. Security reports: security@virling.com. Bugs and ideas: GitHub issues.