Arize
How Arize migrated five years of ML community in a weekend
Featuring
“We had five years of community knowledge trapped in Slack. Now it lives at community.arize.com and our members can actually find it.”
Five years of community, zero days of downtime
When your ML observability community has been humming in Slack for five years, you do not just flip a switch and move it somewhere new. That is what made Arize's migration so impressive. David and his team took half a decade of support threads, product discussions, and community knowledge and brought it all into a dedicated home at community.arize.com. The import alone was 11MB of history, every conversation preserved. They set up Google Tag Manager from day one so they could actually measure what was working. And because their community deals with sensitive ML model data, they built guardrails for PII and API key detection before they even opened the doors. The whole thing was live in a weekend.
Impact
Imported 11MB of historical Slack data spanning 5 years of ML community discussions, preserving every support thread and knowledge share
Launched community.arize.com with custom domain, Google Tag Manager analytics, and dedicated support channels in under a week
Built automated PII and API key detection to keep sensitive model data out of public community threads
“We had five years of community knowledge trapped in Slack. Now it lives at community.arize.com and our members can actually find it.”
