Predictable pricing. Zero ingestion anxiety.
Start FreeSimple Setup
Deploy in minutes
Global Access
Use from anywhere
Expert Support
Chat, email, and consulting available
New Relic is the pioneer of APM with 17 years of platform maturity, 100 GB free monthly ingestion, and one of the most generous free tiers in the industry. We respect that. This page is an honest look at where IAPM takes a different approach, where New Relic excels, and how you can evaluate both with the same production data.
Your bill spikes when you need observability most
Source: per-GB ingestion pricing
The Ingestion Anxiety Problem
Your bill spikes when you need observability most.
- $0.40 per GB ingested: during normal operations, that feels manageable. During an incident, when your systems are flooding logs and traces, your telemetry volume spikes and so does your bill.
- Teams learn to cope by under-instrumenting, adding drop filters, and hesitating before enabling verbose logging during outages.
- Perverse incentive: the moment you need observability the most is the moment it costs the most.
Predictable pricing. Full instrumentation. Zero anxiety.
What If Your Bill Never Changed During an Incident?
Per-node pricing. No ingestion meters.
- Per-node pricing: whether you ingest 100 GB or 1 TB during an outage, your bill stays the same.
- Instrument everything. Log everything. Trace everything. Your cost is predictable: nodes times tier price.
- No drop filters to protect your budget. No anxiety about enabling debug logging in production. Just full observability, all the time.
Zero proprietary agents. Full OTel ecosystem.
Architecture: How We Differ
OpenTelemetry exclusive vs proprietary agents.
IAPM is built exclusively on OpenTelemetry. No proprietary agents to install, license, or maintain. Your instrumentation works with any OTel-compatible backend, so you are never locked in.
New Relic retrofitted OpenTelemetry support onto a 17-year-old architecture built around proprietary agents. IAPM was built from the ground up for OpenTelemetry. Beyond architecture, IAPM replaces the dashboard-hopping workflow with a spatial topology where your services, their relationships, and their telemetry data live in a single 3D environment.
| Aspect | IAPM | New Relic |
|---|---|---|
| Instrumentation | Standard OpenTelemetry SDKs only | Proprietary agents + retrofitted OTel OTLP ingestion |
| Data Ingestion | Direct OTLP (gRPC + HTTP) | Proprietary intake API, OTLP endpoint available |
| Visualization | 3D spatial topology + web dashboards | 2D dashboards, service maps, notebooks |
| Vendor Lock-in | None. Change one endpoint URL to leave. | Proprietary agents, NRQL query language, proprietary APIs |
| OTel Support | Built from the ground up for OTel | OTLP ingestion supported, but platform built on proprietary agents |
| Integrations | OTel ecosystem (community-driven, any backend) | 780+ quickstart integrations |
Tessa fixes code. You review it. You own it.
| Capability | Tessa (IAPM) | NRAI / SRE Agent (New Relic) |
|---|---|---|
| Codebase Access | Full workspace: read, search, rename, modify | No codebase access |
| Production Context | 3D topology + traces + metrics | Dashboard metrics + traces + NRQL |
| Code Fixes | Fixes code. You review, you own it. | Explains issues and generates NRQL queries, no code changes |
| Pricing | Included in every paid tier | CCU-based Advanced Compute pricing (verified as of March 2026, source) |
| Accountability | Human on the loop | Investigation summaries for human review |
AI: Tessa vs NRAI & SRE Agent
Human on the loop.
Tessa connects your production telemetry to your codebase. Add your repositories as workspaces, and Tessa traces a production issue from your 3D topology straight to the source file, then makes the fix.
Your code stays in your workspace. You review the changes. You commit when ready. Tessa does the work; you own the outcome.
New Relic's NRAI and SRE Agent provide investigation summaries, generate NRQL queries, and explain what happened. When the investigation is done, you still context-switch to your IDE to make the fix. And AI usage is billed via CCU-based Advanced Compute, meaning your AI costs spike during the same incidents that spike your ingestion costs. Tessa closes both gaps.
One price. Everything included.
Pricing: The Full Picture
Scenario: 40 nodes, 10 engineers.
New Relic's pricing appears simple, but the costs add up quickly when you factor in full platform users, data ingestion, and AI features for a production team.
- No per-user licensing: IAPM does not charge per seat. New Relic charges $349/user/month for full platform access on Pro.
- No per-GB surprises: IAPM does not charge per GB of data ingested. Your bill is the same whether you ingest 100 GB or 1 TB.
- No AI compute charges: Tessa is included in every paid tier. No CCU-based billing for AI features.
- Predictable math: Nodes x tier price = monthly cost. Count your application instances and you know your bill.
| Line Item | IAPM | New Relic |
|---|---|---|
| Platform User Licensing | No per-user fees | $349/user/mo x 10 = $3,490 |
| Data Ingestion (500 GB/mo) | Included | $0.40/GB x 400 GB (after free 100 GB) = $160 |
| Infrastructure Monitoring | N/A | Included (no per-host charge) |
| APM + Logs + Traces | Included | Included (data ingest covers all signals) |
| AI Assistant | Included (Tessa) | CCU-based Advanced Compute (variable) |
| Estimated Monthly Total | $1,575 (Analyze) | $3,650+ before AI compute |
New Relic pricing based on Pro edition annual commitment rates from newrelic.com/pricing, verified as of March 2026. Actual costs vary by usage. IAPM pricing from immersivefusion.com/pricing. All prices USD.
You don't have to rip and replace
Run Both. Migrate Gradually.
Same telemetry, two destinations, zero re-instrumentation.
- Dual-destination: Your OTel Collector fans out telemetry to both IAPM and New Relic simultaneously.
- No code changes: If you already use OTel SDKs, your instrumentation does not change.
- If you use New Relic agents: Keep them for legacy services. New services start with OTel + IAPM. Migrate at your own pace.
- Exit guarantee: If IAPM is not right for you, change one endpoint URL. Your instrumentation stays exactly the same.
Dual-Destination Collector Config
exporters:
otlp/iapm:
endpoint: "https://otlp.iapm.app"
headers:
API-Key: "YOUR-API-KEY"
otlp/newrelic:
endpoint: "otlp.nr-data.net:4317"
headers:
api-key: "${NEW_RELIC_LICENSE_KEY}"
service:
pipelines:
traces:
exporters: [otlp/iapm, otlp/newrelic]
metrics:
exporters: [otlp/iapm, otlp/newrelic]Standard OTel Collector config. Same telemetry, two destinations.
See what our customers are saying
Testimonial from the US Defense Information Systems Agency (DISA/disa.mil) talkWatch the testimonial from the DISA TEM talk | Request the full DISA TEM talk video
The Better Way to Monitor and Manage Your Software
Streamlined Setup
Simple integration
Cloud-native and open source friendly
Rapid Root Cause Analysis
Intuitive tooling
Find answers in a single glance. Know the health of your application
AI Powered
AI Assistant by your side
Unlock the power of AI for assistance and resolution
Intuitive Solutions
Conventional and Immersive
Expert tools for every user:
DevOps, SRE, Infra, Education