Hazy built serious technology: differential privacy mechanisms for synthetic data, on-premises deployment, purpose-built for regulated industries. Banks used it. Insurers used it. It worked.
Then SAS acquired Hazy in November 2024. Now it’s “SAS Data Maker” — same technology, but locked into the SAS ecosystem.
This changes the competitive equation entirely.
What Changed After the SAS Acquisition
| Before (Hazy standalone) | After (SAS Data Maker) |
|---|---|
| Independent vendor | SAS subsidiary |
| Direct sales | SAS sales channel |
| Focused product | Part of SAS analytics suite |
| Flexible deployment | SAS infrastructure requirements |
| Startup agility | Enterprise procurement cycles |
If you were evaluating Hazy as a standalone tool, you’re now evaluating SAS as a vendor. That’s a very different conversation for procurement, IT, and budget.
Feature Comparison
| Feature | Sovereign Forger | Hazy / SAS Data Maker |
|---|---|---|
| Requires real data | ❌ | ✅ |
| Born Synthetic (zero lineage) | ✅ | ❌ |
| Differential privacy | N/A (not needed) | ✅ |
| UHNWI financial profiles | ✅ 31 archetypes | ❌ Generic |
| KYC/AML fields (29 columns) | ✅ | ❌ |
| Cultural depth | ✅ 6 geo-niches | ❌ |
| On-premises deployment | N/A (dataset delivery) | ✅ |
| Data never leaves environment | ✅ Local LLM | ✅ On-prem |
| SaaS platform | ❌ | ❌ (on-prem only) |
| Self-service purchase | ✅ | ❌ Enterprise only |
| Free sample | ✅ 100 records | ❌ |
| Open pricing | ✅ | ❌ |
| Vendor lock-in risk | None | SAS ecosystem |
| Certificate of Origin | ✅ | ❌ |
| Financial sector focus | ✅ | ✅ (banking, insurance) |
Pricing: Buy vs Procure
Sovereign Forger:
- $499 → 1,000 UHNWI profiles
- $12,500 → 100,000 profiles
- Buy today, download today
- No implementation period
- No vendor relationship required
Hazy / SAS Data Maker:
- Enterprise-only pricing (not public)
- 8-week outcome-based onboarding programs
- Dedicated Customer Success Manager per customer
- SAS licensing model
- Procurement cycle: weeks to months
For a compliance team that needs test data this quarter — not next quarter — the timeline difference matters more than the price.
The Privacy Approach: Structural vs Mathematical
Hazy’s Approach: Differential Privacy
Feed real data into the platform. Apply mathematically proven privacy guarantees (epsilon bounds) to ensure individual records cannot be reconstructed. Strong theoretical foundation. The output is provably private — with quantifiable privacy budgets.
The trade-off: You still handle real data first. You still need data processing agreements. You still need to explain to regulators what epsilon value you chose and why it’s sufficient. The math is rigorous, but the regulatory conversation is complex.
Sovereign Forger’s Approach: Structural Independence
No real data enters the pipeline. No privacy budget needed because there’s nothing to privatize. No epsilon to justify because there’s no person to protect.
The trade-off: You can’t replicate your production data’s exact distributions. The data is mathematically realistic (Pareto-distributed wealth, algebraic constraints) but not a mirror of your actual customer base.
The Ecosystem Question
Choosing Hazy/SAS Data Maker means choosing SAS. If you already run SAS analytics, that’s synergistic. If you don’t, you’re adding a new enterprise vendor relationship for one product.
Choosing Sovereign Forger means buying a dataset. No vendor relationship. No ecosystem. No implementation. No dedicated CSM. Just data.
Sometimes the simplest solution wins.
When to Choose Hazy / SAS
- You already use SAS analytics and want integrated synthetic data
- You need mathematically provable privacy guarantees (differential privacy)
- You want on-premises deployment with data that never leaves your environment
- You have enterprise procurement capabilities and timeline
- You need to replicate your exact production data distributions
When to Choose Sovereign Forger
- You need financial profiles without processing any real data
- You need UHNWI-depth data with cultural accuracy
- You want to buy data today without an enterprise sales cycle
- You don’t want vendor lock-in to the SAS ecosystem
- You need KYC/AML-specific fields (29 columns)
- You need a clean GDPR audit trail with zero data processing obligations
Download Free Sample — 100 UHNWI Profiles →
Last updated: March 2026. Hazy/SAS Data Maker data from sas.com press release (November 2024) and public documentation.
FAQ:
Q: Did SAS acquire Hazy?
A: Yes. SAS acquired Hazy in November 2024. The product is now called SAS Data Maker and is integrated into the SAS analytics ecosystem.
Q: Is Hazy still available as a standalone product?
A: No. Following the SAS acquisition, Hazy’s technology is available only through the SAS platform as SAS Data Maker. Enterprise-only, no self-service option.
Q: What is differential privacy in synthetic data?
A: Differential privacy adds mathematically calibrated noise to data generation, providing provable limits on how much any individual record can influence the output. Hazy/SAS uses this approach. Sovereign Forger does not need differential privacy because it never processes real data — the privacy guarantee is structural (Born Synthetic) rather than mathematical.
Q: How long does it take to implement Hazy vs buy Sovereign Forger?
A: Hazy/SAS Data Maker typically requires an 8-week outcome-based onboarding program with a dedicated Customer Success Manager. Sovereign Forger datasets can be purchased and downloaded immediately from the website.
Learn more about sovereign forger vs hazy and how Born Synthetic data addresses this in our glossary and comparison guides.
