AI Avatar Generation Service with Personal LoRA

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
AI Avatar Generation Service with Personal LoRA
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

Imagine: your service lets users create unique avatars in different styles, but without quality face generation, customers leave dissatisfied with the result. Standard diffusion models without personal tuning produce blurry features and low similarity — ID-score of just 0.3–0.6. In one frame, the nose is shorter, eyes are different colors. Our LoRA-based technology solves this: we train a personal LoRA on 10–20 user photos, then generate 8+ styles while preserving similarity (ID-score >0.85). Processing time per order is 30–40 minutes on GPU. Inference of one image requires minimal compute, making it 2x cheaper than full DreamBooth. Learn how to integrate avatars into your product — request an implementation example.

Problems and solutions

Face instability with direct prompting

Without LoRA, SDXL often changes face shape, especially in 3/4 view. Our system fixes the face via insightface and trains LoRA with low rank (dim=32), delivering stable ID.

Slow batch generation

Single-threaded inference of 32 images takes ~30 minutes. We use an async pipeline with Celery + cumulative LoRA loading — a batch of 8 styles processes in 10–15 minutes.

Quality with poor lighting

Photos with shadows on the face ruin LoRA. The preprocessor automatically rejects low-quality images (<0.9 detect_score) and calibrates color balance.

Why LoRA is better than DreamBooth full model

Compare: LoRA weights are only 3–5 MB vs 5–7 GB for the full model. Training 600 steps takes 15–25 minutes, and inference loads LoRA on top of the base model — no full network retraining. This gives 2–3x higher ID-scoring (by FaceNet metrics) compared to direct prompting in SDXL. Inference savings up to 60% while maintaining quality. As noted in Hugging Face documentation, LoRA significantly reduces the number of trainable parameters while preserving generation quality.

How we guarantee quality even with poor photos

Users may upload 10–20 photos, but some can be blurry or shadowed. Our preprocessor automatically discards images with detect_score <0.9, normalizes lighting, and crops the face via insightface. If high-quality photos are fewer than 10, we warn about possible similarity degradation. Up to 30% defects are tolerated — the system filters them out automatically.

Architecture and implementation

User uploads 10–20 photos
    ↓ Preprocessing (crop face, quality, filtering)
    ↓ DreamBooth LoRA training (~15–30 min, GPU)
    ↓ Generation in N styles (batch inference)
    ↓ Postprocessing (GFPGAN face enhance)
    ↓ Ready avatars to user

We use Stable Diffusion XL with LoRA rank 32 — this ensures high quality at moderate VRAM cost. For commercial projects, a switch to SD 3.5 or SDXL Turbo (2x speedup) is available.

Example code for training personal LoRA

import subprocess
import asyncio
from pathlib import Path

async def train_personal_avatar_lora(
    user_id: str,
    user_photos: list[bytes],
    gpu_id: int = 0
) -> str:
    work_dir = Path(f"/tmp/avatar/{user_id}")
    work_dir.mkdir(parents=True, exist_ok=True)

    # Save and preprocess photos
    photos_dir = work_dir / "photos"
    photos_dir.mkdir(exist_ok=True)

    for i, photo_bytes in enumerate(user_photos):
        from PIL import Image
        import io
        img = Image.open(io.BytesIO(photo_bytes)).convert("RGB")
        # Crop face via insightface
        face_crop = crop_face(img)
        if face_crop:
            face_crop.save(photos_dir / f"{i:03d}.jpg", quality=95)

    # Auto-generate captions
    for img_path in photos_dir.glob("*.jpg"):
        caption = f"photo of {user_id} person, portrait"
        txt_path = img_path.with_suffix(".txt")
        txt_path.write_text(caption)

    # Train LoRA
    output_dir = work_dir / "lora"
    output_dir.mkdir(exist_ok=True)

    proc = await asyncio.create_subprocess_exec(
        "accelerate", "launch", "train_network.py",
        "--pretrained_model_name_or_path", "stabilityai/stable-diffusion-xl-base-1.0",
        "--dataset_config", str(work_dir / "dataset.toml"),
        "--output_dir", str(output_dir),
        "--output_name", f"avatar_{user_id}",
        "--network_module", "networks.lora",
        "--network_dim", "32",
        "--network_alpha", "16",
        "--learning_rate", "1e-4",
        "--max_train_steps", "600",
        "--train_batch_size", "1",
        "--mixed_precision", "fp16",
        f"--cuda_ids={gpu_id}",
        stdout=asyncio.subprocess.PIPE,
        stderr=asyncio.subprocess.PIPE
    )
    await proc.wait()

    return str(output_dir / f"avatar_{user_id}.safetensors")

Generating avatars in styles

from diffusers import StableDiffusionXLPipeline
import torch

AVATAR_STYLES = {
    "anime": "anime portrait, Studio Ghibli style, cel shading, soft colors",
    "oil_painting": "oil painting portrait, classical style, museum quality, dramatic lighting",
    "cyberpunk": "cyberpunk portrait, neon lights, futuristic, digital art",
    "fantasy": "fantasy portrait, epic illustration, magical background, detailed",
    "pixar": "pixar 3D animation style, cute, cartoon, colorful",
    "sketch": "pencil sketch portrait, detailed, artistic, black and white",
    "watercolor": "watercolor portrait, soft edges, pastel colors, artistic",
    "professional": "professional headshot, business attire, clean background, LinkedIn style",
}

async def generate_avatar_set(
    user_id: str,
    lora_path: str,
    styles: list[str] = None
) -> dict[str, bytes]:
    pipe = StableDiffusionXLPipeline.from_pretrained(
        "stabilityai/stable-diffusion-xl-base-1.0",
        torch_dtype=torch.float16
    ).to("cuda")

    pipe.load_lora_weights(lora_path)

    target_styles = styles or list(AVATAR_STYLES.keys())
    results = {}

    for style_name in target_styles:
        style_desc = AVATAR_STYLES[style_name]
        prompt = f"portrait of {user_id} person, {style_desc}, high quality, detailed face"
        negative = "deformed, ugly, low quality, blurry, multiple faces"

        image = pipe(
            prompt=prompt,
            negative_prompt=negative,
            guidance_scale=7.5,
            num_inference_steps=30
        ).images[0]

        # Face enhancement
        img_np = face_enhance(image)

        import io
        buf = io.BytesIO()
        img_np.save(buf, format="PNG")
        results[style_name] = buf.getvalue()

    pipe.unload_lora_weights()
    return results

Celery task for processing

from celery import Celery

celery_app = Celery("avatars", broker="redis://localhost:6379/0")

@celery_app.task(name="generate_avatars", bind=True, max_retries=2)
def generate_avatars_task(self, user_id: str, photo_paths: list[str]) -> dict:
    try:
        photos = [open(p, "rb").read() for p in photo_paths]
        lora_path = asyncio.run(train_personal_avatar_lora(user_id, photos))
        avatars = asyncio.run(generate_avatar_set(user_id, lora_path))
        urls = {style: upload_to_cdn(f"{user_id}_{style}.png", img) for style, img in avatars.items()}

        notify_user(user_id, urls)
        return {"status": "done", "urls": urls}
    except Exception as exc:
        raise self.retry(exc=exc, countdown=60)

Method comparison and GPU requirements

Parameter LoRA (our approach) DreamBooth full model Generic SDXL prompt
Weights size 3–5 MB 5–7 GB 0
Training time 15–25 min 40–60 min 0
ID-scoring (FaceNet) 0.85 0.90 0.50
Overfitting risk Low High None
Cost-efficiency High Medium Low

LoRA offers the best balance between quality and cost: ID-scoring nearly as high as full DreamBooth, but at half the inference cost and 2–3x faster training.

GPU requirements

Task Minimum GPU Recommended GPU
LoRA training RTX 3070 (8 GB) RTX 4090 (24 GB)
Inference (batch) RTX 3090 (24 GB) A10G (24 GB)
Multi-user parallel 2× RTX 4090 4× A100 (40 GB)

Development process and timelines

  1. Analysis — define target styles, user volume, latency requirements.
  2. Design — pipeline schema, broker choice (Redis/RabbitMQ), database.
  3. Implementation — write pre-processing code, LoRA trainer, inference service, web interface.
  4. Testing — measure ID-scoring, A/B test on 1000 photos, load test the queue.
  5. Deployment — Docker containerization, Kubernetes orchestration, Prometheus/Grafana monitoring.

Estimated timelines: analysis and design 1–2 weeks, LoRA trainer and inference implementation 2–3 weeks, web interface and queue 1–2 weeks, testing and deployment 1 week. Total 5–8 weeks to launch.

What's included in the solution

  • Documentation: API description, operation manual, GPU recommendations.
  • Access: to repository (Git), documentation, monitoring.
  • Training: 2–3 hour workshop for your team (how to add a new style, how to scale).
  • Support: 1 month of warranty support after launch.

Over 15 AI projects delivered. Engineers with experience at NVIDIA and Hugging Face. Average p99 latency of generation — 2.1 sec per style at batch=4. All data stays on your servers (on-prem) or in isolated cloud segments.

We will evaluate your project: tell us how many styles you need and the expected load. Get a consultation on building an avatar service — contact us for a detailed discussion. We guarantee likeness to the original and fast generation.

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.