Frequently Asked
Questions

Everything you need to know about pricing, licensing,
and how Tracehound works.

$ Pricing & Licensing

What counts as a "service"?

A service is a logical application — your API server, your worker process, your webhook handler. If it has its own entry point and runs independently, it's a service. Monoliths count as one service.

I have 10 Kubernetes replicas. Do I pay 10x?

No. Replicas of the same service are covered under one license. You pay per logical service, not per instance, pod, or container.

What about microservices?

Each microservice that integrates Tracehound counts as one service. If you have 5 microservices using Tracehound, you need 5 licenses. Enterprise tier includes volume discounts.

Why not price per request like other tools?

Request-based pricing creates unpredictable costs and punishes success. Security should not become more expensive when your product grows. Our flat per-service model means no surprise bills.

Can I try before buying?

Yes. The Community tier is free forever for development, testing, and small projects. Upgrade to Pro when you need production features like Evidence Export and Notification API.

A Argos

How does Argos pricing work with Tracehound?

Argos is a separate product with its own license. You can use Argos standalone ($49/mo) or as a bundle with Tracehound Pro (+$29/mo). Enterprise tier includes Argos at no additional cost.

Do I need Argos if I have Tracehound?

Not necessarily. Tracehound handles request-level threats. Argos detects runtime anomalies between requests — event loop stalls, worker drift, scheduling irregularities. They complement each other but solve different problems.

Can I use Argos without Tracehound?

Yes. Argos works as a standalone runtime observer. It emits signals to your existing security infrastructure (SIEM, alerting, etc.) without requiring Tracehound.

</> Technical

Does Tracehound add latency to my requests?

Tracehound is designed with a zero-allocation hot path. Critical operations happen synchronously without GC pressure. Evidence collection and export happen asynchronously and never block request handling.

What happens if Tracehound crashes?

Tracehound uses fail-open semantics by default. If something goes wrong, your application continues to function — we never block your production traffic. This is configurable for high-security environments.

Is Tracehound a WAF replacement?

No. WAFs operate at the network edge and filter known attack patterns. Tracehound operates inside your runtime and isolates threats that bypass edge defenses. They work together — WAF is first line, Tracehound is last line.

Still have questions?

Check our documentation or reach out to our team.