Introduction
What Groundfloor is, and what you can build with it.
Groundfloor is a platform for building and running applications. You bring the code; Groundfloor runs it and gives it the services most apps need — a database, file storage, secrets, sign-in for your users, feature flags and access to AI models — without you setting up any infrastructure.
You manage everything from the Client Portal at console.groundfloor.cloud, from the gf command-line tool, from AI coding agents through the Groundfloor MCP, or directly through the Groundfloor API.
What you can do
| You want to… | Use | Guide |
|---|---|---|
| Run code: an API, a webhook, a background job, a scheduled task or a container | Coderunner | Deploy |
| Ship a web app with sign-in, users, data and files already built in | Shell apps | Apps |
| Store and query data | A shared database in every workspace, or a managed database of your own; browse it in Data Vault | Data |
| Store files | Files | Files |
| Keep API keys and passwords out of your code | Secrets | Secrets |
| Separate dev, staging and production, and promote between them | Environments | Environments |
| Turn features on and off without redeploying | Feature flags | Feature flags |
| Call AI models with one key per workspace (coming soon) | LLM Gateway | LLM Gateway |
| Let your team in, and control who can do what | Team and roles | Members and roles |
| Let your app's own users sign in | App authentication | App authentication |
How it fits together
Everything you create lives in a workspace, and workspaces belong to an organization — your company or team. A workspace holds your code, data, secrets and settings, and is split into environments such as dev and prod. Core concepts explains each of these in a page.
Next steps
- Quick start — deploy your first function in about five minutes.
- Core concepts — organizations, workspaces, environments and roles.
- Client Portal tour — where everything is.