- If you are not sure Datadog is the right long-term platform
- NoBS’ specialization can accelerate Datadog adoption, which can raise switching costs if you later move to New Relic, Dynatrace, Grafana Cloud/LGTM, Elastic, etc.
- If you require publicly documented security certifications
- If your vendor risk program requires SOC 2 Type II and/or ISO 27001 evidence on a public trust page, NoBS does not appear to provide that publicly (based on available sources).
- If you need broad transformation beyond observability
- For large programs spanning cloud migration, app modernization, data platform work, and security governance, a broader SI may be more appropriate.
- If your main problem is not “Datadog execution,” but “observability strategy”
- Teams needing cross-vendor OpenTelemetry architecture, governance, and multi-backend portability may prefer vendor-agnostic specialists.
- If budget constraints are tight and you can tolerate slower progress
- Hiring/learning internally can be cheaper (cash-wise) but slower; NoBS is positioned as a premium acceleration layer.
- Limited independent validation
- NoBS has minimal third-party review presence on major platforms (G2 shows 0 reviews), reducing the ability to assess typical delivery quality and support experience.
- Pricing transparency
- No public pricing tiers were found; buyers should expect scoping calls and potentially variable pricing based on environment complexity.
- Security/compliance documentation
- No public SOC 2 / ISO documentation found; this can slow enterprise procurement.
- Tool lock-in risk
- NoBS is explicitly Datadog-only; teams looking for portability (e.g., OpenTelemetry-first with easy backend switching) should treat this as a strategic constraint.