Fireworks AI CEO Lin Qiao: Two Standard Modes for AI API Data Retention, Advocating Ephemeral Processing When Workflows Allow
Lin Qiao, co-founder and CEO of Fireworks AI, outlines two standard lifecycle designs for AI inference and training APIs: customer-managed upload-use-delete and ephemeral send-compute-return. She argues that the latter should be prioritized when workflows permit, as it eliminates human errors such as forgotten datasets or missed deletion calls.
In AI infrastructure, data retention is one of the most misunderstood terms. In a November 2026 post on X, Lin Qiao, co-founder and CEO of Fireworks AI, proposed a clear framework for thinking about this: AI inference and training APIs follow two standard design patterns, distinguished by who manages the data lifecycle and where.
The first pattern is customer-managed retention: upload, use, delete. Users create datasets or files, submit jobs, and then explicitly delete the data. The platform keeps the data stored and available until it receives a deletion instruction. Batch APIs are a typical example—OpenAI Batch, AWS Bedrock Batch, GCP Gemini Batch, and Fireworks Batch all follow this standard. The platform cannot know when the user no longer needs the data unless the user defines it; deletion is the user's responsibility.
The second pattern is ephemeral processing: send, compute, return. Users send data, the platform uses it during request processing, and returns the result without retaining the content afterward. Standard inference APIs and serverless training fall into this category. Applications own their conversation history, with no separate platform cleanup step required.
Lin Qiao used an intuitive analogy: saving a spreadsheet to a cloud drive versus passing numbers to a calculator. The former requires the service to keep the file for later use, while the latter only requires computing the answer and returning it immediately.
She advocates that ephemeral processing should be prioritized whenever workflows allow, not for performance or cost reasons, but to avoid human error. Ephemeral processing leaves no forgotten datasets and no missed deletion calls. Every retained copy of data adds something that must be protected and eventually deleted. If data never reaches disk, it cannot be taken from disk later.