Dregs vs Trueguard
Trueguard and Dregs both go after fake signups, trial abuse, multi-accounting, and bots on products that need real users. Trueguard is built around the verification event: you send an event, and it returns risk signals, a risk score, a bot score, and a rules decision. Those events use a durable device ID and the visitor's history, so a repeat signup isn't a blank form. Dregs scores each identity continuously as activity arrives, and prices by account rather than by verification. Both publish their pricing. Here's where each one fits.
Choose Trueguard if…
- You want a risk score and a bot score back on the verification events you send
- You want rules that can block, hold, or flag a signup in the API response
- You want a free plan (1,000 verification events a month) with no credit card
- You also want standalone email verification and phone validation APIs, each on its own meter
Choose Dregs if…
- You want every active account scored as events arrive, without metering each verification
- You want to see exactly why a score moved, so false positives are evidence you can check
- You want self-serve pricing from $17/month, with API access, webhooks, and 90 days of history on the entry plan
- You want custom rules and lists: badges, escalations, and (on Advanced) your own analyzers and datasets
Which is better, Dregs or Trueguard?
It depends on when the decision has to land. Trueguard is the better choice when you want a risk score, a bot score, and a rules decision to block, hold, or flag the verification events you send, or a standalone email verification API. As of November 2, 2026, 1,000 events a month are free. Dregs is the better choice when a SaaS operator wants every active account scored continuously, each score openable into its observations, from $17/month with 90 days of history. If you only score the signups and logins you send, Trueguard's Standard plan can be the smaller bill.
At a glance
| Dregs | Trueguard | |
|---|---|---|
| Built for | SaaS teams fighting fake accounts, free trial abuse, multi-accounting, and bots | SaaS teams fighting fake signups, bots, free tier abuse, and multi-accounting |
| Approach | Continuous identity scoring over each account's accumulated events, devices, and relationships | A verification event that returns scores and a rules decision, using device, network, email, and visitor history |
| What you get back | Four ongoing scores (Humanity, Authenticity, Uniqueness, Behavior), plus badges and escalations | A risk score and a separate bot score on that event, plus a rules decision |
| Scoring transparency | Every score opens into named observations with a value, a confidence, and a plain-English explanation | Risk and bot scores that combine device, network, email, and geolocation signals; rules act on those signals |
| Enforcement | Badges, escalations, and webhooks your application acts on | Rules in the API response: block, require verification, hold for review, or flag |
| Pricing | Published, from $17/month per active identity, plus a checks allowance | Published, free for 1,000 verification events; Standard $49.99/month for 10,000, then $5 per 1,000 |
| Getting started | Self-serve, 14-day trial, no credit card | Self-serve free plan, no credit card |
| Platform | Server SDKs for Python, Node, Java, Ruby, PHP, Rust, and Elixir. Public OpenAPI document, including the groups API. Dregs MCP server for AI agents. | JavaScript package and Event API. Rules can block, require verification, hold for review, or flag in the response. |
Also included
New customers get a default escalation for the Pumping Suspected badge (SMS pumping) and one for the Registration Bombing Suspected badge (registration bombing). Each stays in the dashboard unless you add a notification channel.
You can record the organizations, teams, and workspaces your users belong to. Groups aren't scored. Groups can inform scoring.
What Trueguard does well
Trueguard publishes its prices and a free plan, and registration is open at
app.trueguard.io/register
with no credit card. The integration is a JavaScript snippet plus a backend call. The
docs
start with @trueguard/trueguard-js opening a verification session in the browser, then
your server posts an event to the
Event API
with that verification ID. The API is described as scoring a signup or a login. The published
examples are a registration attempt, before the account exists, and a successful registration.
The signal set is built for fake signups, trial abuse, and multi-accounting. Trueguard lists durable device IDs that survive cookie clears, incognito sessions, and VPN or proxy setups, email intelligence for disposable and low-quality addresses, network analysis for VPNs, proxies, and IP clusters, geolocation, a risk score and a separate bot score, and a rules engine. On the fake account page, those rules can block the registration, require verification, hold it for review, or let it through and flag it, and the decision comes back in the API response. The trial abuse page adds that device history persists across sessions, so a later signup from the same device is still visible. That's a practical fit when the decision has to land on the attempt in front of you.
Dregs doesn't return a block, a hold, a flag, or a verification requirement on the signup in front of you. Your application acts on badges, escalations, and webhooks.
Trueguard also sells a standalone Email Verification API. As of November 2, 2026 it includes 100 validations a month free, and a Standard plan at $49.99/month for 50,000 validations, then $0.001 per validation. Trueguard describes it as its own product, with the same API key and a separate meter, so a validation isn't a Fraud Prevention verification event. A standalone Phone Validation API has its own meter: 100 checks a month free, or $49.99/month for 20,000 checks, then $0.0025 per check, with custom pricing above 500,000 checks a month. Trueguard says the phone check is not part of the fraud event today. Dregs has no phone validation product.
Where Dregs takes a different approach
Verification events and continuous scoring
Trueguard's Fraud Prevention plans are sized in verification events: 1,000 a month on the free plan, 10,000 on Standard, then $5 per additional 1,000. You open a verification session in the browser and send an event from your backend when you want scores and a rules decision. The event can draw on the device ID and earlier history, so it isn't a blind look at one form, but a later look at the same account is another verification event. The commercial unit is the event.
Dregs prices by active identity instead. An account with at least one tracked event in the billing month counts once, and Dregs keeps scoring the account after the verification, on Humanity, Authenticity, Uniqueness, and Behavior, as further events arrive. Badges, escalations, and webhooks follow moments after new activity changes the picture, and you can train the scoring on accounts you already trust. That monthly count is the set of accounts you're watching for abuse, which is a different quantity from a stack of verification events, so the two don't line up one to one. There's more on this distinction on the pricing page.
Scores you can open
Trueguard returns a risk score and a separate bot score, and rules act on the signals you configure. The response answers the event you sent. In Dregs, every score is a standing reading of the account, composed of observations that each carry a value, a confidence, and a plain-English explanation, so you can open a score and see exactly why it moved. False positives are part of fraud detection. Seeing the observation behind a flag is how you keep them from costing you a real customer, and how a team ends up doing less manual review.
The response lives in your application
Trueguard's rules engine ships on every Fraud Prevention plan, and it can answer inside the API response, which is what you want when the signup itself should be blocked, held, or flagged. Dregs raises badges and escalations and calls webhooks, so your application decides whether to step up, limit, or leave the account alone. Custom rules and lists are part of that: badge rules and escalation rules on every plan, and on Advanced your own analyzers and datasets inside the scoring pipeline.
Trueguard pricing vs Dregs pricing
Dregs pricing
- Entry plan
- $17/month (100 active identities)
- Mid tier
- $177/month (5,000 identities)
- Top published tier
- $377/month (10,000 identities)
- Metering
- Per active identity
- Checks
- 500,000 (Starter), 2,500,000 (Growth), 5,000,000 (Advanced)
- Event history
- 90–365 days, by plan
- Free trial
- 14 days, no credit card
Trueguard pricing
- Free
- $0/month (1,000 verification events)
- Standard
- $49.99/month (10,000 verification events)
- After that
- $5 per additional 1,000 verification events
- Enterprise
- Custom
- Metering
- Per verification event
- Free start
- Free plan, no credit card
- Phone Validation API
- 100 checks a month free, or $49.99/month for 20,000 checks, then $0.0025 per check. Custom pricing above 500,000 checks a month.
The two pricing units don't convert: ten thousand verification events aren't ten thousand identities. If you only need a score on the signups and logins you choose to send, Trueguard's Standard plan can be the smaller bill. If every active account should keep a score as it's used, per-identity pricing fits that work better. The $49.99 figure also appears on Trueguard's email verification product, for 50,000 validations, and on its phone validation product, for 20,000 checks. Those three $49.99 prices are different products, so check which plan that price belongs to.
The bottom line
Trueguard is a strong choice when you want a published free plan and a rules decision on the verification events you send, at signup or at a later login, with device history carried into the next attempt. Dregs is the stronger choice when you want continuous, explained scores on the accounts themselves, on a self-serve plan from $17/month with 90 days of history at the entry tier. That's the shape of fake signups, free trial abuse, and duplicate accounts. Comparing another product that meters an evaluation per action? See Dregs vs Rupt. ShieldLabs bills per identification. See Dregs vs ShieldLabs.
Frequently Asked Questions
Q: Which is better, Dregs or Trueguard?
A: It depends on when the decision has to land. Trueguard is the better choice when you want a risk score, a bot score, and a rules decision to block, hold, or flag the verification events you send, or a standalone email verification API. As of November 2, 2026, 1,000 events a month are free. Dregs is the better choice when a SaaS operator wants every active account scored continuously, each score openable into its observations, from $17/month with 90 days of history. If you only score the signups and logins you send, Trueguard's Standard plan can be the smaller bill.
Q: Is Dregs a good Trueguard alternative?
A: Yes, on the overlap. Both cover fake signups, free trial abuse, multi-accounting, and bots in SaaS. Trueguard does that with a risk score, a bot score, and a rules decision on the verification events you send, including a free plan with 1,000 events a month. Dregs does it by scoring every active account continuously, with each score openable into the observations behind it, on a self-serve plan from $17/month.
Q: How much does Trueguard cost?
A: As of November 2, 2026, Trueguard's Fraud Prevention free plan is $0/month for 1,000 verification events, with no credit card. Standard is $49.99/month for 10,000 verification events, then $5 per additional 1,000. Enterprise is custom. A separate Email Verification API uses its own meter: 100 validations a month free, or $49.99/month for 50,000 validations and $0.001 per validation after that. A separate Phone Validation API uses another meter: 100 checks a month free, or $49.99/month for 20,000 checks and $0.0025 per check after that, with custom pricing above 500,000 checks a month. Dregs starts at $17/month per active identity, with 90 days of event history on that plan. Dregs has no phone validation product.
Q: What is the main difference between Dregs and Trueguard?
A: The unit of work. Trueguard meters verification events: you send an event, and you get scores and a rules decision for that moment. Their docs describe signup and login events, and the published examples are a registration attempt and a successful registration. The event can use a durable device ID and earlier history, so it isn't a blank look at a single form, but a later look at the same account is another verification event. Dregs meters active identities. An account with at least one tracked event in the billing month counts once, and its Humanity, Authenticity, Uniqueness, and Behavior scores keep updating as further events arrive. The two units don't convert into each other.
Q: Does Trueguard's email verification API share the Fraud Prevention meter?
A: No. Trueguard sells email verification as a standalone product, with its own quota, and says you can buy it without the main fraud-prevention flow. As of November 2, 2026 that API includes 100 validations a month free and a $49.99 Standard plan for 50,000 validations, then $0.001 each. One request to the validation endpoint is one validation. A Phone Validation API is a third meter: 100 checks a month free, $49.99 a month for 20,000 checks, then $0.0025 per check, and custom pricing above 500,000 checks a month. One request to that endpoint is one check. Trueguard says the phone check is not part of the fraud event today. Fraud Prevention plans count verification events instead, at 1,000 on the free plan or 10,000 on the $49.99 Standard plan. The three $49.99 prices are different products.
Stop fake signups, trial abuse, and duplicate accounts.
Dregs protects SaaS accounts by scoring Humanity, Authenticity, Uniqueness, and Behavior as activity arrives, with badges, escalations, and webhooks when the picture changes. 14-day free trial, no credit card.
Schedule a DemoWe keep these pages current. If anything is out of date, readers and the companies we compare can tell us on the contact page.