Stock library. Prompt box. Freelancer's invoice.No creative engine.

It's the visual-creation layer inside the Intempt platform. You feed it a product photo (or a text description), pick a recipe, and Blu — the built-in creative assistant — generates assets styled to your Brand Kit. Because it lives inside Intempt, those assets flow straight into Journeys, Experiments, and Analytics without a manual export step.

Packshots, lifestyle composites, flat lays, on-model try-ons, editorial spreads, cinemagraphs, vertical reels, product turntables, spokesperson avatars, email banners, SMS cards, push thumbnails, and landing-page sections. Each output type has its own recipe with baked-in art direction.

Neither. Recipes encode the lighting, composition, and styling decisions a creative director would make. You pick the recipe, upload your product, and Blu handles the generation. Brand Kit constrains the output to your visual identity automatically.

Sign up for a free Intempt account -- you get credits on signup, enough to run several recipes across different asset types. No payment info needed to start.

A clean product shot in PNG or JPG works best — ideally on a white or transparent background. Blu strips the background, relights the subject, and composites it into the scene defined by your recipe.

Midjourney and DALL-E are prompt boxes — you write, iterate, download, resize, repeat. Intempt recipes encode the art direction (angle, lighting, background, format) so the output is campaign-ready in one click. Your Brand Kit is applied automatically, and you push the result into a Journey or Experiment from the same screen — no round-trip through five tools.

No. Design is included in every Intempt plan. Free accounts come with starter credits. Paid tiers include a larger credit allowance that scales with your plan, plus the option to purchase additional credits when you need burst capacity.

It depends on the recipe. Credit cost is calculated dynamically based on the underlying model, resolution, and complexity of the operation. You see the estimated cost before confirming each generation -- nothing runs without your approval.

Yes -- cancel from Settings and your plan stays active until the end of the current billing period. No cancellation fees.

Team and Enterprise plans support multiple seats. Everyone on the team shares Brand Kit settings and the org credit pool, but each person's usage is tracked individually. Role-based permissions control who can generate, who can publish, and who can manage settings.

Images export as high-res PNG or JPG. Standard aspect ratios — 1:1, 4:3, 16:9, 9:16 — are built into each recipe. Channel-specific recipes auto-crop to the destination spec (email header, push icon, story frame) so you don't resize manually.

Image recipes typically finish in 5–15 seconds. Video recipes (cinemagraphs, reels, avatar clips) take 30–90 seconds depending on duration. You can queue several at once — they process in parallel.

Yes. Upload a batch of product photos, select the recipe, and Blu processes them concurrently. A 50-SKU product-page refresh that used to take a studio two weeks runs in a few minutes.

Recipes apply different art direction — lighting setups, camera angles, background environments, and prop styling all change. The product itself stays pixel-accurate; the creative treatment around it shifts to match the recipe's intent.

Yes. Motion recipes take any product still and add movement — a cinemagraph animates one element, a turntable spins the product, a reel recipe cuts a 9:16 vertical clip, and an avatar recipe pairs it with a generated spokesperson. You pick the motion type; Blu handles the render.

A workflow chains multiple recipes into an automated pipeline. Example: when a new SKU lands in your catalog, Blu auto-generates a packshot, two lifestyle variants, and an email banner — then drops all four into the product-launch Journey. Workflows run on triggers without anyone typing a prompt, which is how teams scale from one-off generation to always-on creative production.

Your color palette, typography, logos, tone-of-voice guidelines, and any visual rules you want enforced (minimum logo clear space, background restrictions, etc.). Once saved, every recipe Blu runs inherits those constraints — generated visuals use your palette, email copy matches your tone, and logos are placed according to your rules.

A recipe is a structured creative template with baked-in art direction — it defines the output type (e.g., packshot, editorial spread, email banner), the composition rules, the lighting setup, and the crop specs. You don't write a prompt; you pick the recipe and upload your product. Recipes are curated for specific outcomes: storefront hero, social ad, lifecycle email, and so on.

Yes. Custom workflows let you chain steps together and fire them on a trigger — for example, 'when a product is marked active, generate a hero, three social crops, and an email banner, then insert all five into the launch Journey.' Custom recipes let you define your own composition, lighting, and styling rules so Blu reproduces your house style exactly.

Yes. Scenes are reusable — apply the same marble-countertop setup or window-light editorial backdrop to any product in your catalog. This is how brands keep visual consistency across a collection: same scene, different products, every season.

You can export individual files or bulk-download an entire campaign as a ZIP at full resolution. But the bigger unlock is skipping the export entirely — push assets straight into a Journey, Experiment, or your site's content blocks from the Design Canvas.

Yes. Every asset Blu generates is yours to use commercially — storefronts, paid ads, email campaigns, social, print, packaging. There are no extra licensing fees and no attribution requirements.

No. Generated assets belong to your organization. Intempt does not claim IP over your output, and your visuals are never used to train models or exposed to other accounts.

Yes. Uploads, generated assets, and Brand Kit configurations are scoped to your organization. Data is encrypted at rest and in transit, never shared across accounts, and never fed into model training pipelines.

Delete individual assets or whole projects from Settings — asset deletion is immediate. Full account deletion purges all data within 30 days, consistent with GDPR and CCPA requirements.

Infrastructure runs on AWS across US and EU regions. Enterprise plans can pin data to a specific region. All storage is encrypted at rest (AES-256) and all traffic is encrypted in transit (TLS 1.3).