{
  "ids": [
    "matomo",
    "posthog"
  ],
  "title": "Matomo vs PostHog: web reports and product workflows",
  "deck": "Separate website reporting, product investigation and the responsibilities of self-hosting.",
  "answerHeading": "Is the missing capability website reporting or product operations?",
  "answer": "Evaluate Matomo for a website analytics programme with an explicit Cloud or On-Premise hosting choice. Evaluate PostHog Cloud when product analysis belongs alongside replay, flags and experiments in an engineering workflow. Matomo Community is free self-managed software; PostHog Cloud has recurring product allowances. These are different kinds of free access, with different operational costs.",
  "rows": [
    [
      "Starting brief",
      "Website acquisition, engagement and goals",
      "Product behaviour and developer workflows"
    ],
    [
      "Hosting choice",
      "Managed Cloud or customer-run On-Premise",
      "Managed Cloud; hobby self-hosting assessed separately"
    ],
    [
      "Free access",
      "On-Premise Community software",
      "Recurring Cloud allowances by product"
    ],
    [
      "Advanced website tools",
      "Paid On-Premise plugins or Cloud scope",
      "Select required products and their meters"
    ],
    [
      "Rollout workflow",
      "Analytics programme and connected tools",
      "Feature flags and experiments alongside analytics"
    ],
    [
      "Operating responsibility",
      "Self-managed stack or Cloud responsibility split",
      "Cloud administration or separately assessed hobby deployment"
    ],
    [
      "Cost model",
      "Cloud traffic tiers or hosting plus plugins",
      "Separate product consumption and optional capabilities"
    ]
  ],
  "scenarios": [
    {
      "name": "Content website",
      "question": "Can the editor understand landing pages and meaningful goals?",
      "left": "Define the acquisition and goal reports required.",
      "right": "Check whether web analytics meets those same reporting needs.",
      "note": "Hypothetical brief: publish a short weekly decision report rather than collecting every available signal."
    },
    {
      "name": "SaaS release",
      "question": "Can an engineer connect a product question to a controlled rollout?",
      "left": "Identify the additional rollout tools and handoffs required.",
      "right": "Evaluate analytics, flags and experiments as a scoped workflow.",
      "note": "Keep the success event and release identifiers consistent across the proposed process."
    },
    {
      "name": "Deployment control",
      "question": "Who will operate the full analytics stack?",
      "left": "Choose between Cloud and an owned On-Premise deployment.",
      "right": "Treat the hobby self-hosting option as its own operational assessment.",
      "note": "Do not infer production support or feature parity from the existence of a repository."
    },
    {
      "name": "Budget review",
      "question": "Which unit grows with the expected workload?",
      "left": "Forecast Cloud hits or self-managed infrastructure and plugin costs.",
      "right": "Forecast analytics events, replay and flag requests separately.",
      "note": "A hypothetical budget should include a launch spike and the person maintaining the setup."
    }
  ],
  "sections": [
    {
      "id": "hosting-accountability",
      "title": "Make hosting accountability explicit",
      "navLabel": "Hosting choice",
      "paragraphs": [
        "For a self-managed choice, assign upgrades, capacity, backups, access controls and recovery. Ask how a failed analytics service will be detected without relying entirely on the same service. Free software still needs an operating plan.",
        "For a managed choice, define the region, retention, exports and support expectations. PostHog’s hobby deployment and Matomo’s On-Premise product should not be treated as interchangeable support offers merely because both can involve customer infrastructure."
      ]
    },
    {
      "id": "reporting-purpose",
      "title": "Choose a small reporting purpose first",
      "navLabel": "Tool scope",
      "paragraphs": [
        "A marketing website and a logged-in product can share a domain while needing different evidence. The editor may need useful landing-page reports; an engineer may need the event sequence around a new feature. Name the owner and expected decision for each view.",
        "Avoid deploying overlapping replay and event capture simply because the features are available. A smaller set of understood signals is easier to maintain, budget and review than several conflicting definitions of the same action."
      ]
    }
  ],
  "faqs": [
    {
      "question": "Is Matomo Cloud free?",
      "answer": "Matomo Cloud is paid and offers a trial. The permanent free option is Matomo On-Premise Community on your own infrastructure."
    },
    {
      "question": "Does Matomo Community include every premium plugin?",
      "answer": "No. Advanced On-Premise functionality can require paid plugins or bundles. Confirm the exact feature and entitlement."
    },
    {
      "question": "Does PostHog Cloud have recurring free access?",
      "answer": "Yes. It publishes separate monthly allowances, including 1 million analytics events and 5,000 replay recordings. Other products have their own units."
    },
    {
      "question": "Is PostHog hobby self-hosting equivalent to Cloud?",
      "answer": "Do not assume that. Assess current deployment guidance, maintenance, support and product availability separately from the managed service."
    }
  ],
  "id": "matomo-vs-posthog",
  "heading": "Matomo vs PostHog",
  "kicker": "Analytics comparison",
  "description": "Matomo vs PostHog: web reports and product workflows. Compare free access, implementation scope, operating costs and practical buying requirements.",
  "checkedAt": "2026-10-15",
  "researchTag": "Buying requirements comparison",
  "researchLimit": "The buying briefs and acceptance checks are hypothetical evaluation proposals. They are not hands-on tests, performance measurements or vendor scores.",
  "datasetDescription": "Seven practical differences, four hypothetical buying briefs and a four-row acceptance checklist.",
  "type": "workflow-buying",
  "exampleTable": {
    "caption": "Hypothetical buying checklist; the conditions below are proposed acceptance checks, not measured results.",
    "headers": [
      "Requirement",
      "Evidence to collect",
      "Acceptance condition"
    ],
    "rows": [
      [
        "Measurement scope",
        "An agreed journey, events and relevant context",
        "Both evaluations answer the same defined question"
      ],
      [
        "Collection quality",
        "A synthetic journey reconciled with expected records",
        "Counts and missing context can be explained"
      ],
      [
        "Commercial scope",
        "Written plan limits and operating responsibilities",
        "Every required capability has an owner and a budget"
      ],
      [
        "Review process",
        "A short report and follow-up action",
        "The intended team can repeat the investigation"
      ]
    ]
  },
  "sources": [
    {
      "url": "https://matomo.org/pricing/",
      "facts": "Matomo: current product scope, access boundaries and operating requirements."
    },
    {
      "url": "https://matomo.org/feature-overview/",
      "facts": "Matomo: current product scope, access boundaries and operating requirements."
    },
    {
      "url": "https://posthog.com/pricing",
      "facts": "PostHog: current product scope, access boundaries and operating requirements."
    },
    {
      "url": "https://posthog.com/docs",
      "facts": "PostHog: current product scope, access boundaries and operating requirements."
    },
    {
      "url": "https://posthog.com/docs/self-host",
      "facts": "PostHog: current product scope, access boundaries and operating requirements."
    }
  ],
  "relatedLinks": [
    {
      "path": "/guides/analytics-measurement-plan/",
      "title": "Write an analytics measurement plan"
    },
    {
      "path": "/guides/software-total-cost/",
      "title": "Estimate the complete software cost"
    },
    {
      "path": "/guides/software-buying-checklist/",
      "title": "Prepare a repeatable software evaluation"
    },
    {
      "path": "/categories/web-product-analytics/",
      "title": "Browse web and product analytics"
    }
  ]
}