AgenticGrid
Tenants

One backend. Many personalities.

Each tenant is a per-utility (or per-audience) instance of AgenticGrid running on Azure Container Apps. Same React. Same skills. Same governed backend. A tenant-specific system prompt gives the agent its voice; an isolated Azure Files share holds its data; a branded URL fronts the whole thing.

01

Live + demo

What's running today.

Customer instances (Transgrid, MTS) are sign-in-restricted to their organisations. Demo instances (Default analyst, AER review lens, Sparky for Year 9–10 STEM) open with Microsoft sign-in once the lead-capture gateway lands — for now they're previewable via screenshot below; reach us to walk through one live.

Generalist analyst
AgenticGrid Default

Generalist analyst — capability list grounded in NER, AEMO and AER rules. Drop-in starting point for any utility.

Methodology reviewer
AER (review lens)

Methodology-first replies, citation-led, every claim traceable to a CBA Guidelines clause or VCR/VoLL source.

Year 9–10 STEM
Sparky — STEM

Year 9–10 teacher persona that turns a real Broken Hill challenge into a class lesson. Same backend, same tools — friendlier voice.

02

How a tenant is born

One command, four assets, one URL.

Provisioning a new tenant runs through the agenticgrid-deploy-webapp skill:

  1. Build + push the image. Same Docker image as every other tenant — esbuild-bundled webviews + synth-headless ingress.
  2. Create the Azure Files shares. Distribution areas, knowledge corpus, scenarios — all isolated per tenant.
  3. Seed the data. Server-side clone of an existing tenant's distribution areas (≈30 s) or upload from local for the first tenant.
  4. Drop in the system prompt. A markdown file in the tenant share. Change the voice without touching code.
  5. Bind the branded URL + cert. ACA managed certificate, custom domain optional.

The first tenant takes about a day end-to-end. Subsequent tenants take an afternoon.