Skip to content

Commit a5caa9e

Browse files
docs: rename teams to AI Gateway and AI Observability (#17344)
* docs: rename teams to AI Gateway and AI Observability Update stale "LLM Gateway" and "LLM Analytics" references to the current team names. Scoped to display text only; SEO-sensitive positioning page, vale allowlist, generated link data, and published blogs left for marketing to decide. Generated-By: PostHog Code Task-Id: 04e898f9-72fd-48f6-876d-39b206eda46c * docs: use spaced en-dash on AI Gateway team page Match PostHog prose style flagged by Vale on the touched line. Generated-By: PostHog Code Task-Id: 04e898f9-72fd-48f6-876d-39b206eda46c
1 parent b2535ec commit a5caa9e

6 files changed

Lines changed: 10 additions & 10 deletions

File tree

contents/handbook/cs-and-onboarding/engaging-unengaged-customers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Watch customer activity for signs they're exploring a product they haven't adopt
6666

6767
**Suggested wording:**
6868

69-
> Hey @[contact], saw you checking out LLM analytics and wanted to share a few things. It occurred to me that our LLM observability suite might be really helpful for your team.
69+
> Hey @[contact], saw you checking out AI observability and wanted to share a few things. It occurred to me that our LLM observability suite might be really helpful for your team.
7070
>
7171
> Not only do you get evals/traces/generations to track model performance, token usage, etc, you can then also connect those things back to PostHog session/user data. Which means you can actually easily run A/B and multivariate tests on things like prompts, models, and so on, while ALSO seeing how the LLM performance/quality have an impact on conversion and funnel.
7272
>

contents/handbook/docs-and-wizard/developing-the-wizard.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,9 +77,9 @@ Review the logs at `/tmp/posthog-wizard.log`. This log can be quite verbose, so
7777

7878
Potential points of upstream failure:
7979

80-
- Without OAuth from PostHog, the wizard cannot access the LLM gateway. This will prevent all wizard runs. But if OAuth is not possible, we've probably got bigger problems than just the wizard itself.
80+
- Without OAuth from PostHog, the wizard cannot access the AI gateway. This will prevent all wizard runs. But if OAuth is not possible, we've probably got bigger problems than just the wizard itself.
8181
- If GitHub's release artifacts are not available, the wizard will be guessing blindly at how to integrate PostHog, producing incorrect and incomplete integrations.
82-
- If wizard's agent harness cannot connect to the LLM gateway, the wizard run will fail.
82+
- If wizard's agent harness cannot connect to the AI gateway, the wizard run will fail.
8383
- If Anthropic's API is down, the wizard run will fail.
8484

8585
The wizard has the above upstream dependencies. It is also a bundle of client code, subject to various bugs and distribution mishaps. If upstream services are healthy but the wizard is still failing, it's likely a bug in the wizard itself.
@@ -92,6 +92,6 @@ Remember to do a quick sanity check after release with `npm @posthog/wizard@late
9292

9393
### Declare an incident
9494

95-
If an upstream dependent PostHog service like OAuth or the LLM gateway is down, an incident may already in progress. Check the #incidents channel for any related alerts. If not, [declare an incident](/handbook/engineering/operations/incidents), describing the highest-level issue that's causing the wizard to fail.
95+
If an upstream dependent PostHog service like OAuth or the AI gateway is down, an incident may already in progress. Check the #incidents channel for any related alerts. If not, [declare an incident](/handbook/engineering/operations/incidents), describing the highest-level issue that's causing the wizard to fail.
9696

9797
If the wizard client code itself is failing, that's an incident as well.

contents/handbook/marketing/ownership.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ We generally only have product marketers on teams that _already_ have a product
2323
| *PostHog Code* | Annika | Cleo | James H |
2424
| *Replay* | Cory S | Sara* | Paul D'A |
2525
| *Surveys* | Cory S | | Surveys |
26-
| *LLM Analytics* | Marco (new) | To be hired | James H |
27-
| *LLM Gateway* | Marco (new) | | Ben W |
26+
| *AI Observability* | Marco (new) | To be hired | James H |
27+
| *AI Gateway* | Marco (new) | | Ben W |
2828
| *Product Analytics* | Mike W | To be hired | Paul D'A |
2929
| *Web Analytics* | Mike W | To be hired | Paul D'A |
3030
| *Conversations* | | Too early | James H |

contents/handbook/which-products.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Products we know will work well if we ship them:
1616
- Think error tracking or feature flags. The [persona doesn't change](/handbook/who-we-build-for#our-current-persona) as the company gets bigger.
1717
- Especially true if it works for a 2 person startup, because that means we get in first
1818
- Products that are in extremely fast growing markets
19-
- Think LLM Analytics, MCP
19+
- Think AI Observability, MCP
2020
- Products that are very easy to integrate for our existing customers.
2121
- For example, users can enable the product in PostHog without needing to make a code change, or products that built on top of data that people are already collecting in PostHog
2222
- Products that _you_ are excited to build.

contents/teams/ai-gateway/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: LLM Gateway
2+
title: AI Gateway
33
sidebar: Handbook
44
showTitle: true
55
hideAnchor: false
66
template: team
77
---
88

9-
The LLM gateway is PostHog's internal routing layer for calling LLM providers. It gives PostHog's AI features a single endpoint to call, with shared handling for things like provider routing, caching, fallbacks, and cost attribution. The team owns the gateway service, its provider integrations, the [AI Observability Playground](/docs/ai-observability/playground), and the seams where the gateway connects into the rest of PostHog particularly <SmallTeam slug="ai-observability" />.
9+
The AI gateway is PostHog's internal routing layer for calling LLM providers. It gives PostHog's AI features a single endpoint to call, with shared handling for things like provider routing, caching, fallbacks, and cost attribution. The team owns the gateway service, its provider integrations, the [AI Observability Playground](/docs/ai-observability/playground), and the seams where the gateway connects into the rest of PostHog particularly <SmallTeam slug="ai-observability" />.
1010

1111
## Working with other teams
1212

src/pages/startups/[...slug].tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ export default function Startups(): JSX.Element {
147147
<p className="m-0">
148148
PostHog for Startups helps early-stage teams and founders build better
149149
products, faster. Get over $50,000 in credits to use across any PostHog
150-
features, including LLM analytics.
150+
features, including AI observability.
151151
</p>
152152
),
153153
},

0 commit comments

Comments
 (0)