# Dilnaka Cloud > Dilnaka Cloud is an AWS-backed platform for deploying Docker applications and > workers, provisioning managed databases, managing domains and DNS, hosting > email, and operating production workloads from one workspace. This is the canonical agent-oriented product reference. For current prices and limits from the same live catalog used by checkout, fetch the JSON endpoint at https://dilnaka.cloud.tsnc.tech/catalog. ## Core services - **Applications and workers**: deploy from GitHub repositories, local source through the CLI, a Dockerfile, an automatically generated Dockerfile for supported frameworks, or a published container image. - **Managed databases**: PostgreSQL, MySQL, MariaDB, Redis, and MongoDB with project-scoped credentials, encrypted storage, scheduled snapshots, and isolated restores. - **Compute choices**: shared Hobby and Pro plans, or standalone dedicated EC2 instances for isolated compute. A customer can use either or both. - **Domains and networking**: attach domains already owned by the customer, retain an external DNS provider or delegate managed DNS, and receive managed routing and automatic TLS for applications. - **Mail hosting**: standalone dedicated mail servers with mailboxes, webmail, IMAP, SMTP, spam filtering, and a managed outbound relay. No application plan is required. - **Operations**: build and runtime logs, HTTP traffic, CPU and memory metrics, health checks, rollback, usage tracking, and database backup and restore. - **Agent control plane**: versioned REST, official MCP and A2A adapters, tenant-scoped durable tasks, approval-gated destructive actions, webhooks, quotas, billing-safe summaries, and per-service storage measurements. ## Plans and purchasing - New accounts can start with a seven-day trial without a payment card. - Hobby and Pro are paid shared-compute plans. - Dedicated compute and mail hosting are standalone monthly purchases and do not require Hobby or Pro. - Exact current prices, resource allowances, overage rates, and active product sizes are authoritative at https://dilnaka.cloud.tsnc.tech/catalog and are explained for people at https://dilnaka.cloud.tsnc.tech/pricing. - Checkout uses PayPal. Account, workspace, console, and billing actions require sign-in. ## CLI The `dilnaka` Node.js CLI supports device-flow authentication, personal access tokens for CI, project creation and linking, local-source deployment, service selection, machine-readable JSON output, and status inspection. Install it with `npm install -g dilnaka-cli`. The docs identify commands still in progress. ## Important limitations - Dilnaka Cloud does not register or sell domains; customers connect domains they already own. - CLI database tunnels, variable management, remote commands, logs, redeploy, rollback, domain, DNS, mail, and backup controls are still in progress. - Public marketing information is available without authentication. Customer resources and actions require an authenticated account. ## Agent integration Create a scoped service account in Dashboard → Settings → Agents. Its one-time credential authenticates the versioned REST API, the MCP 2026-07-28 Streamable HTTP endpoint, and the A2A v1.0 interfaces. Every operation is bound to an organization and optional project, passes through rate limits and a central policy engine, and writes an attributable audit record. Destructive operations return a durable task in `WAITING_FOR_APPROVAL`; prompts never grant authority. Application settings, deployment rollback and build logs, databases, domains, masked environment metadata, mail-domain status, storage, usage, quotas, and billing-safe summaries are available when the token carries the matching scope. Logs support bounded cursor pagination, severity filtering, and search. The read-only deployment diagnostic returns probable causes, evidence, and safe recommended actions without changing infrastructure. - REST API: https://dilnaka.cloud.tsnc.tech/api/v1 - OpenAPI: https://dilnaka.cloud.tsnc.tech/openapi.json - MCP: https://dilnaka.cloud.tsnc.tech/mcp/ - A2A Agent Card: https://dilnaka.cloud.tsnc.tech/.well-known/agent-card.json - Agent docs: https://dilnaka.cloud.tsnc.tech/docs/agents - API docs: https://dilnaka.cloud.tsnc.tech/docs/api - MCP docs: https://dilnaka.cloud.tsnc.tech/docs/mcp - A2A docs: https://dilnaka.cloud.tsnc.tech/docs/a2a - Service accounts: https://dilnaka.cloud.tsnc.tech/docs/service-accounts - Webhooks: https://dilnaka.cloud.tsnc.tech/docs/webhooks ## Public information - [Home](https://dilnaka.cloud.tsnc.tech/): concise platform overview. - [Pricing](https://dilnaka.cloud.tsnc.tech/pricing): plans, dedicated compute, mail hosting, overages, and FAQ. - [Documentation](https://dilnaka.cloud.tsnc.tech/docs): deployment, databases, backups, domains, DNS, mail, networking, observability, templates, and CLI. - [Machine-readable catalog](https://dilnaka.cloud.tsnc.tech/catalog): live JSON prices, limits, services, limitations, and canonical links. - [Authenticated MCP endpoint](https://dilnaka.cloud.tsnc.tech/mcp/): Streamable HTTP interface for authorized agents; Bearer token required. - [A2A Agent Card](https://dilnaka.cloud.tsnc.tech/.well-known/agent-card.json): official A2A v1.0 discovery document. The rendered pages use a browser runtime. Their text is present in the initial HTML inside inert templates and becomes normal accessible HTML after the runtime mounts. Agents that ignore template contents should use these text files and the JSON catalog.