Changelog

What changed in each Brekfuz release

A complete record of what shipped in each version, from initial release to the current build.

v1.3 Latest

Leave coverage forecast and Linear integration

This release adds proactive leave coverage planning alongside a new Linear integration for engineering teams that use Linear instead of Jira.

  • Leave coverage forecast: six-week advance warning when an approved leave period opens a knowledge gap in any active project domain
  • Suggested coverage assignments: the graph now recommends the team member with the strongest adjacent knowledge to cover each exposed domain during leave
  • Linear integration: read-only access to issue assignment and project cycle data for engineering teams using Linear
  • Coverage assignment confirmation flow: managers can confirm or adjust suggested assignments directly in the Brekfuz dashboard
  • Improved signal weighting for Jira: ticket age decay now reduces the weight of assignments older than 90 days
v1.2

Offboarding plan generation and Notion support

Structured offboarding plan generation is now available for all Intelligence and Enterprise customers, along with Notion integration as a second documentation source option.

  • Offboarding plan generation: triggered when a departure is marked in the HR integration; generates a priority-ranked transfer list within 24 hours
  • Notion integration: read-only access to page authorship and workspace activity data; replaces or supplements Confluence for teams using Notion as their primary knowledge base
  • Transfer progress tracking: signal-based verification of whether a designated recipient's activity in a transferred domain has changed since the transfer session
  • Offboarding manager dashboard: live tracker showing transfer status, days remaining to departure date, and domains at risk of incomplete transfer
  • API rate limit increase: Intelligence tier API rate limit raised from 2,000 to 5,000 events per hour
v1.1

GitHub integration and dependency risk scoring

Dependency risk scoring is now available as a dedicated feature, and GitHub is now supported as a signal source for engineering teams.

  • GitHub integration: read-only access to commit authorship by file path and PR review participation patterns
  • Dependency risk score: each knowledge domain now has a risk score based on ownership concentration, criticality weight, and coverage depth
  • Risk dashboard: organization-wide view of knowledge domains sorted by risk score, filterable by team and project
  • Onboarding gap report: for a new team member, shows the 10 highest-priority domains to engage with based on their role profile
  • Domain ownership history: timeline view of how ownership signals have shifted over the past 6 months for any domain
v1.0 General availability

General availability release

Brekfuz 1.0 is the first generally available release, opening the product to Intelligence tier customers beyond the early-access cohort.

  • Slack integration: channel membership and message frequency patterns as signal inputs for the knowledge graph
  • Confluence integration: page authorship and edit history as documentation ownership signals
  • Jira integration: ticket assignment history and project membership as task ownership signals
  • Knowledge graph visualization: interactive graph explorer showing knowledge domains, team member ownership, and ownership concentration
  • Single-person dependency alerts: automated detection when a domain's ownership is concentrated in a single team member above a configurable threshold
  • Export: knowledge graph data export as JSON and CSV for Intelligence and Enterprise customers
v0.9 Early access

Early access with Slack and Jira signals

The first early-access release shipped to our pilot cohort with Slack and Jira as the initial signal sources.

  • Slack signal ingestion: channel membership and message count by channel (no content) as activity signals
  • Jira signal ingestion: ticket assignment and project membership as task ownership signals
  • Knowledge domain creation: automatic domain discovery from Jira project taxonomy
  • Team member profiles: individual knowledge ownership profiles showing domain activity distribution
  • Beta dashboard: early access to the knowledge graph explorer, read-only for this cohort
v0.7 Internal

Internal prototype: knowledge graph data model

Internal prototype validating the core knowledge graph data model and signal ingestion pipeline with synthetic data.

  • Core knowledge graph data model: domain, person, and ownership-edge schema
  • Signal ingestion pipeline: tested with synthetic Slack and Jira exports
  • Graph database backend: evaluated and selected graph DB for production use
  • Signal weight algorithm v1: initial ownership concentration scoring based on activity frequency and recency
v0.5 Internal

First internal build: signal collection feasibility

The initial internal build validating the feasibility of the read-only metadata signal collection approach across Slack and Jira using test workspace credentials.

  • Proof of concept: read-only Slack OAuth integration reading channel activity metadata without message content
  • Proof of concept: read-only Jira integration reading ticket assignment history
  • Initial signal storage schema: time-series signal storage for team member activity by domain proxy
  • Internal team validation: tested on the founding team's own Slack workspace and Jira project

What ships next

Shape the roadmap by booking a demo

We build from conversations with the teams using Brekfuz. If you have a capability you need that you do not see here, tell us in the demo call.

Book a demo