Reported, and not established
Two customers have already left. That's the detail that changes the risk.
Forbes reports that a cyberattack on Fireworks exposed customer data and AI models, and that the fallout is widening. Two customers told Forbes they had moved their business off the company's systems. One described a series of 'very bad hacks' and poor communication.
Sort it. Reported by Forbes: an attack, exposure of customer data and models, two departures. Reported by one customer: more than one incident, and poor communication. Not established, from the headline and summary the Journal has read: how the attacker got in, which customers and which data, whether model weights or only hosted endpoints were touched, and what Fireworks itself has said. This desk hasn't seen a company statement and won't guess at one.
That's where the cases split. A customer who knows what was exposed can rotate keys, notify the right people and stay. A customer who can't find out has one control left, and it is the exit. If you host fine-tuned models or prompts with any inference provider, treat them as you would a database: they hold your data in a different shape.
Questions for whoever runs it
Which API keys and stored datasets do we have with each model host, and when were the keys last rotated? If a provider told us tonight that our tenant was exposed, who here receives that message? How long would it take us to serve the same model from somewhere else?
