🇯🇵 Langfuse Cloud Japan is live →
HandbookProduct Ops
HandbookProduct EngineeringHow we workProduct Ops

Product Ops

We maintain an increasingly large product surface area with a small team. Processes matter in order to fix important bugs fast, and ship highly requested improvements for customers.

Overview

For product engineering, we use:

  • Linear for internal ticketing and collaboration via comments / RFCs
  • Pylon for managing support across all channels (in-app, GitHub Discussions Support, Shared Slack Channels, Shared MS Teams Channels, Shared Email inboxes)
  • GitHub
    • Issues for bug reports and near term improvements -> use via Linear (no separate inbox)
    • Discussions for feature requests -> use via Pylon (no separate inbox)
    • PR Reviews -> use via Linear PRs (no separate inbox)

We do not use:

  • Our individual email inboxes

Workflow Integration

The following diagram shows how bug reports and feature requests are handled:

GitHub Private Support Pylon Linear Automatically added to triage via native integration. Respond/resolve/deduplicate from Linear Link to Linear issue via Customer Request. Create Linear issue if none exists yet. Close the loop when done. GitHub Issues (Bug Reports) Linear Issues GitHub Ideas Discussions Pylon Tickets GitHub Support Discussions Slack Channels MS Teams Channels Group Email Inboxes In-app Support Linear Customer Requests

Was this page helpful?