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.
AppSite Developer
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.
The people who build and run the platform.
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.
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.
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.
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.
Connect, branch, ship.
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.
Each developer has their own branch. Developer lists the org’s issues and milestones, and the issues assigned to you, alongside the branches.
Deploy from the same place, then trace the module to the backend and domain that serve it.
For engineers: set one up with a command, check it with a doctor, and watch every runner from Developer.
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.
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.
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.
Each developer is a named seat with AppSite Academy — the Developer certificate is included — and access granted or revoked from your environment.
Talk to us about developer seats — or, if you run AppSite, sign in to Developer.