# Your company's tools. Built from a sentence.

Qaldy Cloud runs your company's tools, automations and small backends. Describe one in plain words, or let your own coding agent build it. Every app runs in a sandbox, locked down by default.

URL: https://docs.qaldy.com/

Qaldy Cloud is in a live pilot. These pages describe what runs today. Anything that does not yet is marked [[Preview]] or [[Planned]], and billing is [[Mock]].

:::cards
- [Get started](https://docs.qaldy.com/getting-started/)
  Sign up, build your first app from a sentence, and share it with your team. About ten minutes.
- [Build with your own agent](https://docs.qaldy.com/mcp/)
  Connect Claude, Claude Code, Cursor or ChatGPT over MCP, or use the `qaldy` command line. The client owns the workspace.
- [Connectors](https://docs.qaldy.com/connectors/)
  Telegram, Google Sheets, email, GitHub, Kaspi, Bitrix24 and any HTTPS API. Keys go in once and never come back out.
- [Guides](https://docs.qaldy.com/guides/)
  A backend with rules, your team and handover, the spending cap and budgets, keys and the panic button, the audit log, the phone.
- [API reference](https://docs.qaldy.com/reference/api/)
  Every route of the control plane, generated from the code that serves it.
- [How it stays locked down](https://docs.qaldy.com/concepts/)
  The sandbox, the gate, permissions and the audit log. What we guarantee, and the proofs that check it.
- [Security](https://docs.qaldy.com/security/)
  The threat model, the 17 recorded proofs, and what is still planned.
- [Kazakhstan](https://docs.qaldy.com/kazakhstan/)
  Where data lives today, the printable statement, invoices in tenge and the local stack. Residency is Planned.
:::

## Pick your way in

**You run a company, a team or an operations desk.** Start with [Get started](https://docs.qaldy.com/getting-started/). You describe a tool in a sentence, read the plan and every permission as plain words, approve it, and it runs. Share it like a document; people who only look are free.

**You build software for clients.** Keep your own tools. Add the Qaldy server to Claude Code or Cursor with [MCP](https://docs.qaldy.com/mcp/) or the [command line](https://docs.qaldy.com/cli/), and build into a workspace the client owns. When the work ends, their access to you ends on a date you both can see.

**You run small products of your own.** A [backend](https://docs.qaldy.com/reference/api/backend-data-api/) with tables and a REST API, [sites](https://docs.qaldy.com/reference/api/sites/) at their own address, apps that run per request and sleep when idle, and a hard spending cap that is on by default.

## What is real today

:::note The honest list
The console at [app.qaldy.com](https://app.qaldy.com), the API, the MCP server, the runtime and the gate are running for the pilot. **Preview** means built from the provider's own documentation and not yet run against a live account. **Planned** means not built. **Mock** means the screen works and nothing real happens (billing is the main one). Every page that depends on one of these says so near the top.
:::