Softwr

Technology · head to head

PostHog vs Syft

PostHog logo

PostHog

Technology

The single platform to analyze, test, observe, and deploy new features

From
Free
Rated
-
Full reviewWebsite
Syft logo

Syft

Cybersecurity

Generates a software bill of materials from images, filesystems and archives

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: PostHog the free tier covers 1M events, 5K web session recordings and 2.5K mobile recordings per month before usage-based billing starts; Syft lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller.
  • They diverge on capability: PostHog covers Product analytics, Syft covers Multi-format output.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which PostHog and Syft actually diverge.

Attributes where PostHog and Syft differ
AttributePostHogSyft
Pricing modelusage-basedOpen source, no licence fee
PlatformsWeb, Ios, Android, ApimacOS, Linux, Windows, Docker
CategoryTechnologyCybersecurity
Founded2020Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in PostHog

  • Product analytics
  • Session recording
  • Feature flags
  • A/B testing
  • Heatmaps
  • SQL access
  • Data warehouse
  • Apps platform

Only in Syft

  • Multi-format output
  • Broad ecosystem coverage
  • Binary classifiers
  • In-toto attestations
  • Library and CLI
  • Pairs with Grype

What people use each for

The jobs each tool is most often brought in to do.

PostHog

  • Product analyticsnot Syft
  • Feature experimentationnot Syft
  • User behavior trackingnot Syft
  • A/B testingnot Syft
  • Debug production issuesnot Syft

Syft

  • Producing a bill of materials for a customer or regulator that requires onenot PostHog
  • Feeding an inventory into a vulnerability scanner rather than scanning images directlynot PostHog
  • Recording what shipped in a build so a future disclosure can be answered quicklynot PostHog
  • Public sector work where an SBOM is a contractual deliverablenot PostHog

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

PostHog

  • The free tier covers 1M events, 5K web session recordings and 2.5K mobile recordings per month before usage-based billing starts
  • Accounts without a card on file are limited to 1 project; adding one raises it to 6
  • Data retention is 1 year until a card is added, which extends it to 7 years
  • Support is community-only until the account is on a paid plan
  • Error tracking is capped at 100K exceptions and surveys at 1500 responses per month on the free tier

Syft

  • Lockfile parsing can drop packages silently. An open issue filed in August 2026 reports the yarn v1 cataloguer returning 118 of 745 packages with no error raised, which means a complete bill of materials and an 84 percent incomplete one look identical to the caller.
  • Fidelity varies sharply by ecosystem. Conan for C and C++, Haskell and Terraform get cataloguer support with no licence data, no dependency relationships and no file ownership, so a C and C++ shop gets the least from it.
  • Binary classification yields no licence or dependency metadata, and vendored or statically linked code is exactly where supply chain risk hides, so the blind spot and the risk overlap.
  • Incorrect CPE values and CPE collisions are recorded as open issues, and since Grype matches on CPE and PURL, an inventory error becomes a false negative in the security report downstream.
  • An inventory is not a risk assessment. Even a perfect bill of materials says a vulnerable version is present, never that the vulnerable function is called, and the triage burden lands entirely on the reader.

Pricing, plan by plan

PostHog

Free
  • FreeFree
    • 1M events/month
    • 5K sessions/month
    • Unlimited users
  • Paid$undefined/month
    • $0.00031/event
    • $0.005/session
    • Advanced permissions
  • Enterprise$undefined/month
    • SAML SSO
    • Advanced security
    • Dedicated support

Syft

Free
  • SyftFree
    • Apache-2.0
    • No usage limits
    • Community support
  • Anchore Enterprise$undefined/year
    • Policy enforcement and reporting
    • Federal and commercial tiers
    • Pricing not published, quoted on request

Which should you pick?

Choose PostHog if

  • You need product analytics.
  • You want to start without paying.
  • You work on Web, Ios, Android, Api.
  • You also want session recording.
PostHog review

Choose Syft if

  • You need multi-format output.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Docker.
  • You also want broad ecosystem coverage.
Syft review

Questions people ask

Is PostHog or Syft better?
Neither clearly leads. PostHog starts at Free and Syft at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, PostHog or Syft?
PostHog starts at Free and Syft at Free.
Does PostHog or Syft run on more platforms?
PostHog runs on Web, Ios, Android, Api. Syft runs on macOS, Linux, Windows, Docker.
Can I use PostHog for free?
Both have a free tier, so you can try either at no cost before committing.
What is PostHog best used for?
PostHog is most often used for product analytics, feature experimentation, user behavior tracking, a/b testing. Of those, product analytics and feature experimentation are not what Syft is typically brought in for.
What can PostHog do that Syft cannot?
PostHog covers Product analytics, Session recording, Feature flags, A/B testing. Syft covers Multi-format output, Broad ecosystem coverage, Binary classifiers, In-toto attestations.

Answered from the vendors’ own pages

PostHog: What does PostHog's free tier include per month?

PostHog free tier includes: 1M analytics events, 5K session replays, 1M feature flag requests, 100K error tracking exceptions, 1,500 survey responses, 1M data warehouse rows, 10K data pipeline events, 100K AI observability events, 500 PostHog AI credits, 10K workflow messages, and 10GB log ingestion. Source: https://posthog.com/pricing

Source
Syft: Does Syft find vulnerabilities?

No. It produces an inventory. Grype, from the same company, matches that inventory against vulnerability feeds. They are separate tools and the distinction is frequently lost.

PostHog: How much data retention does PostHog provide on paid plans?

PostHog free tier provides 1-year data retention. Pay-as-you-go plans offer 7-year data retention across all projects, enabling longer historical analysis. Source: https://posthog.com/pricing

Source
Syft: Does anything in the Anchore stack do reachability analysis?

No. Neither Syft, Grype nor the commercial Anchore platform performs call graph or reachability analysis, so none of them tells you whether a vulnerable code path is actually invoked.

PostHog: What percentage of PostHog users stay on the free tier?

PostHog states that 97% of companies use PostHog for free, indicating extensive free tier adoption. However, specific per-unit pricing rates for overages on paid plans are not published. Source: https://posthog.com/pricing

Source
Syft: Is it a CNCF or OpenSSF project?

No. It is single-vendor open source owned by Anchore, with no foundation governance. That is a different licence risk profile from Sigstore.

PostHog: When does PostHog provide priority support on paid plans?

PostHog provides email or Slack support for accounts exceeding $2,000/month on pay-as-you-go plans. Specific response times and support SLAs are not detailed on their pricing page. Source: https://posthog.com/pricing

Source
Syft: What does Anchore Enterprise cost?

Not published. The pricing page is contact-sales only, with named but unpriced commercial and federal tiers.

Syft: How do I know my SBOM is complete?

You largely cannot, which is the honest answer. Silent partial parsing is a known open defect, so a bill of materials used for compliance should be spot-checked against a known dependency list.

Share

Related pages

More on PostHog

More on Syft

Keep looking

Other head to heads