Glossary

The words you see in CloudJod, a sentence or two each.

5 min read

Each word links to the guide, or the part of one, that explains it.

Agent: A coding tool at work in Develop under a name of its own, such as claude-1. Agents claim tasks, lock the files they are changing, and send each other messages; the Agents board shows what each is doing. Agents working together
API token: A secret a script uses in place of a password. It acts as the person who made it, never above their role, and can be made to expire. API tokens
App: One program that runs: a website, an API, a worker. Each has its own address, logs, settings and releases, and can run as several copies. Apps
Approval: A change somebody made that waits for an owner to approve it before it happens. Whose changes wait is up to the owners. Trust and approvals
Area: A part of an organization, such as its apps, its databases or its servers. A person or a role can be limited to some areas. Areas
Build: Turning code into an image that can run. A failed build changes nothing that was running. Builds
CLI: The cloudjod command: what the dashboard does, from a terminal or a script. The CLI
Cluster: A group of servers. An app chooses the cluster it runs on. Your own servers
Command: Something run once with an app's settings, such as a database migration, rather than kept running. One-off commands
Custom role: A role the owners define from a set of permissions, optionally limited to areas. Your own roles
Database: A Postgres or Redis database CloudJod runs for you. An app attached to it is given its connection string. Databases
Department: A part of a large organization, such as HR or Sales, with its own apps and people, on the organization's plan. Departments
Develop: Where the coding tools you use meet your apps: their code, your team's notes, tasks and skills, and a record of what each tool did. CloudJod runs no model of its own there. Develop
Domain: A hostname of your own, such as app.example.com, that an app answers on once you prove you own it. Connect a custom domain
gVisor: A kernel of its own between each workload and the machine, so code that breaks out of its container meets gVisor rather than the host. Everything here runs under it. Your apps, kept apart
Health check: A path CloudJod requests to know a copy of an app is ready. Any 2xx or 3xx answer counts, and a copy is sent traffic only once it answers. Create an app
MCP: The Model Context Protocol: how coding tools such as Claude Code, Codex and Cursor talk to CloudJod. Coding tools, over MCP
One-click app: Ready-made software, such as WordPress or Grafana, installed in one step. One-click apps
Organization: Your team's account: its people, apps, databases, servers and plan. You can belong to several. Teams and access
Preview environment: A copy of an app made for a pull request, so a change can be tried before it is merged. Preview environments
Process type: Another program run from the same app and release, such as a background worker, with its own number of copies and no address of its own. Several processes from one app
Project: One system you run, such as a shop or a CRM, with all of its parts: its apps, one-click installs and databases. Getting started
Release: One version of an app that has run: the exact image and the settings it ran with. Rolling back returns to an earlier release in one step. Releases and rolling back
Replica: One running copy of an app. Traffic is spread across the copies that are ready. Scaling
Role: What a person may do in an organization: owner, admin, member, viewer, or a role the owners define. Roles
Server: A machine of your own, attached with one command, that runs apps as part of a cluster. Your own servers
Skill: Instructions your coding tools follow while they work, shared by your team. Skills
Task: A piece of work on the Develop board, for people and agents: open, doing, in review, blocked or done. Notes and tasks
Template: A one-click app of your own, made from one of your apps or from code, that your team installs in one step. Your own templates