Skip to content

Publish an agent on a website

GaugeWright has a live production proof for website agents. General self-service access is not available yet. Contact GaugeWright before you promise this feature to a customer.

In this guide, you prepare one fixed agent version and publish a panel on an allowed website.

What you need

  • A tested, fixed agent version
  • An approved model provider and hosted credential
  • The exact website origins that may use the panel
  • Session, spend, and retention limits
  • A privacy notice for visitors

1. Prepare the agent

Test the agent with safe sample input. Confirm its instructions, tools, model provider, allowed panel types, initial files, and output limits.

If the agent will collect a result, define before publication:

  • the files or transcript parts that can be collected;
  • the required data format;
  • the receiving account;
  • the maximum size; and
  • whether collection is required.

The running agent cannot widen, change, or suppress these collection rules.

2. Configure the deployment

Set:

  • allowed website origins;
  • anonymous or signed-in visitors;
  • allowed panel types;
  • session and concurrency limits;
  • spend limits;
  • retention period;
  • exact model credential; and
  • collection recipient, if used.

The model credential must match the provider and credential type allowed by the agent. GaugeDesk does not fall back to a shared key.

3. Preview

Preview the panel. Test:

  • an allowed and a blocked website origin;
  • a normal conversation;
  • refresh and resume;
  • session and spend limits;
  • a provider failure; and
  • collection validation, if used.

4. Publish

Publish the fixed version. Publication creates a signed release that cannot change.

Copy the generated integration code to an allowed website. New sessions use the active release. A session already in progress stays on the release that it started with.

The author's computer and GaugeDesk application do not serve website visitors. The hosted runtime continues to serve an active deployment when the author's computer is offline.

5. Monitor and update

Monitor sessions, model use, spend, errors, and collected results. To update the agent, test and publish a new fixed version.

Downloaded visitor material enters quarantine. Review it before you allow it into a project.

Tell visitors where data goes

Before a visitor sends data, tell them:

  • who operates the agent;
  • why you collect the data;
  • which model provider receives prompts and context;
  • that GaugeWright hosts the session;
  • what the deployment can collect;
  • how long data can remain;
  • how to make a privacy request; and
  • how to get support.

Do not say that the model runs locally. GaugeWright does not have SOC 2 or ISO 27001 certification or a completed independent penetration test.

Success check

The deployment is ready when the allowed site can start and resume a session, a blocked origin cannot start one, limits work, and collected results enter quarantine as configured.

See Current limits.