Install the dregs.js tracking script and send your event data. Dregs will fingerprint devices, analyze usage patterns, and continuously score each user's Humanity, Authenticity, Uniqueness, and Behavior.
Dregs scores each visitor's Humanity on the probability that there's a real live human controlling the web browser.
Identify the unwanted bots and scrapers so you can disable or quarantine their accounts before they cause trouble.
Dregs scores each user's Authenticity based on web form submissions, profile data, and similar factors.
Sort out the disposable accounts so you can focus your onboarding and outreach efforts on real, high-intent people.
Dregs scores each user's Uniqueness, or the probability that this is the person's only account or visit to your site.
Identify duplicate accounts to deal with free trial freeloaders, content spammers, and other non-unique users.
Dregs scores each user's Behavior in your app continuously, comparing the user's activity to your ideal profiles.
Highlight your most promising users and get early warning of the troublemakers misusing your app.
Send your analytics events, and Dregs updates each user's scores moments after every action they take in your app. The scores belong to the user, not to a single check at signup, so they keep sharpening as more events arrive. When Dregs spots an abusive or suspicious activity pattern, that account's scores drop to warn you of trouble.
Official Dregs SDKs handle authentication, retries, and idempotent delivery, so a few lines start
the scoring. Read a user's scores back the same way, at whatever point in your app is worth
protecting. Browser tracking stays with the dregs.js script.
pip install dregs
npm install @dregs/sdk
com.dregs:dregs-sdk
bundle add dregs
composer require dregs/dregs-sdk
A documented REST API underneath them all.
After scoring your users, Dregs can send Notifications through your channels, open Escalations when rules are breached, and enable Full Autonomy: everything you need to sort out the riffraff and send them on their way.
As soon as you add the Dregs tracking script and start sending your events, Dregs starts analyzing your user and event data and scoring your users.
Dregs works out of the box and gets more accurate with training. In the early days you can visit the Dregs dashboard to review user scores and train Dregs on which users and behaviors fit your ideal user profile and which ones don't.
Typically, you can expect your Uniqueness and Humanity scores to be accurate from the very beginning. Authenticity scores start out pretty good and improve over time. Behavior scores take some training to dial in, since they're based on custom events that are unique to your application, and that training is what makes them fit your product.
Set up channels (email, Slack, or webhook) and tell each one which events it cares about. Dregs fires notifications the moment an event matches a channel's subscription.
Notifications give your team early warning of potential hackers, spammers, bots, and free trial abusers, or highlight high-scoring users who might appreciate extra attention.
Subscribe each channel to exactly the events it should care about: identity scoring, badge changes, escalations opening or closing. Quiet in your inbox, noisy in your automation webhook, or whatever split fits your team.
When an identity crosses a threshold you've set, Dregs opens an escalation: a stateful incident that stays open until someone on your team acknowledges or closes it.
Escalation rules let you dial in the sensitivity of your response. Urgent thresholds for potential hackers and spammers; gentler thresholds for freeloaders and trial abusers who are annoying but not an immediate threat.
Each escalation tracks through its full lifecycle (open, acknowledged, closed), so manual review becomes a clear queue of what needs attention and an auditable record of how each incident was handled.
Once Dregs is well trained and you're happy with the scoring, set up webhooks along with a sprinkling of code in your app to unlock fully autonomous abuse prevention.
Webhooks notify your app of changes in user scores. When a new user arrives or an existing user's scores change, Dregs will send your app a webhook call with the updated scores and badges for that user.
Your app can then take action on the scores to customize or curtail the user's experience, based on your own unique thresholds and requirements.
Fully autonomous abuse prevention means automatically quarantining, shadowbanning, rate limiting, or completely blocking bad actors inside your application, even while your team sleeps.
Stop freeloaders from signing up multiple times with different emails or devices to endlessly exploit free trials. Dregs detects duplicate accounts and fraudulent patterns so you can enforce fair use for everyone.
Stolen cards often enter your SaaS as throwaway accounts: bots cycling signups and payment methods to see which cards work. Dregs flags that account and device pattern almost instantly so you can stop the campaign at signup, which can also mean fewer fraudulent charges and chargebacks downstream. Card declines and disputes stay with your payment processor.
Spammers and phishers try to exploit your app to spread scams, post fake content, or send malicious links. Dregs flags suspicious signups and activity so you can keep your platform clean, compliant, and trustworthy.
SMS pumping abuses verification systems by triggering thousands of messages, inflating your costs and overwhelming services. Dregs can detect and block abnormally repetitive actions before they hit you too hard.
Fake signups using disposable emails, auto-generated names, or nonsense inputs clutter your user table. Dregs automatically identifies low-quality data and flags it so your user base remains high quality.
Attackers try to use leaked passwords to break into accounts. Dregs detects automated login attempts, unusual access patterns, and suspicious behaviors to stop credential stuffers in their tracks.
Unwanted bots and web scrapers can steal your data, overload your servers, or rip off your content without permission. Dregs identifies scraping behaviors and helps you block them while keeping false positives away from your legitimate users.
Your real customers notice spam, fake accounts, and abuse on your platform, and so do the prospects you're trying to win. Dregs helps you keep it clean and secure, giving genuine users a better experience while chasing off the troublemakers and riffraff.
Start your free trial today and see how Dregs can help you identify bots, freeloaders, and other bad actors on your platform.
Integration takes minutes, and you'll start seeing results almost immediately. Set up channels, webhooks, and escalations to keep your platform clean and free of abuse.
A: The phrase "dregs of society" has been used colloquially and in literature to refer to the lowest and most ill-behaved among us. The word dregs came into English from Old Norse and refers to the sediment or grounds at the bottom of a liquid like beer or coffee, but when applied to people (and bots) on the internet, we mean the sorts of lowlifes and miscreants that you're doubtless all too familiar with if you've operated an online SaaS for any length of time.
A: The bare minimum setup involves adding the tracking script to your app's pages, which will transmit
device fingerprints, and calling the identify and track functions when important things happen in your app.
It's quite similar to integrating with an analytics tool like Google Analytics or MixPanel. After you create your Dregs account
you'll be guided through the setup. See the getting started guide for a full walkthrough.
A: Typically you should start seeing value from the user scoring as soon as the first events arrive. Your Dregs dashboard will show at a glance who the good users are, and who are the likely bots and troublemakers, so your team can take action. It gets better once you set up channels so you don't have to check the dashboard for scores, and better still when you enable webhooks for automatic intervention by your app when Dregs detects a problem user.
A: Not directly. Dregs works at the account layer: fake signups, free trial abuse, bots, duplicates, referral fraud, and similar account problems. It doesn't process cards, decline transactions, or manage chargebacks; Stripe Radar and your payment processor handle those. But card testing usually arrives as a wave of throwaway signups, and Dregs scores those identities, so stopping them at the account can also reduce the payment fraud and chargebacks that would have followed.
A: Dregs offers tiered plans priced by the active identities you track each month, with a monthly event allowance on each plan, starting with a free trial so you can see the value before committing. Check out our pricing page for full details on plans and features.