Your work. Your space.

Find the right Gonu tool for the next step.

Features & demosExplore Engineering Brain workflows and sample screensExploreWeb ChatFor quick questions, planning and everyday workTry nowDesktop WorkerFor local repository work with a dedicated desktop appDownloadVS Code ExtensionFor developers who already work in VS CodeSource betaGonu CLIFor terminal workflows and structured task inspectionSource betaGonu IDEFor developers exploring an integrated Gonu editorNot releasedDocs & demosPractical guides for every Gonu toolLearn
Skip to content
gonu.
Checking account…Try on web
Admin only

Admin: model catalog

Make reviewed Gonu-hosted model offers available to eligible users.

Open admin model settingsExplore the example

WHEN IT HELPS

Put it to work.

Operate a centrally funded model offering while customers only choose models and use their plan allowance.

Before you begin

  • Platform administrator access, separate from workspace ownership.
  • Provider credentials supplied through the existing server secret deployment process.

WALK THROUGH IT

See the workflow, step by step.

Interactive example

Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.

  1. Open Admin Settings → Gonu models & routing. Read provider connection status. Keep API keys in the server secret mechanism, never in model fields or public frontend variables.

  2. Add a direct-provider model or browse OpenRouter metadata. Verify exact model ID, context/tool capabilities, rates, tier, usage multiplier and allowed plans.

  3. Enable the reviewed offer and the global hosted switch, then save. Check visibility with an eligible account. Separately validate a small authorized live request.

gonu / Admin: model catalogSAMPLE
g.
ILLUSTRATIVE SCREEN · 1 / 3

Admin / Platform provider connections

Key configuredPresence check only
Key not configuredOperator must update server secrets
Customer setupNo personal key for Gonu-hosted offers
Example only · your real screen shows your own data.
Step 1 of 3

THE USEFUL RESULT

What you should leave with.

An explicit model catalog with centrally managed credentials and plan-aware availability.

Know the boundaries.

  • Do not store credentials in model JSON, screenshots, source control or NEXT_PUBLIC_/VITE_ values.
  • Adding a provider key does not automatically populate all models. Provider balance, access, policy and task capability can still block a request.

IF SOMETHING DOESN’T WORK

Key configured but no model appears for a user.

Check global enablement, individual offer enablement, allowed plan, capability overrides and workspace policy. Verify you saved the catalog successfully.

Contact support