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.
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.
qaldy command line. The client owns the workspace.ConnectorsTelegram, Google Sheets, email, GitHub, Kaspi, Bitrix24 and any HTTPS API. Keys go in once and never come back out.GuidesA backend with rules, your team and handover, the spending cap and budgets, keys and the panic button, the audit log, the phone.API referenceEvery route of the control plane, generated from the code that serves it.How it stays locked downThe sandbox, the gate, permissions and the audit log. What we guarantee, and the proofs that check it.SecurityThe threat model, the 17 recorded proofs, and what is still planned.KazakhstanWhere 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. 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 or the command line, 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 with tables and a REST 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.