Publish your first site
On this page
This page takes one app from a conversation with your Agent to a link you can send. The examples follow two fictional sites: Harbourview Dental, a clinic booking page anyone can open, and Alpine Lodge Winter Gala, a hotel event page behind a password. The same steps work for a retail promotion, a restaurant menu, a school open-day form, a gym timetable or a supplier page.
A Cloud Agent is the better place to host a site people depend on. See Cloud vs on-premise Agents.
Before you start
The app has to be running on the Agent, and its status has to be Active. Static pages, a Python app, a React front end with an API, or your own container all work, as long as the app serves HTTP and passes the public-ready checks.
Ask the Agent to build it to that standard. For example: "Build a booking page for Harbourview Dental, with services, opening hours and a form. Make it ready for the public internet." Review the result in the Agent before you publish it. The Agent can build the app. It cannot put the app on the internet. Only a person can do that.
Then publish the app to the Performance Hub menu and open it there, the way your staff will. That review is the check before anyone outside Performance Hub can open it. See The Published Apps tab.
Internal tools should stay on the menu. A staff roster or a stock lookup is not a public site.
Open Public site
- In Performance Hub, open AI Agent.
- Select the Agent.
- Open Device management, then Published Apps.
- On the app's row, click Public site.
The dialog is titled Public site: {app name}.


Figure 1: Public site on the published app's row
The dialog opens with: "Let people outside Performance Hub open this app in a browser. It gets its own web address with HTTPS, and you can add your own domain."
If the app is paused, the dialog says "The app is paused, so its public site is offline until you resume it." and "Resume the app before putting it on the internet." Resume it, then come back.
The same dialog is one click from two other places:
- In Edit published app, the Public site section shows Publish to Internet before the site is on, and Manage public site once it is.
- In the Agent's tab settings, Publish to Internet… has the tooltip "Give this app its own web address on the public internet".


Figure 2: Manage public site, from Edit published app
You can also open the app itself from Published Apps in the desktop app. Turning the site on is done in Performance Hub.
Choose who can open it
Under Who can open it, pick one audience.
| Audience | Help text |
|---|---|
| Only Performance Hub | "Not on the internet. People open it from the Performance Hub menu." |
| Anyone with the password | "Visitors enter a password you choose before they see the app." |
| Anyone on the internet | "Anyone with the address can open the app." |


Figure 3: The three audiences. The site is not on the internet until you put it there
Anyone on the internet is right for a booking page, a menu or an open-day form. Anyone with the password is right for a guest list, a real-estate shortlist or an event page you only want to share with people who have the password. Only Performance Hub takes a live site back off the internet. See Take a site off the internet.
Set the web address
Web address suggests a first part from the app name. You can change it. Until the site is created, the rest is a masked 8-character code, and the hint reads "You can change the first part. A fixed 8-character code is added when the site is created."


Figure 4: The first part is yours. The code is added when the site is created
Use 2 to 40 characters: lowercase letters, numbers and single hyphens, starting and ending with a letter or a number. A clinic might use clinic-booking. A hotel event might use winter-gala. Reserved names, and names that could be mistaken for a login or another brand, are refused.
After the site is live, the hint changes to "You can change the first part. The code after it stays the same." The finished address looks like https://clinic-booking-a1b2c3d4.ph-sites.com.
You can add your own domain later. See Custom domains and DNS.
Wait for the readiness check
The dialog checks the app before it can go on the internet. First it says "Checking the app is safe to put on the internet…".
When the check passes: "The app is ready for the internet."


Figure 5: A passing readiness check. The note under it is shown when this Agent cannot cap the app's memory and CPU
On an Agent that cannot cap the app's memory and CPU, the panel also says "This AI Agent can't cap the app's memory and CPU, so a very busy site can slow the agent down." A site you expect to be busy belongs on a Cloud Agent. See Cloud vs on-premise Agents.
When something fails, the panel says "Fix these before the app can go on the internet:" and lists the problems. One example is "The app's container is also connected to other networks." The note under the list reads "Public apps run in a locked-down container, so a problem in the app can't reach the rest of your AI Agent or your network."


Figure 6: The app is not ready. Ask the Agent to fix the list, then check again
Click Ask the agent to fix these, then Check again. Put on the internet stays disabled until every problem is fixed and the acknowledgement is ticked. The rules are explained on Security and isolation.
Acknowledge what you are publishing
The acknowledgement is different for a public site and a password site. Put on the internet stays disabled until the box is ticked. The same confirmation is required when the site is saved.
For Anyone on the internet:
"I understand that anyone on the internet can use every page of this app, including admin pages. Performance Hub sign-in no longer protects it, so it mustn't show private information unless it has its own sign-in."


Figure 7: Put on the internet stays disabled until the acknowledgement is ticked
Read that sentence against the app you just reviewed. If any page shows private information, and the app has no sign-in of its own, stop here and keep the audience on Only Performance Hub.
A site with a password
Choose Anyone with the password and enter a password of 8 to 128 characters. The hint reads "At least 8 characters. Share it only with people who should see the app."
The password acknowledgement is shorter. It does not include the clause about private information:
"I understand that anyone with the password can use every page of this app, including admin pages. Performance Hub sign-in no longer protects it."


Figure 8: A password site for Readiness Test, with the password field empty and the acknowledgement still unticked
Share the password only with the people who should see the app. A common password, a repeated run of characters, or the site's own name is refused. The password is stored only as a salted hash. See Passwords.
Put it on the internet
Tick the acknowledgement and click Put on the internet.
The dialog says "Setting up the web address. This usually takes under a minute." The live address then appears, with Copy address and Open site, and the tip "If the address doesn't load yet, wait 30 seconds and try again. A new address can take a moment to reach every network."


Figure 9: The site is on the internet. Copy the address or open it
The first time any app on an Agent goes public, the Agent opens a separate outbound connection for visitors. The site may be unreachable for a minute or two while that happens. Wait, then try the address again.
The owner and the organisation admins are notified by email, in the notification bell and by push. Turning the site on is recorded in Audit Logs as the underlying Performance Hub action.
Send the link. For a password site, send the password separately.
A live password site looks like this. The password field reads "Leave blank to keep the current password", and the hint reads "A password is set. Entering a new one signs everyone out, and they need the new password to get back in."


Figure 10: A live password site. The address, the password and your own domain are managed here
What the visitor sees
A password site shows "This site is password protected." and "Enter the password to continue." The visitor clicks Enter. The footer reads "Hosted on ph-sites.com · Report abuse".


Figure 11: What a visitor sees before a password site opens
A correct password opens the app. The visitor's browser keeps a secure, HTTP-only cookie for 7 days, or until you change the password.
A site with no password opens straight onto the app.


Figure 12: A public booking page. Put a contact address such as hello@example.com on your own site
The pages a visitor sees are in English.
After it is live
Change the app on the Agent and visitors see the new version. There is no separate deploy step. Every request is checked again. If an update breaks a public-ready rule, visitors see "This site isn't available yet" until it is fixed.
To rename the address, change the password, pause the app or take the site off the internet, see Managing sites. To serve it on www.example.com, see Custom domains and DNS.
Related pages
- Public Sites
- Custom domains and DNS
- Security and isolation
- Managing sites
- The Published Apps tab
- Access control: who can open the Agent