Glossary
Every Groundfloor term, in one place.
| Term | Meaning |
|---|---|
| Activity log | The record of who changed what, and when, in an organization or workspace. Kept for 30 days. More |
| App | Packaging for one product: what users open, its address and who can launch it. Either a Shell app or a standalone app. More |
| App authentication | How your app's users sign in: none, Groundfloor sign-in, or your own identity provider. More |
| App user | Someone who signs in to your apps on the Shell site. Not part of your team, and never signs in to the Client Portal |
| Client Portal | Groundfloor's web interface, at console.groundfloor.cloud. Tour |
| Coderunner | Code you run on Groundfloor: a Function, Job, Schedule or Service. More |
| Collection | A table of records in Data Vault |
| Data Vault | Where you browse, query and edit collections, and grant access to them. More |
| Dataplane | Groundfloor's data API: the one API your code uses to read and write collections, whichever database they're in |
| Deployment | A version of a Coderunner, running with its settings: CPU, memory, instances, environment variables |
| Deployment URL | The address of a deployed Function, Job or Service |
| Environment | dev, staging or prod. Secrets, flags, Coderunners and app releases are kept per environment. More |
| Execution | One run of a Function, Job or Schedule |
| Feature flag | A value your code reads to turn features on or off without redeploying. More |
| Function | A Coderunner that runs your handler when a request arrives. More |
gf | Groundfloor's command-line tool. More |
| Groundfloor MCP | Lets AI coding agents inspect your workspace and read these docs. More |
| Handler | The function you write for a Function, Job or Schedule. Coderunner calls it; you don't write a server |
| Job | A Coderunner that runs once and finishes. More |
| LLM Gateway | Access to AI models through one key per workspace. Coming soon. More |
| M2M token | A token for code that runs with nobody signed in: Coderunners, CI, servers. More |
| Managed database | A dedicated PostgreSQL database for one workspace. More |
| Manifest | groundfloor.manifest.json: a Shell app's name, pages and colours. More |
| Organization | Your company or team on Groundfloor. It holds your workspaces, team and plan. More |
| Process Log | Your code's output and errors. More |
| Promote | Copy secrets, flags, app releases or Coderunners from one environment to another |
| Role | What someone can do. Your team has Owner, Admin, Billing admin, Writer, Member and Partner in an organization, and Owner, Admin, Writer, Member and Partner in a workspace; app users have roles such as viewer, user and admin |
| Schedule | A Job that runs on a timetable. More |
| Secret | An API key, password or token, stored encrypted per environment. More |
| Service | A Coderunner that runs any container serving HTTP. More |
| Shared database | The PostgreSQL database every workspace gets. More |
| Shell app | A web app that runs in your workspace's Shell site, with sign-in, data, files and flags built in. More |
| Shell site | Your workspace's web address for Shell apps: <workspace-slug>.app.groundfloor.cloud |
| Site access | Which app-user roles can use each collection, your files and each app. More |
| Slug | A short, URL-safe name, such as my-first-app |
| Standalone app | A product made from your own Coderunners, with its own domain. More |
| Starter kit | The ready-made project you build a Shell app from. More |
| Team | The people who build and run your workspaces. More |
| Tenant | One of your app's customer companies, when Multi-tenant sign-in is on |
| Version | One upload of a Coderunner's code. Deploy any version, including an older one |
| Workspace | One project, holding its Coderunners, apps, data, files, secrets and flags. More |