> ## Documentation Index
> Fetch the complete documentation index at: https://docs.seekr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release notes – 2026

export const ReleaseTags = ({type, deployment}) => {
  const base = {
    display: "inline-block",
    padding: "2px 8px",
    borderRadius: "3px",
    fontSize: "11px",
    fontWeight: "600",
    marginRight: "4px"
  };
  const typeStyle = {
    feature: {
      backgroundColor: "#d0f4de",
      color: "#1b4332",
      border: "1px solid #52b788"
    },
    improvement: {
      backgroundColor: "#fef3c7",
      color: "#92400e",
      border: "1px solid #fcd34d"
    },
    "bug-fix": {
      backgroundColor: "#ffe5d9",
      color: "#6d0011",
      border: "1px solid #ff6b6b"
    }
  };
  const typeLabel = {
    feature: "Feature",
    improvement: "Improvement",
    "bug-fix": "Bug Fix"
  };
  const deployStyle = {
    "seekr-managed": {
      backgroundColor: "#c7f9cc",
      color: "#004b23",
      border: "1px solid #00cc88"
    },
    "self-managed": {
      backgroundColor: "#d3e4fd",
      color: "#023e8a",
      border: "1px solid #4361ee"
    }
  };
  const deployLabel = {
    "seekr-managed": "Seekr-managed instance",
    "self-managed": "Self-managed instance"
  };
  const deployments = Array.isArray(deployment) ? deployment : deployment ? [deployment] : [];
  return <div style={{
    marginBottom: "8px"
  }} className="not-prose">
      {type && <span style={{
    ...base,
    ...typeStyle[type]
  }}>{typeLabel[type]}</span>}
      {deployments.map(d => <span key={d} style={{
    ...base,
    ...deployStyle[d]
  }}>
          {deployLabel[d]}
        </span>)}
    </div>;
};

export const SupportedOn = ({ui = false, api = true, sdk = true, sdkVersion = null}) => <div className="not-prose">
    <div className="inline-flex flex-wrap items-center gap-x-5 gap-y-2 px-4 py-2.5 rounded-lg border border-[#00dad3] bg-[#00dad3]/10 text-sm">
      <span className="font-bold text-black dark:text-white whitespace-nowrap">
        Supported on
      </span>
      <div className="flex items-center gap-5">
        <span className="inline-flex items-center gap-1.5 font-semibold text-black dark:text-white">
          <Icon icon={ui ? "circle-check" : "circle-xmark"} color={ui ? "#00dad3" : "#9ca3af"} size={16} />
          UI
        </span>
        <span className="inline-flex items-center gap-1.5 font-semibold text-black dark:text-white">
          <Icon icon={api ? "circle-check" : "circle-xmark"} color={api ? "#00dad3" : "#9ca3af"} size={16} />
          API
        </span>
        <span className="inline-flex items-center gap-1.5 font-semibold text-black dark:text-white">
          <Icon icon={sdk ? "circle-check" : "circle-xmark"} color={sdk ? "#00dad3" : "#9ca3af"} size={16} />
          SDK
        </span>
      </div>
    </div>
    {sdk && sdkVersion && <div className="mt-1.5 text-xs text-black/60 dark:text-white/60">
        Requires seekrai {sdkVersion}
      </div>}
  </div>;

<Update label="October 16, 2026" description="Version 2026.9.0" tags={["Feature"]}>
  ## Teams, single sign-on, GPU selection, and database backup

  ### Role-based access control

  Users can now work together in teams. Agents, fine-tuning jobs, deployments, files, and vector databases belong to a team, and every member of the team can use them based on their role.

  * **Organization** – The top-level container for every user, team, and resource in your deployment.
  * **Teams** – Groups of users who share resources. Users can belong to more than one team and switch between them.
  * **Roles** – Organizations have Owner and Member roles. Teams have Admin and Creator roles.

  Each user also gets a personal workspace that only they can see. The upgrade moves each existing user's resources into their personal workspace. For details, see [Role-based access control](/flow/role-based-access-control).

  ### Organization setup and single sign-on for `sfe`

  `sfe org setup` creates the first administrator and your organization in one step. If your deployment uses Keycloak, it also creates the Keycloak realm and binds it to the organization. New users who sign in through single sign-on then join that organization. `sfe org setup` can also create a break-glass administrator for signing in when single sign-on is unavailable.

  Administrators can sign in to `sfe` with their single sign-on account using `sfe org login`. For steps, see [Create the first SeekrFlow administrator](/self-managed/flow/deploy/admin).

  ### GPU selection for fine-tuning

  You can now choose which GPU types fine-tuning jobs run on. Set the types in your values file, then label your GPU nodes to match. For steps, see [Create the SeekrFlow values file](/self-managed/flow/prepare/values-file).

  ### Database backup and restore

  You can now back up every SeekrFlow database with `sfe db backup` and restore it with `sfe db restore`. Reverting an upgrade doesn't undo its database changes. Restoring a backup does. For steps, see [Revert a SeekrFlow upgrade](/self-managed/flow/operate/revert-upgrade).

  ### Upgrade considerations

  * **Back up your databases first** – The upgrade changes the database schema and moves stored files to team locations, which can take hours for a large file store.
  * **Use `sfe` 3.7.0 or later** – Backup, restore, `sfe org setup`, and `sfe org login` need it.
  * **Expect agents to be briefly unavailable** – Agents are unavailable while their database migrates.
  * **Label your GPU nodes** – Fine-tuning jobs stay pending until their nodes carry `seekr.io/gpu_type`, or until `global.gpu.nodeSelectorKey` names your nodes' existing label.
  * **Tools and AI-Ready Data now deploy by default** – Set `enabled: false` for any you don't want. File search needs OpenSearch, and web search needs a Brave Search API key.
  * **Enable `sfe` sign-in on existing realms** – Run `sfe org sso setup --reconcile`.
  * **Remove `Explainability.images.runner`** – If your values file sets it, remove it. The image no longer exists.
</Update>

<Update label="July 17, 2026" description="Version 6.2026.0" tags={["Improvement"]}>
  ## Serve inference through AWS Bedrock and Azure AI Foundry

  <SupportedOn ui={false} api={true} sdk={true} />

  Cloud service provider inference adds support for Azure AI Foundry, alongside AWS Bedrock.
</Update>

<Update label="April 22, 2026" description="Version 5.2.5" tags={["Feature"]}>
  ## AWS Bedrock support extended to ingestion pipelines

  <SupportedOn ui={true} api={true} sdk={true} />

  SeekrFlow ingestion pipelines now support AWS Bedrock for embedding generation and PDF-to-Markdown conversion.

  * Embedding generation for vector databases and RAG workflows can now run on AWS Bedrock.
  * PDF-to-Markdown conversion uses Bedrock-compatible vision models, supporting AI-ready data jobs for synthetic dataset generation and downstream fine-tuning.
  * Using a `bedrock:`-prefixed model automatically routes embedding requests to AWS Bedrock.
  * Vector databases created with Bedrock models use Titan embeddings for indexing and retrieval.
</Update>

<Update label="March 12, 2026" description="Version 5.2.5" tags={["Improvement"]}>
  ## Self-hosted platform update

  <SupportedOn ui={true} api={true} sdk={true} />

  This update expands platform availability and adds new capabilities across agents, orchestration, and deployment environments.

  **New platform support**

  SeekrFlow now supports Oracle Cloud Infrastructure (OCI). Organizations can deploy SeekrFlow on OCI environments running NVIDIA GPUs, expanding deployment options for customers with Oracle cloud infrastructure requirements. OCI support currently includes:

  * SeekrFlow UI
  * SeekrFlow API

  **Agents**

  * Tool Library support for agents
  * Multi-Agentic Orchestration (Beta) — agents can coordinate across multiple tools and tasks

  **Platform**

  * OCI deployment support via Helm
  * vLLM upgrade improving inference performance on NVIDIA GPUs
</Update>

<Update label="February 2026" description="Version 5.0.X" tags={["Improvement", "Feature"]}>
  ## Self-hosted platform update

  <ReleaseTags type="improvement" />

  Updates for self-hosted SeekrFlow deployments on AWS, AWS GovCloud, and Appliance environments.

  **Agents and inference:**

  * AWS Bedrock inference support for agents with cloud service provider-hosted inference
  * Full agent execution including tools, streaming, and promotion/demotion workflows
  * Multi-LoRA inference with hot loading
  * `vLLM` upgrade for improved performance and stability
  * CSP inference routing to Bedrock endpoints based on region and model availability

  **Fine-tuning:**

  * LoRA support for reinforcement (GRPO) and instruction fine-tuning (NVIDIA-based)

  **Explainability:**

  * Inference-time data attribution

  **UI and documentation:**

  * Dark mode support
  * Documentation updates covering new inference, agent, and fine-tuning capabilities

  ## AWS Bedrock inference for agents

  <ReleaseTags type="feature" />

  <SupportedOn ui={true} api={true} sdk={true} />

  AWS Bedrock inference support for SeekrFlow Agents, providing an alternative to Seekr-hosted GPU inference. Agents can now use `Claude 4.5` via AWS Bedrock for all intra-agent inference (planner, executor, evaluator, summarizer).

  **Capabilities:**

  * Full end-to-end agent execution including Agent Chat in the UI, streaming and non-streaming runs, and multi-tool execution
  * Bedrock models appear in existing agent model-selection UI
  * Configure at deploy time via Helm (EKS-only)
  * Deployments select either Bedrock inference or Seekr-hosted GPU inference

  **Current limitations:**

  * Agents only (Model Chat is disabled when Bedrock is enabled)
  * File search and vector-backed retrieval not yet supported for Bedrock agents
  * Reasoning and speed optimization parameters are ignored to ensure consistent execution
</Update>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.