Coderunner
Run your code on Groundfloor — functions, jobs, schedules and containers — without managing servers.
Coderunner runs your code on Groundfloor. Upload it from the Client Portal, the gf CLI or an AI agent, and Coderunner builds it, runs it and scales it. You don't manage servers.
Choose a workload type
Each Coderunner has one workload type. Pick the one that matches how your code should run:
| Type | Choose it when your code should… | For example | Public URL |
|---|---|---|---|
| Function | respond to a request | an API, a webhook, a tool for an AI agent | Yes |
| Job | do a task once and finish | an import, a report, a backfill | Yes, mainly for testing |
| Schedule | run a job on a timetable | a nightly cleanup, a daily report | No |
| Service | stay running and serve HTTP | a web app, a dashboard, any container | Yes |
To change a Coderunner's type later, create a new Coderunner.
What you write
For a Function, Job or Schedule you write one function, the handler, and Coderunner calls it. You don't write a web server or a Dockerfile. Supported languages:
| Language | Files at the root of your ZIP | Reference |
|---|---|---|
| Node.js | handler.js, package.json | Node.js |
| Python | handler.py, requirements.txt | Python |
| .NET | Handler.cs, CodeRunner.Function.csproj | .NET |
| Go | handler.go, go.mod | Go |
| Rust | handler.rs, Cargo.toml | Rust |
More languages are on the way.
A Service is different: it's any container that serves HTTP, so you bring a Dockerfile and the application, in any language.
How a Coderunner is organized
Coderunner e.g. "Customer importer"
├── Versions each upload of your code
└── Deployments a version, running, with its settings
└── Executions each run of a Function or Job- A version is created every time you upload code. You can deploy any version, including an older one.
- A deployment runs a version with its settings: CPU, memory, how many instances, environment variables and, for a Schedule, its timetable.
- An execution is one run. Its status, output and errors are kept so you can troubleshoot.
Ways to work with Coderunner
| Tool | Best for |
|---|---|
| Client Portal — Build → Coderunner | Creating, deploying and watching Coderunners in a browser |
gf CLI — gf deploy | Deploying from your terminal or a CI pipeline |
| Groundfloor MCP | Letting an AI coding agent inspect and deploy for you |
| Coderunners API | Automating everything from your own code |
All four use the same Coderunners, versions and deployments.
Before you start
- A workspace where you're a Writer, Admin or Owner. See Members and roles.
- For the CLI:
npm install -g @groundfloorcloud/cli, thengf login.
You don't need to set up App authentication to use Coderunner. That's only for signing in your app's own users.
Next steps
- Quick start — deploy a first function in five minutes.
- Functions — write, deploy and call a function.
- Configuration and secrets — environment variables, secrets and resources.