Engwire runs on your machine. Engwire for teams is a separate hosted product, for when the rest of the company needs to know what shipped. It finds the few engineering changes worth communicating, explains what changed for the people who need to know, and sends the update to the right Slack channel. No firehose. No status report to write.
For B2B software teams with 8–40 engineers using GitHub + Slack. We're onboarding the first six teams by hand.
An example update, as it would arrive
#product-updates
EngwireApp09:41Shipped
Large CSV exports no longer time out
Accounts above 100,000 rows now stream their export instead of failing partway through, resolving a recurring problem for large customers.
Area: Billing·Production·4 related changes·Why this fired
EvidenceDeployment status: success · environment productionAvailability boundary: production deployment, billing-apiCommit range resolved from the previous production deployment4 pull requests in that range, all mapped to BillingDetected by rule, not by a model. Wording rendered from these facts.
Your tools record activity. Engwire for teams finds the news.
8 activities → 1 update worth reading
What the tools record
—pull request opened (draft)
—3 commits pushed
—check suite passed
—draft removed
—review requested
—label added: needs-qa
—pull request merged
—deployment status: success
Technically visible. Practically invisible — which is why the channel is muted.
What people need to know — an example
Shipped#product-updates
Large CSV exports no longer time out
Accounts above 100,000 rows now stream their export instead of failing partway through.
Area: Billing·Production·4 related changes·Why this fired
One update, after production availability is proven. Not when the branch merges.
You already have a workaround
“Our GitHub channel is muted.”
“Someone writes the weekly engineering update by hand.”
“Support keeps asking whether it shipped yet.”
They're the same problem: engineering systems record what happened, but nobody turns it into a useful update for the people outside the workflow. Engwire for teams automates the factual spine; humans keep the judgment.
Engwire for teams recognizes state changes; it does not forward activity. Detection is deterministic — explicit rules over source evidence, with no model in the path.
Ready for review
Fires once when a pull request actually becomes reviewable.
draft removed · opened non-draft · reopened non-draft
A channel notification, not a queue: it does not care who was asked. Engwire on your own machine is the one that acts on a review request naming you.
commits pushednot news
checks passednot news
label addednot news
draft removed
Ready for review
Never on commits · passing checks · reviewer assignments · labels · comments · merge
Shipped
Fires once when a delivery is proven available in production.
One deployment carrying twenty merged pull requests becomes one update — not twenty.
Collapsing them is what runs today. Naming which twenty — resolving the commit range and the area each change belongs to — is the milestone in progress, and it is the part the examples on this page are showing you.
based on the availability boundary configured for that scope
mergednot news
green buildnot news
staging deploynot news
production deployment succeeded
Shipped
The same event, written for the room it arrives in.
Same evidence. Different audience. Both examples.
Engineering
Shipped#eng-build
Streaming export path is live in production
Export requests above the row threshold now stream from the worker instead of buffering the full result set.
Readers don't need an Engwire account. The news arrives in Slack.
A model may explain. It never decides.
01 — Evidence
Source facts are retained and normalized. Duplicates and out-of-order delivery resolve safely.
02 — Detection
Explicit deterministic rules decide whether a meaningful event occurred. No model makes this decision.
03 — Routing
You state intent: shipped changes from these repositories go to #support-heads-up, written for that room rather than for engineers. Generated text cannot decide destinations.
04 — Wording
Today, deterministic copy built from the evidence above — no model in the path at all. Enrichment is the next milestone: a model explaining those same facts at the level each audience needs, with an unsupported claim omitted rather than softened.
Every update keeps its provenance, so you can see why it fired and what produced its wording. That the deterministic path is the one running today is also what makes the guarantee cheap to keep: when enrichment ships, a model failure, a rejected draft or a workspace opt-out falls back to exactly the message you would get now.
Transparency, not surveillance
Visibility without scoring people.
Making outcomes visible must never become scoring people. This is a product decision, not a missing feature.
noDORA scorecards or delivery rankings
noper-person commit, PR, or line counts
novelocity charts or team leaderboards
noasking engineers what they did yesterday
Six design partners, then we open it up
Run Engwire for teams on your real engineering workflow, with us.
We'll connect GitHub and Slack with you, watch the first weeks of real updates, and tune anything that arrives as noise.
02Shipping often enough that there is real news each week
03People outside engineering need context but do not live in GitHub
04Willing to tell us when an update was noise — that feedback is the point
A short email, then a shared setup call.
Before you authorize anything
The permissions you are shown are read from GitHub as you are about to grant them, not a list written down here that could already be out of date.
Each one Engwire for teams recognises says what it is for. Repository contents, for instance, is asked for so a shipped update can name the changes between two deployments — and is never written.
Each one discloses what the access permits, not what Engwire for teams happens to use. Deployments are named in full rather than narrowed to the successful ones it acts on.
Disconnecting revokes the grant and stops the access. What was already recorded stays: the events and deliveries in your history are built on it, and removing it would take them with it.
Something you can have today
This one is pre-launch. Engwire itself is not: it is open source, installs in one line, and reviews the pull requests that ask for you — on your own machine, with no account to make.