Dashboard
MRR
$—
Active
—
customers
Starter
—
$15/mo
Custom
—
$20/mo
Pro
—
$29/mo
🏪 Boutique Capacity
0 / 100
GitHub Actions
Connect GitHub to view Actions
New Customer Workflow
1
Add the customer — Customers tab → + Add Customer. Fills in name, slug, email, tier, and theme colour.
2
Create the app — Builds tab → 🛠️ New App. Scaffolds the build folder in GitHub and generates a Cowork prompt to paste into a new session.
3
Build in Cowork — open a new Cowork session, paste the prompt. Claude builds the app in
builds/{slug}/. Review, commit, push.4
Mark Ready — back in the Builds tab, set the build status to Ready so the Publish button appears.
5
Publish — click Publish. Everything is automatic: GitHub repo, Pages, DNS, Cloudflare Access OTP policy, and portal cascade to all of the customer's existing apps.
6
Push the portal — run the generated command to deploy the client-facing site.
7
Custom / Pro tier only — register the client's own API keys via
POST worker.appsforhire.app/admin/set-client-keys after publishing.Builds
Apps in progress — build in Cowork, then publish to the client's repo
Loading builds…
Customers
Loading…
| Client | Tier | App URL | Status | Since | Actions |
|---|---|---|---|---|---|
| Loading… | |||||
Access Audit
Cross-reference Cloudflare Access policies against customer records
🔵 Admin / Dev Emails — shown in audit but not flagged
First email in the list is used for the per-app dev access toggle (📥 / 📤).
Click Run Audit to check every Cloudflare Access policy against your customer records. Requires Admin Secret (🔑).
🧪 Dry Run & Workflow Health
Validate any build before committing, and check all system integrations
GitHub API
—
CF Worker
—
CF Access API
—
GitHub Token Scopes
—
Run a Dry Run — simulate publish without writing anything
📱 App Gallery
Manage which apps appear in the public demo gallery — toggle visibility, thumbnails, and demo links