Luma Dream Machine Pricing: Plans, Credits and API

Buying path

The default buying path for a Dream Machine buyer is the Dream Machine app route, not the developer API and not Luma Agents by default. Start with the free or trial-credit surface to test output quality, prompt behavior, and rough credit burn, then move to the smallest paid web plan that removes the real blocker.

The blocker is usually commercial use, watermark removal, or repeat monthly generation volume. Luma's support docs describe a Dream Machine web ladder with Lite, Plus, Unlimited, and Enterprise, while the current Luma pricing page shows a newer Plus, Pro, and Ultra ladder tied to Luma and Luma Agents. Treat those as separate buying contexts.

For buyers who work mostly on mobile, the iOS route needs its own check. Luma's Dream Machine docs and Apple's App Store listing show iOS in-app subscriptions that do not map perfectly to the web plan prices, so mobile buyers should verify renewal, cancellation, and credit behavior inside the App Store flow.

Upgrade triggers

The first upgrade trigger is commercial output. Free and Lite Dream Machine generations are documented as personal-use and watermarked, so paid commercial work should start only after the buyer has confirmed that the selected route grants the needed usage rights for the generation being created.

The second trigger is watermark and export quality. If a workflow depends on finished clips rather than internal concept review, the buyer should confirm that the chosen paid plan removes watermarks for the intended generation route and model before producing client or public campaign assets.

The third trigger is credit predictability. Video generation can consume credits unevenly by model, resolution, duration, HDR setting, or video-to-video workflow. A buyer should upgrade only after testing the repeated workflow enough to know whether Lite-level credits are enough or whether Plus, Unlimited, or a current Luma plan is the practical route.

API and team boundaries

Dream Machine API spend is a separate developer lane. Luma's credit-system docs state that Dream Machine subscription credits do not transfer to the API, and the API docs require a separate API key and billing surface. A creator subscription should not be budgeted as prepaid product integration spend.

Luma Agents also needs separation. The current Luma pricing page includes Luma Agents usage multipliers, while the Luma Agents API docs price image generation through pay-as-you-go and provisioned throughput. That is a different credit and workload model from older Dream Machine web and iOS plan docs.

Team and Enterprise routes solve different problems from individual credit volume. Use Team when shared workspaces, team organization, usage analytics, user spend limits, or SSO matter. Use Enterprise when procurement, training, custom fine-tuning, data commitments, or negotiated commercial terms matter more than picking a self-serve tier.

Final pricing check

Before paying, verify the exact plan surface you are using: Dream Machine web, Dream Machine iOS, current Luma app pricing, Dream Machine API, Luma Agents API, Team, or Enterprise. The plan names, credit balances, and rights language can differ across those official sources.

Also confirm model and workflow cost before committing. Ray3.14 text-to-video, Ray3.14 HDR, video-to-video, Kling, Veo, image generation, audio, reframe, and top-up credits can all consume credits differently. The safest buying decision is based on the route and model that will be used in production, not on the lowest visible monthly price alone.