WaymakerOS Help Center

Apps are frontend applications deployed through Waymaker Host to Cloudflare's global CDN — 330+ cities, sub-50ms latency, automatic SSL and DDoS protection. Every app gets automatic builds from GitHub.

Creating an App

Required Fields

name — Used to generate the URL slug (e.g., "Customer Portal" becomes customer-portal)

Optional Fields

repository_url — GitHub repo URL (e.g., https://github.com/org/repo)
repository_branch — Branch to deploy from (default: main)
framework — Framework preset: next, react, vue, astro, svelte, remix, nuxt, gatsby, docusaurus, angular, solid
build_command — Custom build command (e.g., npm run build)
root_dir — Root directory for monorepo projects (e.g., apps/my-app)
output_dir — Build output directory (e.g., dist, .next, build)
workspace_id — Associate with a specific workspace

CLI Example

waymaker host apps create \
  --name "customer-portal" \
  --repo https://github.com/acme/portal \
  --branch main \
  --framework next \
  --root-dir apps/portal

MCP Example

"Create an app called customer-portal from github.com/acme/portal, it's a Next.js app in the apps/portal directory"

Framework Detection

If you don't specify a framework, Waymaker can auto-detect it from your repository. It checks for:

next.config.js / next.config.ts → Next.js
nuxt.config.ts → Nuxt
remix.config.js → Remix
astro.config.mjs → Astro
gatsby-config.js → Gatsby
svelte.config.js → SvelteKit
angular.json → Angular
vite.config.ts with Vue → Vue
vite.config.ts with React → React (Vite)
vite.config.ts with Solid → Solid

Monorepo Support

For monorepo projects, set the root_dir to point to your app's directory:

waymaker host apps create \
  --name "dashboard" \
  --repo https://github.com/acme/monorepo \
  --root-dir packages/dashboard \
  --build-command "npm run build" \
  --output-dir dist

The build runner will cd into the root directory before running your build command.

App Lifecycle

Status	Meaning
`pending`	Created, no deployment yet
`building`	Build in progress
`active`	Successfully deployed and live
`error`	Last build failed
`archived`	Soft-deleted

Updating an App

Change any configuration field after creation:

waymaker host apps update <app-id> \
  --branch develop \
  --build-command "npm run build:staging"

Deleting an App

Apps are soft-deleted (archived). The hosting project remains but stops receiving new deployments:

waymaker host apps delete <app-id>

Only the creator can archive an app.

Restoring an Archived App

If you archived an app and want to bring it back:

Open Host and find the archived app
Go to Settings
Click Restore
Push to your repository to trigger a new deployment

Listing in the App Store

Make your app available to other workspaces in your organisation:

Open your app in Host
Go to the App Store tab
Toggle Listed on

Other workspaces can now discover and subscribe to your app from Commander. See Listing Your App in the App Store for details.

Team & Collaboration

Every app has team members with different access levels:

Role	Access
Creator	Full access — deploy, settings, team, archive/restore
Collaborator	Deploy, edit settings, manage environment variables
Viewer	Read-only — cannot see environment variable values

See App Team & Collaboration for details on managing your team.

Next Steps

Deployment History — viewing past deployments
App Types — internal vs public apps
Listing Your App — making your app available to other workspaces
Troubleshooting Deployments — common issues and fixes

Hosting Apps