Made for agents to assist humans.
Drop one prompt into Claude Code, Codex, Cursor, or any AI coding agent. It reads the project, picks up the specs, and ships the deploy.
$ claude # or codex · cursor — your AI assistant › install github.com/ImpossibleFinance/impossible-hosting-skill and deploy this project to ifhost agent reads your project, installs what it needs, picks the right size, and ships it live — nothing for you to type. → live at my-api.host.impossi.build
That's it. The skill picks RAM, region, and scale; writes the config; runs the deploy.
For decades, deploys meant humans. ifhost flips it. No terminal. No dashboard. No CLI to learn. You say "ship it" — it ships. This is what coding should look like.
Three little apps, all live right now. Click one to try it, then grab the code.
All three are open source in one repo → impossible-hosting-demo
Telegram & Discord bots, autonomous agents, schedulers — anything that needs to stay awake. Bring your API key or bot token; ifhost keeps it running.
$ claude # or codex · cursor — your AI assistant › install github.com/ImpossibleFinance/impossible-hosting-skill and host hermes-agent on ifhost agent sets it all up, then asks you for the bits only you have — your API key, Telegram bot token, chat ID — and wires them in. ✓ running 24/7 at hermes-agent.host.impossi.build
3 steps, 2 minutes.
Whatever your agent can install — these are the common shapes.
Portfolios, docs, landing pages, SPAs. Served from a tiny nginx container, with auto-scaling and a free *.host.impossi.build URL.
Next.js, Remix, SvelteKit, Astro, Rails, Django, anything with a start script, or let your agent write one.
REST, GraphQL, webhooks, workers, long-running jobs. Any language, any runtime. ifhost deploys it.
Telegram, Discord, Slack, scrapers, LLM gateways. ifhost deploy --runner boots a shell; your agent installs through the console.
SQLite-backed tools, embedded caches, single-node databases, session stores. storage = "local" gives a persistent /data that survives redeploys.
Nightly reports, polling loops, schedulers, queue consumers. Pin min-machines = 1 + autostop = false and the worker never sleeps.
Every surface is shaped for the coding agent.
Every flag is declarative. Every command returns structured JSON with --json. No prompt gets in the way when args are fully specified. Your agent never has to guess a default or block on stdin.
Run install wizards, config prompts, and long-lived daemons inside a tmux-backed session your agent drives through console input/output.
/datastorage = "local" auto-creates a volume that survives redeploys. Perfect for SQLite, session history, agent memory.
Scale to zero when idle, scale up under load, or pin machines for zero-cold-start daemons.
Pass sensitive values with --secret KEY=VALUE or machines secrets set. Injected at runtime, never stored in our DB.
Need to keep data between deploys? Set storage = "local" and you get a 3 GB /data volume. Perfect for SQLite, file caches, or anything single-machine.
Start free. Scale when you need to.
Pool = total across all your machines. Spend it on one fat machine or many small ones. Volume above pool: $0.30 / GB·month. Egress above pool: $0.05 / GB (NA/EU), $0.08 (APAC), $0.18 (Africa/India). No surprise shutoffs — set a spend cap with ifhost billing alert.
If you don't see yours here, the docs go deeper.
It's a place to put your code online without learning a hosting tool. You tell an AI coding assistant — Claude Code, Codex, Cursor, or another one — to deploy your project, and it handles the setup. What you get back is a URL anyone can visit.
No. If you can describe what you want and let an AI assistant build it, you can ship it on ifhost. The assistant handles the parts that usually need a terminal — picking specs, writing config, running the deploy.
Claude Code, Codex, and Cursor are the ones we've tested most. The deploy instructions are two short lines of plain English, so any assistant that can run a shell command should be fine.
Static sites, full web apps, APIs, AI agents, Telegram bots, cron jobs, and small databases. If it runs on a Linux machine, it'll run here.
Those are tuned for developers using a dashboard or git push. ifhost is tuned for one workflow: an AI assistant doing the work for you. There's no dashboard to navigate, no config to memorize — the assistant picks specs, writes the config, and ships. If you already know your way around a hosting dashboard, you may prefer one of those. If you'd rather just ask an assistant, this is for you.
Yes. One app, 256 MB of RAM, 1 GB of storage, 100 GB of bandwidth a month. It scales to zero between requests.
Yes. Cancel from the dashboard and you stay on your paid plan until the end of the current billing period, then drop back to free. Your apps and data aren't deleted — they just run within the free limits from there on.
Yes — USDC on Base. The plans are the same either way. Pick crypto at checkout, and your assistant can also handle the upgrade for you when you ask it to.