Owner access

Admin token

Add your owner token once here. SiteForge will use it across templates, widgets, customers, domains and app exports.

Owner API token

Control centre

Platform overview

Manage the templates, customer workspaces, policies, widgets, plans and domains that power the subscription platform.

-Templates

Uploaded website products in your library.

-Widgets

Embeds and add-ons available to customers.

-Customer sites

Accounts, allocations and temporary sites.

-Bookings

Requests received from customer websites.

Customer dashboard

Latest customer activity

Enter your owner token to load the customer dashboard.

Customer accounts

Create and manage customer websites

This area creates a separate customer website account. It does not change your main SiteForge platform.

Existing customers

Manage customer sites

Select a customer below to edit their template allocation, domain, embed code and team access.

Loading site accounts...

Selected site

Site

Open site preview

Allocate template

Business name Template Existing website URL to show

Only needed for the plain embed template. Use the original website address, not the custom domain you are connecting here.

Custom domain

QR launch links

The QR code is created automatically. Add the store links when the apps are live; the same QR code will keep working.

Website link Apple App Store link Google Play link

Add a custom domain to show the 20i CNAME setup.

Whole-site embed code

Use this to embed the customer’s whole website into another page while their domain is being connected.

Open embed

Automatic site QR code

Customers scan this once and choose Website, Apple or Google. Store links can be added later without replacing the QR code.

Permanent QR destination

Download QR Open QR page

Team invites

No invites yet.

Revenue

Subscription tiers

Starter

Monthly priceTemplates allowedWidgets

Growth

Monthly priceTemplates allowedWidgets

Agency

Monthly priceTemplates allowedWidgets

Widget marketplace

Embeds and add-ons

Library

Uploaded widgets

Compliance defaults

Policy templates

Privacy policyDefault for all sites

Cookie policyRequires cookie banner

Booking termsService businesses

Edit default policy

Policy nameDefault wordingApplies to

Cloudflare

Domains and routes

20i customer instructions

Customers only need to create one CNAME at 20i. SiteForge stores the matching site entry so the Worker knows which website to show.

Record typeCNAME Namewww Value / targetshowcaseyourwebsite.co.uk

Customer domain entries

Enter your owner token to load customer domains.

Website to app

Convert customer websites into Apple and Google apps

Pick a customer website or App Studio build, add the customer Apple signing files, then request the finished Apple IPA and Google AAB builds.

Create store-ready app shell

Owner API token Search apps/templates Customer site, App Studio app or live template Convert the linked website into an app shellSiteForge uses the selected customer website/App Studio URL as the live app source, then adds the native wrapper, loading screen, offline screen, icons, permissions and store files around it.

App name Bundle / package ID

App description

Primary colour Accent colour

Apple category Google category

Apple Team ID Google Play app-signing SHA-256, optional for first AAB

Build and upload the first AAB before adding the Google Play app-signing SHA-256. Play Console shows that fingerprint after app signing is set up.

Apple App Store signing

For each customer: create a CSR on your Mac, create the Apple Distribution certificate in their Apple Developer account, export it from Keychain as a .p12, create the App Store provisioning profile, then upload the .p12 and .mobileprovision here.

Distribution certificate .p12 Distribution certificate password App Store provisioning profile .mobileprovision SSL push certificate .p12, only if push is enabled SSL push certificate password

Google Play signing and services

SiteForge creates the Android upload keystore automatically. Save the generated keystore safely because future updates to the same Google app must use the same upload key. The package name cannot be changed after release.

Existing upload keystore, only for updating an app already published

Keystore password, optional Key alias

Key password, optional

Google SHA-1 fingerprint Google project ID

google-services.json, if Firebase/push is enabled

Final app icon, 1024 x 1024 PNG recommended Splash / launch screen image

App permissions needed Camera or photo uploadsUse only if customers can upload photos, receipts, profile images, review images or booking images. Microphone or video recordingUse only if the app records voice notes, videos, calls or audio messages. Location, maps or nearby servicesUse if customers see directions, nearby branches, delivery areas, table/location tools or map features. Push notificationsUse if the app sends booking updates, order updates, event reminders, offers, loyalty rewards or customer alerts.

Apple Transporter upload file, if already built Google Play upload file, if already built Store screenshots Extra store files from Apple or Google

Step 1: choose a customer site, add the Apple signing files, then press the button. Finished .ipa and .aab files appear in Build jobs when the builders complete.

What SiteForge now generates

Native app shell linked to the selected customer website or App Studio build
Loading, offline/error screen and mobile app wrapper configuration
Apple App Store metadata, review notes, association file and Transporter handoff
Google Play listing, app content baseline, TWA config and assetlinks file
Capacitor project with build scripts for iOS and Android
Apple signing checklist and uploaded certificate/profile references
Android keystore, package name, SHA fingerprints, Google services and Firebase push checklist

The aim is one simple action: pick the customer website, add the app details and signing files, request the hosted builds, then download the finished .ipa and .aab from Build jobs.

Finished files

Build jobs

Loading builds...Checking for finished AAB and IPA files.

GoodBarber-style process

1. Customer websiteSelect the customer website or App Studio build.This is the live app source.

2. App detailsConfirm app name, bundle/package ID, colours, description and permissions.These become the store metadata and native config.

3. Apple filesAdd the customer Apple Team ID, .p12 certificate and App Store provisioning profile.SiteForge creates ExportOptions.plist automatically.

4. Google filesPaste SHA values or Google project details if needed.SiteForge creates the Android upload keystore for new apps.

5. Request buildsPress Request IPA/AAB builds.SiteForge queues the Apple and Google build jobs.

6. Download final filesUse Build jobs to download the finished .ipa and .aab.The .ipa goes into Apple Transporter.

Operations

Support and audit log

Template uploadedMaison ElaraToday

Customer preview openedDemo accountToday

Policy updatedCancellation policyDraft

Admin token

Platform overview

Latest customer activity

Templates and versions

Upload template ZIP

Upload status

Imported templates

Edit template

Create and manage customer websites

Create a brand new customer site

Manage customer sites

Site

Allocate template

QR launch links

AI update customer site

Whole-site embed code

Automatic site QR code

Invite team admin

Team invites

Subscription tiers

Starter

Growth

Agency

Embeds and add-ons

Uploaded widgets

Add widget

Policy templates

Edit default policy

Domains and routes

20i customer instructions

Customer domain entries

Convert customer websites into Apple and Google apps

Create store-ready app shell

What SiteForge now generates

Build jobs

GoodBarber-style process

Support and audit log