All pages
Powered by GitBook
1 of 1

Loading...

Custom LLM Configuration

Introduction

This release introduces Custom LLM Configuration in Unifize.

Organizations can now explicitly configure how AI behaves across structured workflows, including prompt governance and model selection. This improves consistency, auditability, and execution control when using AI within checklist-based fields.

AI behavior is no longer dependent on implicit defaults. It is now governed through defined configuration at the organization level.

Release Capabilities

  1. Organization-Level System Prompt

    1. Admins can define a System Prompt for the organization.

    2. The System Prompt applies across AI-enabled fields.

    3. Changes are effective for new executions.

    4. Access is restricted to authorized administrators.

    1. Organizations can select which AI model is used for execution.

    2. Model selection is explicit and configurable.

    3. Switching models does not change governance or field-level controls.

    1. AI is triggered only within defined AI-powered checklist fields.

    2. Output is returned in structured format aligned to Unifize schemas.

    3. AI execution is scoped to the record and field context.

    1. AI behavior is governed by explicit configuration.

    2. Prompt precedence is enforced.

    3. No hidden or implicit AI instructions are applied.

Unifize supports integration with a broad ecosystem of AI model providers. This enables flexibility across cloud, enterprise, hosted, and private model deployments.

Supported providers include:

Enterprise & Foundation Model Providers

  • OpenAI

  • Anthropic

  • Azure OpenAI / Azure AI

  • AWS Bedrock

Additional Platforms & Model Hosts

  • DeepSeek

  • DeepInfra

  • Fireworks AI

  • ElevenLabs

This allows organizations to use approved vendors, regional deployments, or private model infrastructure without redesigning workflows.

AI remains assistive — user validation is required before applying outputs.

Configuration changes are traceable.

AWS Sagemaker

  • Google Vertex AI

  • Google Gemini (AI Studio)

  • Cohere

  • Mistral

  • Groq

  • NVIDIA NIM

  • IBM Watsonx

  • HuggingFace

  • Databricks

  • Snowflake

  • Together AI

  • Replicate

  • Perplexity

  • xAI

  • AssemblyAI

  • Meta Llama API

  • Ollama / Ollama Chat

  • OpenRouter

  • Vercel AI Gateway

  • SambaNova

  • Predibase

  • Novita AI

  • Nscale

  • Lambda AI

  • Cloudflare AI Workers

  • GitHub Models

  • GitHub Copilot

  • Watsonx Text

  • Voyage AI

  • Volcengine

  • Triton

  • VLLM / Hosted VLLM

  • AI execution behavior is harder to audit.

    Configuration-driven and traceable execution.

    Before

    After

    AI behavior relied on implicit or static configuration.

    AI behavior is governed by explicit organization-level configuration.

    Limited visibility into how prompts were applied.

    Clear System Prompt control and precedence.

    Model flexibility constrained.

    Explicit model selection supported.

    Model Selection

    Structured AI Execution

    Deterministic Configuration Behavior

    Supported Model Providers

    Before vs After