Stable Diffusion Integration: Custom Image Generation Pipeline

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
Stable Diffusion Integration: Custom Image Generation Pipeline
Medium
~3-5 days
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1347
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1247
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    948
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1183
  • image_logo-advance_0.webp
    B2B Advance company logo design
    642
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    921

Clients often complain that Midjourney offers no control over object poses, DALL·E becomes expensive at 5000 queries per day, and the license for generated images remains unclear. An open-source model like Stable Diffusion solves these problems: you get a self-hosted system with fine-tuning capabilities tailored to your business. Below is how we do it in practice and what a typical project includes.

What Problems Does Self-Hosted Stable Diffusion Solve?

We integrate ready-made LoRA models for specific art styles (anime, photorealism, 3D render) or custom fine-tuning on your dataset. We attach ControlNet for precise object positioning, and inpainting for local editing. For example, for an e‑commerce client we trained a LoRA on 500 product photos — the result: unified background generation in 2 seconds on an RTX 4090.

At 1000+ generations per day, cloud API costs become significant. For a client processing 5,000 images/day, switching to self-hosted SDXL saved $2,400/month on API costs. A self-hosted solution on an RTX 4090 pays for itself in 3–4 months, especially if you use quantized models (INT8) to reduce VRAM. The savings at scale can reach 60% compared to cloud services.

A task queue on Redis + Celery handles dozens of concurrent requests, while xFormers or Flash Attention 2 accelerate each generation by 20–30%.

How We Set Up the Generation Pipeline: Stack and Patterns

Our main tool is the diffusers library from Hugging Face. We use SDXL as the base model, attach a Refiner for final polish, and LoRA for styling. For comparison, SD 1.5 generates 512×512 with noticeably poorer detail, while SDXL produces 1024×1024 with quality close to Midjourney. This Stable Diffusion integration leverages latent diffusion and classifier-free guidance (CFG) to control output fidelity.

from diffusers import (
    StableDiffusionXLPipeline,
    StableDiffusionXLImg2ImgPipeline,
    StableDiffusionXLInpaintPipeline,
    DPMSolverMultistepScheduler
)
import torch
from PIL import Image
import io

class StableDiffusionService:
    def __init__(self, model_path: str = "stabilityai/stable-diffusion-xl-base-1.0"):
        self.pipe = StableDiffusionXLPipeline.from_pretrained(
            model_path,
            torch_dtype=torch.float16,
            use_safetensors=True,
            variant="fp16"
        )
        # Optimised sampler with Karras noise scheduling
        self.pipe.scheduler = DPMSolverMultistepScheduler.from_config(
            self.pipe.scheduler.config,
            use_karras_sigmas=True
        )
        self.pipe.to("cuda")

        # Optional VRAM optimizations
        self.pipe.enable_model_cpu_offload()
        self.pipe.enable_vae_tiling()

    def generate(
        self,
        prompt: str,
        negative_prompt: str = "nsfw, low quality, blurry, watermark, text",
        width: int = 1024,
        height: int = 1024,
        steps: int = 30,
        guidance_scale: float = 7.5,
        seed: int = None
    ) -> bytes:
        generator = torch.Generator("cuda").manual_seed(seed) if seed else None

        image = self.pipe(
            prompt=prompt,
            negative_prompt=negative_prompt,
            width=width,
            height=height,
            num_inference_steps=steps,
            guidance_scale=guidance_scale,
            generator=generator
        ).images[0]

        buf = io.BytesIO()
        image.save(buf, format="PNG")
        return buf.getvalue()

According to Hugging Face documentation, the DPMSolverMultistepScheduler with Karras sigmas provides faster convergence and quality.

SDXL Refiner for final polish:

from diffusers import StableDiffusionXLImg2ImgPipeline

refiner = StableDiffusionXLImg2ImgPipeline.from_pretrained(
    "stabilityai/stable-diffusion-xl-refiner-1.0",
    torch_dtype=torch.float16,
    use_safetensors=True,
    variant="fp16"
)
refiner.to("cuda")

def generate_with_refiner(prompt: str, steps: int = 40) -> bytes:
    # Base generates latent vector
    image = base_pipe(
        prompt=prompt,
        num_inference_steps=steps,
        denoising_end=0.8,
        output_type="latent"
    ).images

    # Refiner adds details
    image = refiner(
        prompt=prompt,
        num_inference_steps=steps,
        denoising_start=0.8,
        image=image
    ).images[0]

    buf = io.BytesIO()
    image.save(buf, format="PNG")
    return buf.getvalue()

Why LoRA Is Better Than Full Fine-Tuning?

Full fine-tuning requires 24+ GB VRAM even for SD 1.5 and takes hours. LoRA is a set of low-rank matrices (rank 16–64, 10–100 MB) that are attached on top of the pretrained model. We use peft to load multiple LoRAs simultaneously, combining styles with different weights. For example, 70% "anime" style + 30% "realistic textures".

# Load LoRA for a specific style
pipe.load_lora_weights("./loras/anime_style_v2.safetensors")
pipe.fuse_lora(lora_scale=0.8)

# Multiple LoRAs simultaneously
pipe.load_lora_weights("lora1.safetensors", adapter_name="style1")
pipe.load_lora_weights("lora2.safetensors", adapter_name="style2")
pipe.set_adapters(["style1", "style2"], adapter_weights=[0.7, 0.3])

Comparison of Approaches: LoRA vs Full Fine-Tuning

Parameter LoRA Full fine-tuning
VRAM requirements 8-12 GB 24+ GB
File size 10-100 MB 2-6 GB
Training time 1-2 hours 6-24 hours
Ability to combine styles Yes (up to 10 adapters) No
Quality on small dataset (100-500 images) Excellent Mediocre

How We Accelerate Generation?

We use fp16 computation, enable_vae_tiling to reduce peak VRAM, and enable_model_cpu_offload to partially offload to CPU. For batch processing we apply torch.compile to optimize the graph. In production we set up a request balancer on RabbitMQ with multiple GPU workers.

Performance by GPU

GPU VRAM Generation time 1024×1024 (30 steps)
RTX 3060 12 GB ~18 sec
RTX 3090 24 GB ~7 sec
RTX 4090 24 GB ~4 sec
A100 40G 40 GB ~3 sec

xFormers or Flash Attention 2 speed up by 20–30% with the same VRAM.

Example REST API wrapper:

from fastapi import FastAPI, BackgroundTasks
from pydantic import BaseModel
import uuid

app = FastAPI()
sd_service = StableDiffusionService()

class GenerateRequest(BaseModel):
    prompt: str
    negative_prompt: str = ""
    width: int = 1024
    height: int = 1024
    steps: int = 30
    seed: int = None

@app.post("/generate")
async def generate(req: GenerateRequest, background_tasks: BackgroundTasks):
    job_id = str(uuid.uuid4())
    background_tasks.add_task(
        process_generation, job_id, req.dict()
    )
    return {"job_id": job_id}

@app.get("/result/{job_id}")
async def get_result(job_id: str):
    status = redis_client.get(f"job:{job_id}")
    return json.loads(status) if status else {"status": "not_found"}

Process of Work

  1. Analysis. We gather requirements: number of generations, needed LoRA/ControlNet, GPU budget.
  2. Design. We choose the stack (SDXL + Refiner, queue), design the API (REST/WebSocket) and storage (S3/MinIO).
  3. Implementation. We write a FastAPI wrapper, configure LoRA and ControlNet, and set up monitoring (Prometheus + Grafana).
  4. Testing. We run 100+ generations with varying parameters, measure p99 latency and throughput.
  5. Deployment. On your server or cloud (AWS SageMaker / Google Vertex AI). We hand over documentation and auto-scaling scripts.

What's Included

  • Ready-made REST API wrapper with /generate and /result endpoints (async queue).
  • Support for LoRA, ControlNet, inpainting, img2img.
  • Deployment documentation for your infrastructure.
  • Training for your team (1-2 hours online).
  • Compatibility guarantee with your database (via generation log table).

Estimated Timeframes

API wrapper over SDXL — from 3 to 5 days. Self-hosted service with queue and storage — from 1 to 2 weeks. The cost is calculated individually based on integration complexity and the need for fine-tuning. Contact us — we'll find the best configuration for your budget.

Our Stable Diffusion integration provides efficient image generation using SDXL, LoRA, and ControlNet. We have 10+ years of experience in AI/ML and 40+ implemented image generation pipelines for e‑commerce, game dev, and advertising. We guarantee 24/7 stable operation and provide post-launch support. Get in touch to discuss the details.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Model Speed (1024×1024, A100) Quality (CLIP score) Controllability (ControlNet, IP-Adapter) VRAM (fp16)
Stable Diffusion 3.5 2.0–3.5 s 0.28–0.31 via ControlNet (allowed) 16–20 GB
FLUX.1 [schnell] 0.8–1.2 s 0.30–0.33 limited (no ControlNet) 12–14 GB (4‑step)
FLUX.1 [dev] 3–5 s (50 steps) 0.32–0.34 via IP-Adapter, ControlNet (adapter) 24+ GB
Midjourney (API) 5–10 s (queue) 0.31–0.33 prompt + style reference not required

Video Generation: Which Models Are Best?

Model Availability Duration Resolution Controllability
Sora (OpenAI) API (limited) up to 60 s 1080p prompt, image-to-video
Wan2.1 (Alibaba) open weights up to 81 frames 720p prompt, I2V, V2V
CogVideoX-5B open weights 6 s 720p prompt, I2V
Kling 1.6 API up to 30 s 1080p prompt, I2V
Mochi-1 open weights 5.4 s 480p prompt

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

  • Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
  • Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
  • Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
  • Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

  • Model (or API integration) with performance benchmarks (latency p99, throughput).
  • Pipeline documentation (prompt engineering guide, model card, dependency versions).
  • Integration with your backend (REST/gRPC, queues).
  • Configured monitoring (dashboards, alerts for quality drift).
  • Training workshop for the team (2–4 hours).
  • Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

  1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
  2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
  3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
  4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
  5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
  6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.
What We Verify at the Proof of Concept Stage
  • Alignment of expectations and actual generation quality (CLIP score, user study).
  • Inference speed at different batch sizes and GPU types.
  • Likelihood of toxic/incorrect generations — checking safety filters.
  • Scalability: will the model handle peak load.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.