CI & fixtures · SDXL Lightning

CI and Fixtures: Keep SDXL Lightning Out of the Pipeline

CI should be deterministic. Live SDXL Lightning calls via Replicate, fal.ai in tests and Storybook make snapshots flaky and bills noisy—especially for neon street speed drafts where visual regression is the whole point.

Where image API costs go off the rails

You pay for uniqueness you do not ship

Most SDXL Lightning outputs never leave staging—yet still hit the invoice.

Storybook and docs should not generate

Component libraries need stable pictures, not live SDXL Lightning samples on every build.

Marketing drafts churn images too early

Copy changes five times; SDXL Lightning should not bill five hero generations for that.

Team keys multiply chaos

Shared SDXL Lightning keys without quotas turn weekend hacks into multi-seat burn.

Scenario: CI & fixtures with SDXL Lightning

A PR pipeline regenerates images through SDXL Lightning for visual tests, email previews, or README builds. Network blips retry jobs; each retry can bill again on Replicate, fal.ai. Snapshots never stabilize because the model is non-deterministic. Instead, download licensed fixtures once from Epochal, commit or cache them, and assert against fixed bytes. Keep SDXL Lightning experiments in a manual or nightly job with hard budgets—not on every push. Your teammates get green checks; finance gets a flat image line instead of a surprise inference spike.

The fix: Epochal Stock at $50 USD/month (no per-image fee)

Epochal Stock Developer Image API is a single plan at $50 USD/month: full catalog access, 30 requests/minute per account, and unlimited original downloads with one concurrent transfer. There is no per-image fee and no free tier in v1. Use it wherever the picture does not need a unique SDXL Lightning synthesis—prototypes, fixtures, placeholders—so generative spend stays reserved for finals. Authenticate server-side with a Bearer key only; never put keys in browser JavaScript.

  • Price: $50 USD/month — single plan
  • Per-image billing: none
  • Rate limit: 30 requests/minute per account
  • Downloads: unlimited originals, one concurrent transfer
  • Best for: tests, prototypes, and placeholders instead of another SDXL Lightning generation
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.

Get the Epochal developer API See pricing details

Stock examples for CI & fixtures

Pulled server-side from Epochal tags: server, technology, city. Previews are cached; API keys never hit the browser.

Energy Consultant With Thermal Imaging Camera in Neon-Lit Setting — stock example for CI & fixtures for SDXL Lightning
Energy Consultant With Thermal Imaging Camera in Neon-Lit Setting
Child Using Laptop at Home With Packed Bags and Flowers — stock example for CI & fixtures for SDXL Lightning
Child Using Laptop at Home With Packed Bags and Flowers
Sustainability Team at Workshop Repairing Electronics With Smiles — stock example for CI & fixtures for SDXL Lightning
Sustainability Team at Workshop Repairing Electronics With Smiles
Elderly Man Stands by Boats at Sunset With City Lights Behind Him — stock example for CI & fixtures for SDXL Lightning
Elderly Man Stands by Boats at Sunset With City Lights Behind Him
Elegant Interior Space With Bookshelves and Sunset View — stock example for CI & fixtures for SDXL Lightning
Elegant Interior Space With Bookshelves and Sunset View
Palatial Chef's Kitchen With Marble Waterfall and Evening Light — stock example for CI & fixtures for SDXL Lightning
Palatial Chef's Kitchen With Marble Waterfall and Evening Light

FAQ

Why is SDXL Lightning a bad fit for CI?

Generative outputs are non-deterministic and often metered. CI needs stable fixtures; SDXL Lightning is for intentional creative runs.

How many Epochal downloads can CI use?

Original downloads are unlimited serially with one concurrent transfer per account. Plan parallel jobs so they do not fight the single-transfer limit.

What is the request rate limit?

30 requests/minute per account across all keys. Batch metadata where possible; do not fan out one key per micro-job without backoff.

Prototyping CI & fixtures Content placeholders Model hub

SDXL Lightning version guides

4-step 8-step