Cloudish
See your company’s Brand Profile.
Overview
Tagline Brand-provided · 2026-10-20
Cloudish is the cloud an AI agent deploys a container to. Vercel assumes a person, a git repo, and a framework. Cloudish assumes an agent, a Dockerfile, and a prepaid key.
Description Brand-provided · 2026-10-20
Cloudish — an agent-first container cloud: the cloud an AI agent deploys a container to. Built by Hal9 Inc.
Also known as Brand-provided · 2026-10-20
- cloudish.ai
- Cloudish by Hal9
- Cloudish AI
Identity
Mission Brand's website · 2026-10-07
Provide a cloud where agents can independently deploy and run containers without requiring a human signup, cloud console, local Docker daemon, registry, or credit card.
Website Brand-provided · 2026-10-20
https://cloudish.ai
Voice & tone Brand-provided · 2026-10-20
Technical, plain-spoken and anti-hype — developer-to-developer. Short declarative sentences, lowercase product naming, concrete specifics (endpoints, curl commands, vCPU/GB, exact credit math) over adjectives. Defines itself by what it removes: 'no Kubernetes YAML, no registry to host, no reverse proxy to configure by hand,' 'no credit card, nothing to sign up for first.' Disarmingly honest and self-aware — openly concedes that Vercel, Render and Fly are better for human dashboard workflows, and admits only one datacenter is live in production. Dry wit and a light sci-fi/space motif (moonbase, regolith, rover-planner, 'then orbit stops being a joke') keep it playful without being salesy. Unusually, it speaks directly to machines as readers ('Agent reading this page: the full API reference lives at /skill.md'), which is itself the brand's core statement.
Offerings
Problem solved Brand-provided · 2026-10-20
Cloudish is the cloud an AI agent deploys a container to. Vercel assumes a person, a git repo, and a framework. Cloudish assumes an agent, a Dockerfile, and a prepaid key. Operator: the agent signs itself up — one unauthenticated POST https://cloudish.ai/api/v1/keys returns a key; no browser, no card, no OAuth, no human approval. Unit: any Dockerfile, build context, or image, built server-side with no local Docker daemon and kept running as a long-lived process at a permanent URL, with an optional persistent volume; SQLite, WebSockets, workers and MCP servers are supported workloads, not edge cases. Money: credits are prepaid on the key (1 credit = $1), metered by the second, and the agent can never spend past its balance; any key can mint child keys for free and transfer credits to them. Surface: the skill file (cloudish.ai/skill.md) and the HTTP API are the product; a human can claim a key later for a dashboard, but nothing requires one.
Core capabilities Brand-provided · 2026-10-20
Turn an agent-built localhost app into a live URL, Host apps with persistent storage or Postgres | Cloudish container hosting — server-side Docker builds from a build context or image reference, run at a live HTTPS URL, Deploy API (POST /api/v1/projects) with single-endpoint build/run status polling (building / running / failed) and build logs, Key API (POST /api/v1/keys) — unauthenticated key creation plus free child-key minting, Credit ledger and key-to-key credit transfers (agents funding sub-agents), Persistent storage volumes per project (e.g. /data, 5 GB; files, Postgres, survives restarts, redeploys and idle scale-downs), Encrypted per-project environment secrets, injected at runtime, never returned by listing calls, Managed subdomains and custom domains with automatic TLS certificates, 'Sign in with Cloudish' — a standard OpenID Connect identity provider backed by Auth0, Scale-up / scale-to-zero compute metered by the second (default 0.5 vCPU / 1GB), Web dashboard — project status, build history, live logs, credit transfers, and a credit-value slider, SKILL.md — an Anthropic-style agent skill file generated from the live API, installable into Claude Code, Codex, Cursor, Grok, Regional datacenter endpoints addressable by subdomain (do.cloudish.ai New York live; seattle.cloudish.ai in testing; more cities planned)
Products / SKUs Brand-provided · 2026-10-20
Cloudish container hosting — server-side Docker builds from a build context or image reference, run at a live HTTPS URL, Deploy API (POST /api/v1/projects) with single-endpoint build/run status polling (building / running / failed) and build logs, Key API (POST /api/v1/keys) — unauthenticated key creation plus free child-key minting, Credit ledger and key-to-key credit transfers (agents funding sub-agents), Persistent storage volumes per project (e.g. /data, 5 GB; files, Postgres, survives restarts, redeploys and idle scale-downs), Encrypted per-project environment secrets, injected at runtime, never returned by listing calls, Managed subdomains and custom domains with automatic TLS certificates, 'Sign in with Cloudish' — a standard OpenID Connect identity provider backed by Auth0, Scale-up / scale-to-zero compute metered by the second (default 0.5 vCPU / 1GB), Web dashboard — project status, build history, live logs, credit transfers, and a credit-value slider, SKILL.md — an Anthropic-style agent skill file generated from the live API, installable into Claude Code, Codex, Cursor, Grok, Regional datacenter endpoints addressable by subdomain (do.cloudish.ai New York live; seattle.cloudish.ai in testing; more cities planned)
Pricing Brand-provided · 2026-10-20
Prepaid credit model, no tiers and no subscriptions. Credits are bought upfront like a gift card and metered by the second; spend is hard-capped at the balance on the key, so there is no card on file and no invoice after the fact. 1 credit = $1.00 (slider example: 10 credits = $10.00). Illustrative value at 10 credits: ~6.2 days of an always-on container at the 0.5 vCPU / 1GB default, or ~343 typical image builds (~10 min each at ~3 vCPU / 5GB). Live rates: https://www.cloudish.ai/pricing.json and cloudish.ai/instances.md. New keys include 0.1 credits to start, subject to availability; no credit card and no signup required. Credits can be transferred key-to-key, and a human 'claiming' a key deposits credits onto the same key the agent already uses.
Audience
Target industry Brand-provided · 2026-10-20
Two linked audiences. Primary technical user: AI coding agents themselves (Claude Code, Codex, Cursor, Grok and other agent runtimes) that need to ship a container without a human clicking through a console — plus multi-agent systems where a parent agent spawns and funds sub-agents. Primary human buyer: developers, indie hackers, prototypers and AI-curious builders who vibe-code apps, APIs and dashboards with an agent and need a shareable public URL fast, without an AWS console, a Kubernetes setup, or entering a credit card. Secondary: agent/tool builders who want deployment as a callable capability. Buying intent is immediate and bottom-of-funnel — 'my agent built something on localhost and I need a link someone else can open today' — with low commitment risk (free credit grant, no card, prepaid cap). Explicitly not targeting teams that want a human-driven dashboard workflow (deferred to Vercel/Render/Fly) or enterprises with a platform team running production infra on AWS/GCP.
Customer base Brand's website · 2026-10-07
AI agents and people using coding agents such as Claude, Codex, and Grok; developers deploying containerized applications, APIs, dashboards, workers, and MCP servers.
Ideal customer profile Brand-provided · 2026-10-20
AI coding agent (Claude Code, Codex, Cursor) at Solo builder / side project
Use cases Brand-provided · 2026-10-20
Turn an agent-built localhost app into a permanent URL, Run long-lived processes Vercel-style platforms refuse: SQLite-backed apps, WebSocket servers, background workers, MCP servers, Keep files on a persistent volume across restarts and redeploys, Let a parent agent mint and fund child keys for sub-agents with a hard spend cap
Customer outcomes Brand's website · 2026-10-07
- AI agents can obtain their own API key and deploy without waiting for a human
- Applications built locally become reachable through a persistent HTTPS URL
- Containers can keep running beyond serverless function timeouts
- Application data can persist across restarts and redeployments
- Compute spending is capped by the prepaid balance on an API key
- Developers can inspect build status, deployment status, and logs through the API or dashboard
- Agents can deploy without installing Docker locally or managing a registry
- Applications can use encrypted runtime secrets and managed authentication
Landscape
Differentiation Brand-provided · 2026-10-20
The operator is the agent: it signs itself up with one unauthenticated POST /api/v1/keys, deploys any Dockerfile or image as a long-running container with an optional persistent disk, and spends prepaid credits it can never exceed — no human, browser, or card at any step.
Unique advantage Brand-provided · 2026-10-20
The operator is the agent: it signs itself up with one unauthenticated POST /api/v1/keys, deploys any Dockerfile or image as a long-running container with an optional persistent disk, and spends prepaid credits it can never exceed — no human, browser, or card at any step.
Page last updated 2026-10-20.