SSiteForge Admin

Owner access

Admin token

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

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.

Template operations

Templates and versions

Upload template ZIP

Upload status

Waiting for a template ZIP.

  • Validate package
  • Store assets in R2
  • Create D1 records
  • Enable preview
  • Publish to gallery

Imported templates

Loading templates...

Customer accounts

Create and manage customer websites

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

New customer

Create a brand new customer site

Use this for a new paying customer, demo account or test site. The template you choose will be copied into their own customer workspace.

Existing customers

Manage customer sites

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

Revenue

Subscription tiers

Starter

Growth

Agency

Widget marketplace

Embeds and add-ons

Library

Uploaded widgets

Loading widgets...

Add widget

Compliance defaults

Policy templates

Privacy policyDefault for all sites
Cookie policyRequires cookie banner
Booking termsService businesses

Edit default policy

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, create the native app shell, add the store signing files, then download the finished Apple .ipa and Google .aab.

Create store-ready app shell

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

Use the files you create in the customer Apple Developer account. SiteForge generates the Apple export settings automatically.

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.

App permissions needed

Step 1: choose a customer site, then press the button. SiteForge will queue Codemagic for the final .ipa and .aab. Fallback packs are only created if hosted build cannot be queued.

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, request the builds, then download the finished .ipa for Transporter and .aab for Google Play when the build service returns them.

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/Codemagic creates the Android upload keystore for new apps.
5. Hosted buildPress Create app shell and request IPA/AAB.Codemagic builds the final store upload files.
6. Download resultsBuild jobs shows the finished .ipa and .aab.The .aab goes to Google Play; the .ipa goes into Apple Transporter.

Hosted build jobs

Finished Apple and Google build files appear here when the connected build service uploads them back to SiteForge.

No build jobs loadedRequest a hosted build or press refresh.

Operations

Support and audit log

Template uploadedMaison ElaraToday
Customer preview openedDemo accountToday
Policy updatedCancellation policyDraft