Skip to content
testcritic

Gretel.ai vs Hoverfly

Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.

Entry price

Quote on request

Quote only

Free and open source

Open source

What drives the bill

The metric that actually scales your invoice.

The old credit-based self-serve tier is gone. The successor microservices are licensed through NVIDIA AI Enterprise; NeMo Data Designer can be tried on build.nvidia.com.

Free and open source. You pay in engineering time and CI minutes.

Free tier

Everything, self-hosted

Open source

Apache-2.0

Self-hostable

No-code authoring

Languages

PythonCodeless
GoJavaPythonCodeless

Platforms

API
API

Fits teams

Enterprise
Scale-up / mid-marketEnterprise

Adoption

Emerging

NVIDIA (formerly Gretel) · since 2019

Emerging

SpectoLabs · since 2016

Strengths

  • Formal differential-privacy guarantees rather than best-effort masking, now via DP-SGD in NeMo Safe Synthesizer.
  • Synthetic data preserves statistical relationships useful for analytics and model training.
  • Backed by NVIDIA's platform investment rather than a single startup's runway.
  • Capture mode produces a realistic simulation from live traffic with no authoring.
  • Latency injection makes it useful for performance and resilience testing too.
  • Small footprint — a single Go binary.

Limitations

  • No longer buyable as Gretel — you are procuring NVIDIA AI Enterprise, which is far heavier than the old self-serve signup.
  • Model training adds time and cost compared to rule-based masking.
  • Safe Synthesizer trains on a real dataset, so it does not help with greenfield data that does not exist yet.
  • Smaller community and slower development than WireMock.
  • Proxy configuration in complex networks takes effort.
  • Captured simulations need periodic refresh.

Best for

Regulated enterprises already standardising on NVIDIA AI Enterprise. Teams that wanted Gretel's self-serve tier should look at Tonic or Neosync instead.

Teams needing lightweight service virtualisation against real recorded traffic.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.