Skip to content

title: Bifrost description: Bifrost is an AI gateway: one OpenAI-compatible endpoint in front of the model providers you register, with virtual keys, budgets and request logs.

Bifrost

What is it

Bifrost is an AI gateway: one OpenAI-compatible endpoint in front of the model providers you register, with virtual keys, budgets and request logs. It is the gateway of the LLM gateway page.

The platform offers it as a managed application: an Argo CD Application the platform creates for you - from the shop or from the marketplace's Bifrost (managed) template - and keeps in sync with the chart. Its secrets are generated once at deployment, its hostname sits on the app domain of your cluster, and the platform watches its health. The same chart installed by you (helm install, or the plain template) is unmanaged: it runs in your project like any other workload, and nothing on the platform side follows it.

How to create

Through the marketplace. In the console (web.grn.cloud) open the Developer Catalog, choose Bifrost (managed) and fill in the application name and the hostname. The result is an Application in your home project; its resource tree shows the project it creates and what runs in it. The deployment also appears as an order in the shop, so your account lists every application you run; a paid product is billed from the day of the deployment.

Through the shop. Bifrost Free (free, monthly) in the shop, on the AI cluster: your gateway answers at https://<hostname>.ai.grn.cloud. Type the hostname on the order line and confirm; a mail tells you when the application is reachable, with its address and a link to the Application in the console. The first order also creates your cloud account on that cluster (welcome mails).

How to make changes

Configuration lives in the Application: open it in the GitOps page of the console, and the YAML tab shows the chart values under spec.source.helm.valuesObject - that is where the dashboard password and the encryption key are read. Values the platform set for you (the hostname, the generated secrets) are kept; the other values are yours to change, and Argo CD applies the change at the next sync. Change the settings of an application walks through it.

A shop application follows its order line: a larger plan, another storage size or a new hostname is a change of the subscription in the shop (or a new order line), and the platform updates the application to match; the chart version follows the product. A marketplace application's chart version is its own targetRevision: Versions, upgrades and removal covers both.

How to cancel

Ordered in the shop: cancel the subscription in the shop. The application is removed ten minutes after the order line ended. Created from the marketplace: delete the Application in the GitOps page; the project it created and everything in it go with it, and the order line in the shop ends within the hour.

Deletion removes the application's data with it. Make and keep your own backup before you delete: the platform keeps none for you.

References