Build Sites
Apps with several pages and pages anyone can open
A site is an app on the Site plan. On top of everything a Pro app has, a site can:
- have several pages, each with its own address — for example
/products,/contactor/account/orders; - make pages public, so people without an Operator account can open them;
- set a title and description per page, which browsers, search engines and link previews show.
Plans at a glance
| Plan | Daily cost | What you get |
|---|---|---|
| Free | none | The app itself, ERP.net data and AI |
| Pro | 1 credit per day | Everything in Free, plus Operator Cloud: files, tables, secrets, web requests, triggers and procedures |
| Site | 2 credits per day | Everything in Pro, plus Pages: extra page addresses, public access and custom domains |
Usage adds to the daily cost.
When you need a site
Choose Site when the app must reach people outside your team, or needs separate addresses:
- Landing page for a product or a campaign.
- Public contact or order form that customers fill in without signing in.
- Product catalog showing live ERP.net prices and stock.
- Shareable dashboard — for example delivery status a partner can open from a link.
- Several distinct screens that people bookmark or share, such as
/reportand/settings.
You do not need a site for an internal tool that only signed-in colleagues use on one screen. Pro (or Free, if you don't need storage) is enough.
Examples
- "A stock dashboard for my warehouse team" → Pro.
- "A page where customers check their order status with an order number" → Site.
What a public page can and cannot do
A visitor of a public page is not signed in. So a public page cannot use:
- your ERP.net connection;
- the app's tables or stored files;
- secret values.
Anything it shows from a server comes through a web request marked Public. A public request runs on the server with its own stored login (for example an ERP.net service user), kept under Secrets. The App Builder sets these up for you — you only type in the login values.
Example: a public catalog page calls a public request "Get products", which logs in to ERP.net with a service user and returns names and prices only.
Mark a request Public only when its result is safe for anyone to see.
Switching an app to Site
- Open the app in the App Builder.
- Go to Properties.
- In the plan card, choose Upgrade on Site.
The Pages tab appears next to Cloud.
Downgrading from Site removes the Pages tab and turns every public page, including a public Home page, back to non-public.
Next steps
- Getting Started — build a simple public site step by step.
- Page Settings — access modes, addresses and page settings.