Introduction
Virling is open-source revenue analytics. It joins every visit to the payment that followed, so you can see which channels make you money, not just traffic.
What Virling answers
- Revenue by channel. Which channel brought the most revenue this month, after refunds.
- Value per visitor. What a visitor from each source is worth, so a launch or a Reddit post can be judged by money instead of pageviews.
- The path before payment. Which sessions a paying customer had in the lookback window, and which one got the credit.
What works today
- A tracking script under 1 KB gzipped that records pageviews, referrers, UTM tags, single-page-app route changes and custom goals, with a first-party visitor ID. See Add the script.
- An optional cookieless mode that counts visitors with a daily salted hash.
- Event ingest into embedded DuckDB with bot filtering, a per-site rate limit and channel rules. Visitor IPs are never stored.
- Payment sync from Stripe, Dodo Payments, Polar and LemonSqueezy with a read-only key: a 90-day backfill, then a poll every minute.
- Attribution with two models and a configurable lookback window, renewals that inherit the first payment’s channel, and payment journeys in the app.
- Magic-link sign-in and an onboarding flow, served when you start the server with
--app.
Virling runs as one Rust binary with embedded storage. There is no Postgres, ClickHouse or Redis to run next to it. See How Virling works.
Project status
Virling is in early development. The current release is v0.1.0. Expect breaking changes until a stable release, and read the changelog before you upgrade.
The hosted plan at app.virling.com is Not available yet. Today you run Virling on your own server. See Hosted plan.
License
Virling is licensed under AGPL-3.0. Self-host it freely. If you run a modified version as a service, share your changes. It is built by Stacklance Infotech LLP.
Next
Follow the Quickstart to go from an empty server to your first attributed payment.