Glossary
The words Qaldy uses (the City, a gate, an isolate, a manifest, the Trust Score) in one sentence each, with a link to the page that explains them.
| Word | What it means |
|---|---|
| Workspace | A company's place in Qaldy. Its apps, people, keys and settings belong to the company, not to whoever created it. |
| App | A tool or automation that runs in a sandbox. A site and a backend project are apps of their own kind. |
| The City | The home screen: every app is a building, every automation a road, every run a car. Everything in it is real data. See Get started. |
| Island | A workspace's patch of the City. Its size follows the workspace's plan. |
| Plan (of an app) | What Qaldy would build, shown with every permission as a sentence, before anything is built. See Build your first app. |
| Manifest | The list of everything an app may do. Anything not on it is denied. See App manifest. |
| Trust Score | A 0 to 100 score from static checks on an app version. Under 60 is never published. See Approvals and the Trust Score. |
| Sandbox / isolate | The small, fast environment an app runs in, with no network of its own and no secrets inside. See The sandbox. |
| Gate | The service every request to an app and every call out of one passes through. It checks sharing, checks permissions, adds keys and writes the audit log. See The gate and write-only secrets. |
| Egress | Anything leaving the sandbox for the internet. Closed by default. |
| Connector | How an app talks to another service (Telegram, Sheets, an HTTP API) without ever holding its key. See Connectors. |
| Write-only | A key that can be put in but never read back, by anyone. |
| Runner, viewer, editor | What a person may do with one app: run it, open it, change it. See Share it. |
| Builder, admin, owner | A person's role in the workspace. See Permissions and roles. |
| Safe band | The plainest builds and changes an agent may approve by itself. Everything wider waits for a person in the console. See Approvals. |
| Audit log | A hash-chained record of every action and every refused call. See The audit log. |
| Spending cap | The most a workspace can spend each month beyond its plan. On by default. See Plans and the spending cap. |
| MCP | The protocol your own coding agent uses to talk to Qaldy. See Build with your own agent. |
| Budget | A smaller limit inside the spending cap for one app, automation, agent token or member. Soft ones tell you; hard ones stop new work. See Spending cap. |
| Shield | The gate's per-person, per-address and per-app limits, daily limit and flood detector for apps others can open. See Spending cap. |
| Control plane | Qaldy's API and its database: sign-in, sharing, builds, billing, the audit log. Apps keep serving for a while without it. See A bad day. |
| Checkpoint | A daily signed statement of how long a workspace's audit chain was and what it ended in, signed with a key that is not in the database. See The audit log. |
| Exposure check | A check that questions a throwaway copy of an app the way a stranger would, before a public link. See Exposure check. |
| Panic button | One step that revokes every token, key and open sign-in of a workspace. See Keys and the panic button. |
| Published tool | An automation an owner chose to show to their colleagues' agents as an MCP tool. See Automations as tools. |
| Try link | An invitation to a locked trial workspace for a day, with no account. See Try it. |
| Pilot, Preview, Planned, Mock | Pilot: live, with rough edges. Preview: built from the provider's documentation and not run live yet. Planned: not built. Mock: the screen works and nothing real happens. |