We’re putting $5.5M behind research and development of smaller, specialized AI models for real-world deployment — Read our manifesto →
    All posts

    Pinterest Is Re-Prioritizing Open AI Models, but Not for Every Workload

    How proprietary prototypes, adapted open models and Pinterest-native systems divide the work in a scaled visual AI portfolio.

    Conscious Engines

    How proprietary prototypes, adapted open models and Pinterest-native systems divide the work in a scaled visual AI portfolio.

    The reported result

    Pinterest says it is shifting more AI investment toward fine-tuned open-source models, particularly for visual and multimodal tasks. In a December 2025 Pinterest Engineering report, the company reported similar performance at less than 10 percent of the cost of leading proprietary models for relevant workloads.

    Pinterest also reported that PinCLIP, an internally trained multimodal embedding system, outperformed state-of-the-art open embeddings by more than 30 percent on core retrieval tasks.

    Those are strong numbers, but the strategy is more interesting than the headline. Pinterest is not making a single open-versus-closed choice. It divides model sourcing by the source of differentiation.

    Reported Production Results

    <10%

    Cost of leading proprietary models

    Pinterest-reported cost for relevant adapted open-model workloads at similar performance.

    >30%

    PinCLIP retrieval outperformance

    Reported improvement over state-of-the-art open embeddings on core retrieval tasks.

    Hundreds of billions

    Graph nodes

    Scale of Pinterest's proprietary visual and behavioral graph.

    The three-part model portfolio

    Pinterest describes three broad model categories:

    CapabilityDefault sourcing logicReason
    User and recommendation modelsBuild internallyDeeply coupled with Pinterest's graph and product
    Visual encoders and generationInternal or adapted open modelsProprietary visual data creates differentiated quality
    General text and reasoningOpen and third-party modelsBroad pretraining is expensive and often commoditized

    Third-party platforms remain useful for coding, internal productivity and rapid prototyping. Once a product capability reaches scale, internally hosted or fine-tuned models can provide better economics, personalization and control.

    The company states the principle directly: “Compact, fit-for-purpose models can meaningfully out-perform general purpose LLMs on specific tasks.”

    Why Pinterest's data changes the model decision

    Pinterest is a visual discovery platform with a graph containing hundreds of billions of nodes. A general multimodal model can understand common images, but it does not naturally contain Pinterest's user representations, visual boards, search behavior and style relationships.

    An API can personalize through text context. Pinterest can go further by training or adapting models to consume internal embeddings and session signals directly. That can improve both quality and efficiency. Long visual contexts may contain tens or hundreds of Pins. Passing every detail through a proprietary multimodal API creates token and image-processing cost while losing some of the structure in Pinterest's own representations.

    This is the economic reason private data can justify a bespoke enterprise model. The model becomes valuable not because the company owns more parameters, but because it can use data and product signals that a general provider cannot optimize for.

    Pinterest Assistant is a router, not one giant brain

    Pinterest Assistant combines a core multimodal language model with native retrieval, recommendation and specialized generation tools. The core model interprets the request, plans and calls tools. Much of the differentiated work happens in Pinterest-native systems.

    This architecture avoids asking one model to reproduce the company's recommendation engine inside a prompt. It also lets teams improve individual tools without retraining every other component.

    The design mirrors enterprise AI model routing:

    1. A general model handles language, planning and tool selection.
    2. Specialized retrieval and recommendation models handle domain decisions.
    3. Internal data and embeddings stay close to the systems built for them.
    4. Proprietary providers remain available when they offer a real capability advantage.

    What the less-than-10-percent figure means

    Pinterest says self-hosted, fine-tuned open models provide about an order-of-magnitude inference-cost improvement in image-heavy conversations. It does not publish the model names, exact traffic mix, hardware utilization, fully loaded engineering cost or raw quality table behind the comparison.

    The result is therefore a company-reported metric for relevant visual and multimodal categories, not a claim about all Pinterest AI. It also does not show that self-hosting wins at low volume. Pinterest has the traffic and engineering scale to keep infrastructure productive.

    For an enterprise, the test should use:

    fully loaded cost per accepted multimodal outcome = model + image processing + infrastructure + engineering + review / accepted outcomes

    The evaluation should include retrieval relevance, personalization, brand safety, latency and severe errors, not only a generic multimodal benchmark.

    The enterprise lesson

    The right question is not whether to buy or build AI. It is where company-specific data creates enough value to justify adaptation and ownership.

    Use a proprietary model when broad capability and speed to launch matter. Adapt an open model when the task repeats, private signals improve quality and scale justifies the serving work. Build an internal model when the capability is central to the product and the training data is uniquely defensible.

    Pinterest belongs in the Frontier Model Downshift Index beside Dropbox's teacher-runtime design, Replit's routing system and the build-versus-buy framework. Each case rejects the idea that one sourcing choice should govern every task.

    Building a Production-Ready System

    Conscious Engines helps enterprises identify the workflows where private data, repeated volume and operating constraints make a bespoke model commercially rational. We can retain third-party frontier models for prototyping and hard cases, then build specialized models, retrieval tools and routing around the capability that creates durable advantage.

    The objective is a portfolio in which every model has a defined job, quality gate and cost budget.