Coderunner Overview
Standalone serverless workloads on Groundfloor — definitions, versions, deployments, CLI/MCP, and Control Plane routes.
Coderunner is Groundfloor's apps runtime — deploy Node.js, Python, .NET, and other workloads as functions, jobs, schedules, or services. Control Plane integrates via a typed HTTP client; the Customer Portal, gf CLI, and Coderunner MCP all drive the same lifecycle.
Architecture
Customer Portal / gf CLI / MCP
↓
Control Plane (/v1/workspaces/{id}/coderunners/…)
↓
Coderunner service (definitions, versions, deployments, execution)
↓
Kubernetes / runtimePublic URLs for deployed services may route through the Front Door edge proxy when enabled. Standalone (unbound) services expose the deployment upstream URL; branded domains apply to App-bound services.
Lifecycle (D-061)
| Step | Description |
|---|---|
| 1. Definition | Create a named coderunner (workload type + runtime) — no App required |
| 2. Upload | ZIP upload creates a version (poll until build completes) |
| 3. Deploy | Bind a version to CPU/memory/replicas/schedule/env |
| 4. Run | Invoke via API or open the service endpoint |
Optional: connect a Git source and webhook (POST /v1/webhooks/git/{source_id}) for push-to-deploy. Helper bind to an existing product App with app_id is optional packaging — never create an App solely to deploy.
POST …/apps with app_kind=coderunner is rejected.
Portal and tooling
| Surface | Guide |
|---|---|
| Portal list / detail | Coderunner |
| Dev tokens, CLI, MCP | Developers |
| Promote across envs | Environment Promotion |
Requires CODERUNNER_URL and CODERUNNER_TOKEN on Control Plane.
Auth to Coderunner
Control Plane forwards:
| Header | Value |
|---|---|
Authorization | Bearer — Portal-minted JWT, gf token, or session |
x-client-key | Workspace UUID |
x-userid | Internal Portal user ID |
See API reference for upstream paths.
Related
- Coderunner API reference
- Front Door
- Process log
- Shell integration — federated UI delivery (separate from Coderunner deploy)