AppSite Developer

Run the platform’s engineering from inside AppSite.

Repositories and the branch each developer works on, the cloud projects, hosting and DNS that serve every module, the functions, databases and keys behind them, and the module registry the whole platform reads — without leaving the desk.

Who it’s for

The people who build and run the platform.

Developers

Your branch, your issues, your deploys.

Repositories and milestones across the org, the issues assigned to you, and the branch you work on — each developer on their own, enforced — with deploys run from the same place.

Own branchMy issuesDeploy
Platform and IT

The map of what serves what.

Google Cloud projects, App Hosting backends, hosting sites and DNS, functions, databases and buckets, and the billing behind them — every module traced to where it is served from.

App HostingDNSFunctions
Owners

Keys kept server-side, access you can see.

API keys held server-side and never pasted into code, each on a rotation schedule — rotated automatically where the provider allows it, flagged for an owner to rotate when due everywhere else — plus single sign-on, the security and policy settings, and roles and usage for everyone who touches the platform.

Key rotationSSORoles & usage
The module registry

The platform, in one place.

Every module’s entry — where it is served, where it opens, what it is called and what appsite.ca says about it — is edited here, and every Hub, Desk and Home reads it.

  • AppSite modules — the registry: host, entry path, label — the Hub and the Desk open modules from it.
  • Module copy — the words appsite.ca shows for each module, written here.
  • Repositories & branches — the SDK and its modules, a branch per developer.
  • Cloud & hosting — Google Cloud projects, App Hosting, hosting sites, DNS, functions, databases, buckets.
  • Connectors — GitHub, Google Cloud, Apple Developer and single sign-on.
  • Developers & sandboxes — developer profiles, roles and assignments, and sandboxes to try things in.

From a repo to a release in three steps

Connect, branch, ship.

Step 1 · Connect

Name your GitHub org and Google Cloud projects.

Set them once on your tenant — the org’s repositories and the cloud projects then appear, read through AppSite’s server-side access with no tokens in the browser. Nothing to copy by hand.

GitHubGoogle Cloud
Step 2 · Branch

Work on your own branch.

Each developer has their own branch. Developer lists the org’s issues and milestones, and the issues assigned to you, alongside the branches.

Own branchMilestones
Step 3 · Ship

Deploy, and see where it landed.

Deploy from the same place, then trace the module to the backend and domain that serve it.

DeployServed from

The appsite CLI: your computer is the runner

For engineers: set one up with a command, check it with a doctor, and watch every runner from Developer.

Set it up

One command, then a doctor.

setup.sh or setup.ps1 installs what is missing and starts the runner with the computer. Then appsite doctor checks that Claude Code is signed in with your subscription — not the API — and that Firestore, GitHub and Chrome are ready.

setup.sh · setup.ps1appsite doctorStarts with the computer
Run on

Your computer, or Google Cloud Shell.

The Cyber Check record’s Run on picker sends a fix, a repair or a scan to whichever runner is on. Cloud Shell has its own setup script and answers while a tab is open; a deploy needs a computer that has the repo.

Run on pickercloudshell-setup.shDeploys stay local
Watch it

Live output from every runner.

Developer’s Dashboard lists each runner — on, waiting or off, and the Claude account answering for it — with the output it is printing, refreshed every few seconds, and the setup commands to copy. It shows real runners, not a practice terminal. For platform operators.

On · waiting · offLive runner outputSetup commands
Start

Developer seats come with AppSite Enterprise.

Each developer is a named seat with AppSite Academy — the Developer certificate is included — and access granted or revoked from your environment.

Put your engineering on the platform.

Talk to us about developer seats — or, if you run AppSite, sign in to Developer.