Coderunner Overview
Serverless code execution on Groundfloor — definitions, versions, deployments, and Control Plane proxy routes.
Coderunner is Groundfloor's apps runtime — deploy Node.js, Python, .NET, and other workloads. Control Plane does not replace Coderunner; it integrates via a typed HTTP client and Customer Portal management UI.
Architecture
Customer Portal / API
↓
Control Plane proxy (/v1/workspaces/{id}/apps/.../coderunner/...)
↓
Coderunner service (definitions, versions, deployments, execution)
↓
Kubernetes / runtime (per environment namespace)Public URLs for deployed functions route through the Front Door edge proxy when enabled.
Lifecycle
| Step | Description |
|---|---|
| 1. Definition | Register a named function or job |
| 2. Upload | ZIP upload creates a version (poll until completed) |
| 3. Deploy | Bind a version to CPU/memory/schedule config |
| 4. Run | Invoke via externalEndpoint or one-time execution API |
Control Plane persists Coderunner IDs in the app manifest.coderunner block.
Portal status
The Coderunners page is live but requires CODERUNNER_URL and CODERUNNER_TOKEN on Control Plane. Without them, the UI shows an integration-pending state.
App Management (pillar #6) covers Shell federated publish today; full Coderunner deploy-from-portal flows are still maturing.
Auth to Coderunner
Control Plane forwards:
| Header | Value |
|---|---|
Authorization | Bearer — Portal-minted JWT or forwarded user session |
x-client-key | Workspace UUID |
x-userid | Internal Portal user ID |
See API reference for upstream paths.
Related
- Coderunner API reference — endpoints and request bodies
- Front Door — public URL routing
- Process log — runtime logs
- Shell integration — alternative app delivery model