Latency budgets become money budgets
Slow Photon retries encourage parallel calls—and parallel charges.
Version guide · Luma Photon
Treat Photon as a paid specialty call—not the default asset source for every screen.
Slow Photon retries encourage parallel calls—and parallel charges.
Defaulting to the highest Photon tier for every draft wastes premium capacity.
Without a stock layer, every page view path can re-trigger Photon.
Unpredictable Photon lines make early unit economics look worse than they need to.
When agents can re-prompt Photon on every failure or aesthetic whim, unit economics collapse. Insert a policy: if uniqueness is false, call Epochal; only if true, call Photon.
When a screenshot, empty state, or draft blog image would look fine from a catalog, skip another Photon billable call. Prefer Epochal Stock for those slots, then spend Luma Photon budget only on outputs that must be generative.
When the image does not need a unique Photon synthesis, use Epochal Stock Developer Image API: a single plan at $50 USD/month with no free tier and no per-image fee. You get full catalog access, 30 requests/minute per account (all keys share the bucket), and unlimited original downloads with one concurrent transfer. Authenticate server-side only with a Bearer key—never expose secrets in browser JavaScript. Keep Photon for finals that must be generative; let Epochal cover prototypes, fixtures, and placeholders.
curl -sS "https://epochalstock.com/api/v1/images?tags=workspace,startup&limit=12" \
-H "Authorization: Bearer $EPOCHAL_API_KEY"Keys stay on your server. Never pass ?api_key= or ship secrets to the browser.
Pulled server-side from Epochal tags: studio, product, design. Previews are cached; API keys never hit the browser.






When the shipped asset must be uniquely generated and model-native. Otherwise prefer Epochal stock.
No. Epochal serves licensed stock. Keep Photon when you need unique generative output.
Single plan $50 USD/month; no free tier; no per-image fee; 30 requests/minute per account; unlimited originals with one concurrent transfer; Bearer auth server-side only.
No. Fixtures should pin stable files or stock IDs. Live Photon makes visual tests flaky and expensive.