Cloud vs on-premise Agents

On this page

A public site can run on a Cloud Agent or on a Physical Agent (on-premise). The path a visitor takes is the same for both. What changes is whether the site depends on the building it belongs to.

Use a Cloud Agent for a site people depend on: a clinic booking page, a hotel event site, a retail promotion, a restaurant menu, a school open-day form. A Physical Agent (on-premise) remains a valid choice when you want the app to stay on site, or when most of the visitors are in the building.

The same path for every visitor

A visitor is routed to the nearest Performance Hub gateway. That gateway reaches the Agent over the Agent's existing outbound connection. The Agent does not accept an inbound connection, on either kind of Agent. The request is checked, then sent to the app container. The diagram is on Public Sites, and the rules are on Security and isolation.

Gateway and relay nodes run in the same regions as our Cloud Agents. Visitors are routed to the closest node automatically, the way a CDN routes them. The list of gateways grows as demand grows. Visitor traffic is not held in one region. The site's content stays on your Agent. For a Cloud Agent, that is in the Cloud region you chose when you added it.

The gateway does not keep a copy of the site. If the Agent is offline, there is nothing for the gateway to serve. Neither kind of Agent sleeps when it is idle.

How the two compare

Cloud AgentPhysical Agent (on-premise)
Serving pathNearest gateway, then the Agent's outbound connectionThe same path
Always onYes. It restarts on its ownIt runs while the facility has power and internet
Facility power and internetNot usedRequired. If either drops, visitors cannot open the site
Load on the facility networkNoneVisitor traffic shares the facility's connection
The connection visitors feelA datacentre connection, which is typically more consistentA facility line that is also carrying the site's own business
Where the content staysOn the Cloud Agent, in the Cloud region you choseOn the appliance at the site
Fair useIncluded in the Cloud Agent cost. There is no separate Public Sites charge50 GB per month, because visitor traffic goes through Performance Hub relay nodes
When the Agent is offlineThe gateway does not serve a copy of the siteThe same

Visitor traffic goes through the gateway to the Agent. That is why a Cloud Agent's connection is the better fit for a public site, and why a Physical Agent (on-premise) has a fair-use limit. The 50 GB a month is not a billable extra. See Limits and fair use.

Cloud Agent hours are listed on Platform pricing. Public Sites does not add a line of its own.

Add the Agent you want

Add Agent asks where the Agent should run. Choose Cloud Agent or Physical Agent.

Add Agent, offering a Physical Agent or a Cloud AgentAdd Agent, offering a Physical Agent or a Cloud Agent

Figure 1: Choose a Cloud Agent or a Physical Agent when you add the Agent

  • Cloud Agent — "Launch a Cloud Agent Instance in a region you choose. No pairing." You pick the region and the size. See Add a Cloud Agent.
  • Physical Agent — "Pair an on-site device with a serial number or QR code." The appliance is the AI Agent Processor. It needs ordinary outbound internet, and it does not need an open inbound connection.

On an Agent that cannot cap a container's memory and CPU, the readiness panel says "This AI Agent can't cap the app's memory and CPU, so a very busy site can slow the agent down." A busy public site is another reason to prefer a Cloud Agent.

When a Physical Agent (on-premise) is the right choice

Keep the app on a Physical Agent when the data should stay on hardware at the site, or when the people opening it are already there: a waiting-room board, a staff page that you later decide to share with a password, a timetable on the gym floor. Placement, power and the network are covered on The hardware.

The fair-use limit still applies. A site that draws visitors from outside the building, or that serves large files, belongs on a Cloud Agent.

Move an app to another Agent

The app's files live on the Agent that runs it. To run the same app on a different Agent, restore a backup onto that Agent, publish the app there, and turn the public site on. See Backups and Restore & recovery.

A custom domain can only be connected to one site. Remove it from the old site before you add it to the new one. Unpublishing the old app disconnects its custom domains so they can be used elsewhere. See Unpublish the app.

Removing an Agent takes its published apps, and their public sites, offline. The gateway does not keep a copy of the site.