# Product & feature comparisons - Handbook
Keeping product comparison charts up-to-date across a large website with multiple products is tricky, so we've built a way to source data from a single place. That way, if a competitor adds a new feature (or updates an existing one), we can update the data in one place and have it automatically reflected across the entire website in existing product comparison tables, blog posts, and other documentation.
To do this, we need a source of record for:
- feature definitions (each PostHog product and its feature set)
- competitor data (each competitor and their product and feature offerings)
By standardizing all features across all products and competitors, we can generate a comparison table without any hard-coded data.
## Example
This is not an ordinary Markdown table. (In fact, it's not Markdown at all!)
OutputCode
Amplitude
[compare](/blog/posthog-vs-amplitude.md)
Some product summaries
[**Product Analytics**](/product-analytics.md)
Track usage, retention, and feature adoption with comprehensive analytics
✓
✓
[**Experiments**](/experiments.md)
Run statistically rigorous A/B/n tests and validate ideas with confidence
✓
✓
Cherry-picked rows about Product Analytics
**Free usage**
Custom description for the pricing row
1 million events
10k monthly tracked users
**Autocapture**
Capture events without manual tracking
✓
✓
**SQL query editor**
Write SQL queries directly against your data without a separate data warehouse
✓
Add-on
**Cohorts**
Create cohorts of users to analyze and compare
✓
✓
See more examples in the [PostHog vs Amplitude blog post](/blog/posthog-vs-amplitude.md). All tables are dynamically rendered from data sourced from json arrays.
## Product & platform features
Feature definitions for PostHog products are stored in:
PostHog AI
```
/src/hooks/featureDefinitions/{productName}.tsx // individual products
/src/hooks/featureDefinitions/platform.tsx // overall platform
```
### Session Replay example:
`/src/hooks/featureDefinitions/session_replay.tsx`
Features can live in the `features` node, or nested inside in a logical grouping. (This is a truncated example.)
typescript
PostHog AI
```typescript
export const sessionReplayFeatures = {
summary: {
name: 'Session Replay',
description: 'Watch real user sessions to understand behavior and fix issues',
url: '/session-replay',
docsUrl: '/docs/session-replay',
},
features: {
canvas_recording: {
name: 'Canvas recording',
description: 'Capture canvas elements in your app',
},
chat_with_recordings: {
name: 'Chat with your recordings',
description: 'Discover useful recordings using AI-powered chat',
},
},
platform_support: {
description: 'Record on web and mobile across major frameworks',
features: {
web_app_recordings: {
name: 'Web app recordings',
description: 'Capture recordings from single-page apps and websites',
},
mobile_app_recordings: {
name: 'Mobile app recordings',
description: 'Capture recordings in iOS and Android apps',
},
ios_recordings: {
name: 'iOS recordings',
description: 'Record sessions from iOS mobile apps',
},
},
},
}
```
## Competitor (& PostHog) data
Competitor data is stored in:
PostHog AI
```
/src/hooks/competitorData/{competitorName}.tsx
/src/hooks/competitorData/posthog.tsx
```
### Amplitude example:
`/src/hooks/competitorData/amplitude.tsx`
Feature-level data for competitors is stored in the same format, with the exception being that products are namespaced under the `products` node in a single file instead of being spread across multiple files for each product.
There's also a `platform` node below the `product` array.
typescript
PostHog AI
```typescript
export const amplitude = {
name: 'Amplitude',
key: 'amplitude',
assets: {
icon: '/images/competitors/amplitude.svg',
comparisonArticle: '/blog/posthog-vs-amplitude',
},
products: {
session_replay: {
available: true,
pricing: {
free_tier: '1,000 recordings',
},
features: {
canvas_recording: false,
chat_with_recordings: false,
clickmaps: false,
conditional_recording: false,
},
},
},
platform: {
deployment: {
eu_hosting: true,
open_source: false,
self_host: false,
},
pricing: {
free_tier: true,
transparent_pricing: false,
usage_based_pricing: true,
},
},
}
```
## Referencing data
There are several ways to assemble competitor tables. It uses the `` component which uses `` internally.
### Compare products between competitors
This will list out the top-level product names and descriptions.
OutputCode
Amplitude
[compare](/blog/posthog-vs-amplitude.md)
[**Product Analytics**](/product-analytics.md)
Track usage, retention, and feature adoption with comprehensive analytics
✓
✓
[**Web Analytics**](/web-analytics.md)
Privacy-focused web analytics with real-time data and no sampling
✓
✓
[**Session Replay**](/session-replay.md)
Watch real user sessions to understand behavior and fix issues
✓
✓
### Render all items within a node
Use `features` to render all items inside the node.
This is helpful for comparing all features within a product without having to reference them individually.
OutputCode
Amplitude
[compare](/blog/posthog-vs-amplitude.md)
Features
**Advertising analytics**
Track ROI on Google Ads and other marketing campaigns
Beta
✓
**Actions**
Combine multiple events into a single action for analysis
✓
**AI analysis**
Surface user pain points using AI
✓
**Alerts**
Alert when types of events happen
✓
**Autocapture**
Capture events without manual tracking
✓
✓
**Cohorts**
Combine users based on properties and events for group analysis
✓
✓
**Custom events**
Manually capture custom events and properties wherever they happen
✓
✓
**Custom properties**
Add more data to custom events or users
✓
✓
**Monetization analytics**
Track purchase value, LTV, and other revenue metrics
Via [Revenue Analytics](/revenue-analytics.md)
✓
**Predictive insights**
AI-powered alerts when metrics change
✗
✓
**Real-time view**
Monitor activity on your site or app as it happens
✓
✓
**Toolbar**
Tag events or view insights on your live website or app with an overlay
✓
✗
**User profiles**
Track personally-identifiable user info like name, email, and usage data
✓
✓
Optional custom section header
[**Dashboards**](/dashboards.md)
Combine insights into shareable dashboards
✓
✓
### Compare specific features between competitors
If you want to cherry-pick specific features, just reference the key directly. (This is useful for blog posts that compare specific features between competitors in a manually set order.)
OutputCode
Amplitude
[compare](/blog/posthog-vs-amplitude.md)
**Free usage**
Monthly free tier
1 million events
10k monthly tracked users
Core features
**Autocapture**
Capture events without manual tracking
✓
✓
**SQL query editor**
Write SQL queries directly against your data without a separate data warehouse
✓
Add-on
[**Dashboards**](/dashboards.md)
Combine insights into shareable dashboards
✓
✓
### Override label/description but source values from competitor files
This is useful when referencing a global feature but want to tailor the label or description to be more personalized to the product or feature.
*Example: If there's a global data retention for 7 years but in reference to heatmaps, you might want to say "Heatmap data retained for 7 years."*
PostHog AI
```
{
label: 'Custom label',
description: 'Custom description about heatmaps',
path: 'heatmaps.features.heatmaps',
},
```
### Add custom line items with arbitrary values
If you need to add a custom row that doesn't exist in the competitor data, you can use the `values` property to specify a value for each competitor.
OutputCode
FullStory
[compare](/blog/posthog-vs-fullstory.md)
**In-app prompts and messages**
Send messages to users in your app
✓
✗
**Custom pricing tier**
Special pricing available
Enterprise only
All plans
The `values` array should have the same length as the `competitors` array, with each value corresponding to a competitor in order.
### Section headers
Add section headers to organize comparison tables into logical groups. Headers only require a `label` property:
TSX
PostHog AI
```jsx
```
Headers automatically span across all columns and are styled with a border to visually separate sections.
## Product page overrides
### Excluding sections
Product pages list out all sections within a product's feature set by default, but in some cases it doesn't make sense to do so.
For example, showing the `platform.integrations` section might make sense for the [Product Analytics comparison](/product-analytics.md#feature-comparison), but not for [LLM Analytics comparison](/llm-analytics.md#feature-comparison) where that product doesn't really integrate with the tools that are otherwise integrated across the PostHog platform.
If you want to exclude a section from rendering, you can use the `excludedSections` property.
TSX
PostHog AI
```jsx
```
For product pages, this is handled by the `excluded_sections` property in the product's feature definition file.
`/src/hooks/productData/llm_analytics.tsx`:
typescript
PostHog AI
```typescript
export const llmAnalytics = {
...
comparison: {
companies: [
{
name: 'Langfuse',
key: 'langfuse',
},
{
name: 'Langsmith',
key: 'langsmith',
},
{
name: 'Helicone',
key: 'helicone',
},
{
name: 'Braintrust',
key: 'braintrust',
},
{
name: 'PostHog',
key: 'posthog',
},
],
rows: ['llm_analytics'],
excluded_sections: ['platform'], // or an individual node like 'platform.integrations'
},
}
```
### Excluding rows with missing data
By default, the component will show rows where a competitor's cell doesn't have a value. This can be overridden on a per-product basis by setting `require_complete_data: true` in the product's feature definition file.
`/src/hooks/productData/product_analytics.tsx`:
typescript
PostHog AI
```typescript
export const productAnalytics = {
...
comparison: {
rows: ['product_analytics'],
require_complete_data: true,
},
}
```
### Community questions
Ask a question
### Was this page useful?
HelpfulCould be better