Skip to content

Insites AI

How the Pieces Fit Together

Last updated 18 November 2026

The three parts of Insites AI, how one question flows through them, and where CloudShell fits.

The parts

Insites AI is pre-release. This page was written against the build of 31 October 2026 and will be revised at release.

Insites AI is made of three parts. Knowing which part does what explains where your data goes and who can change what.

PartWhere it runsWhat it does
The AI pages in the adminYour browser, inside the site adminThe chat panel, Reports, History, Configuration, Automations, and the Slack and Site assistant settings. It holds no secret keys.
The AI features on your siteYour siteStores your conversations, the record of every change, the credit ledger and your settings. It checks roles and data exclusions on every read, and it applies a change only when an administrator confirms it.
The Insites AI serviceHosted by InsitesRuns the AI model, meters usage and credits, and runs the scheduled jobs. The key for the AI model exists only here, never on your site.

One question, start to finish

  1. You type a question in the chat panel. Your site gives your browser a short-lived token that proves who you are and what role you have.
  2. The service checks your credits. If they are used up, it stops here, before any AI call.
  3. The service adds context: your private notes, the owner's rules, and the Insites Logic Engine guidance the task needs.
  4. The AI model works through the question. Each time it needs data, it calls a tool on your site. Your site checks your role and the excluded tables and fields before it answers.
  5. The answer comes back with any chart, and one credit charge is recorded for the turn.

Where CloudShell fits

CloudShell and Insites AI are separate, and they serve different people:

  • Insites AI is for the people who run the site. It works inside the admin, and a confirmed change is written straight to the site, the same way as an edit made in the admin.
  • CloudShell is for developers who use their own AI tool. It connects that tool to a site so it can read, deploy and sync files. See About CloudShell.

A change made through Insites AI does not reach a Git repository on its own. If your team deploys from a repository, pull the change first, or a later deploy will overwrite it. This is the same rule as for any edit made in the admin. Owners can turn on a commit message for every applied change, so the change is easy to describe when you commit it. See Configuration and Data Access.

The Insites Logic Engine

Before Insites AI writes a site file, it reads the Insites Logic Engine: the public rules for how to build on Insites. Your own AI tool can read the same rules through CloudShell. Data about your site always comes from your site, never from the Logic Engine. See Insites Logic Engine.

Scheduled work

Some work runs without anyone starting it. You do not configure the schedule; results appear in Reports and on the Assistant page.

WhenWhat runs
Every 5 minutesAutomations, so record and form triggers react within five minutes
Every hour, at five pastDue saved questions, due pinned charts, then automations
NightlyThe daily digest, and re-reading your site for the site assistant