Ask away.
What people want to know before signing up. Pick how you'd like it explained.
The gist
What you're getting into
So what am I signing up for?
A computer of your own in the cloud, with an AI already running in a terminal in your browser. Tell it what kind of website you want. It writes the whole thing, serves it from that same machine, and hands you a live link. No setup weekend.
Do I need to know how to code?
No. If you can describe a thing out loud, you're qualified. Say what you want, say when it's wrong, keep going till it's right. And if you do write code, nothing's locked away — real machine, real files, keys to the whole car.
How's this different from a website builder?
Builders hand you a box of blocks and a fence around the yard. This hands you the yard. No template gallery, no grid to fight, no wall you hit at 11pm when you want the one thing they never thought of.
Isn't this just AI with extra steps?
Most of the work in "making a website" was never the website. It was the servers, the deploys, the dashboard you forgot the password to. An AI on your laptop still leaves you all of that. Here, the machine writing your site is the same one answering the door when somebody shows up.
Getting started
What you bring, how long it takes
What do I have to bring?
A browser and a Claude account. The AI runs on your machine signed in as you, so the first thing you'll do is click through Claude's own login. Your conversations stay between you and Anthropic — we're not standing in the middle taking a cut.
Do I have to install anything?
Not a thing. Terminal, editor, files — all of it in a browser tab. Nothing to keep updated on your laptop, nothing to uninstall later.
How long till something's live?
Your computer's ready in a couple of minutes, usually less. A first version of a simple site turns up a few minutes after that. The building screen shows what's actually happening — no fake progress bar.
What if I get stuck?
Say so, right there in the terminal. It's a conversation, not a form. "That's not what I meant." "Bigger photos." "Put the hours back." You can also cut it off mid-build — no sitting politely while it finishes something you already hate.
Your machine
It's actually yours
Is it a real server, or a sandbox?
Real as it gets. You get root. apt install sticks around
after a restart, systemd runs, Docker runs. Anything that runs on a
Linux box runs on yours.
Is there anything I'm not allowed to do with it?
Barely anything. No crime, nothing aimed at other people's systems, no spam or crypto mining — the whole list is on the terms page and it's short. Past that it's your computer: install what you want, delete what you want, publish what you want. Nobody reviews it, nobody approves it, nobody asks what it's for.
Can I host a whole application, not just a website?
That's the point. A database, logins, payments, an API, file uploads, an admin page only you can see — Postgres, Redis, Node, Python, Go, Docker, whatever the job calls for. It's a real server, so it runs real server things, and one computer holds as many apps as you feel like piling on it. Nobody's counting.
What happens when I close the tab?
If Claude's mid-job it keeps working until it's finished — closing the tab doesn't cancel anything. Your terminal session is kept either way, so come back tomorrow on some other machine and it's where you left it, conversation and all. Refresh it, sleep the laptop, lose the wifi — same session when you're back.
Can I run something on a schedule — a nightly job, a cron?
Not dependably yet, and it's the one thing that catches people out. Your computer naps when nobody's using it, and a sleeping machine can't wake itself, so a job set for 3am only runs if something else woke the box around 3am. On a busy site frequent jobs go off fine; a nightly job on a quiet site won't. Until we ship a proper scheduled wake, run anything time-critical somewhere that's always awake and let it call your site — or ask us, because we'd rather hear it than have you find out.
Does my site go down while I'm off doing other things?
Never. Your computer naps when nobody's using it — that's how a flat price stays flat — but the website's up the whole time. Somebody knocks, it's awake in about a second, page served.
Can I get in there and change things myself?
However you like. Ask in the terminal, open a full editor in the browser, or work the file browser — upload, download, rename, drag a folder of photos straight in. Mix and match, day to day.
What if it breaks something? What if I break something?
There's a reset button, and it's meant to get used. It rebuilds the system from a clean image and leaves your stuff exactly where it sat — home folder, your site, all of it.
Do you back up my files?
No — same as any server you'd rent yourself. Pull anything precious down through the file browser, or ask for a git repo pushed somewhere safe. That's a one-sentence ask. Reset brings back the system, not your work, and that difference is worth knowing before you need it.
Going live
Addresses and domains
What address does my site get?
A free subdomain — yourname.iwmwn.app — with HTTPS from
the start. Plenty of people never bother moving off it.
Can I use a domain I already own?
Yes. One record at your registrar, pointed our way, and that's it for good — we'll never ask you to change it again. Not for resets, not for upgrades, not for anything we rearrange on our end. Certificates issue and renew themselves.
Is this going to mess with my email?
No. We take the one record you point at us and leave the rest of your domain alone. Your MX records don't move.
Do you sell domains?
No. Buy yours wherever's cheapest and aim it over here. There are plenty of registrars already — we'd rather not be one more.
Money
What it costs, and how you leave
What's this cost me?
Free plan, no card. Paid runs $14 to $79 a month with hosting and domains in the price. The AI is on your own Claude account, billed by Anthropic. Whole breakdown's on the pricing page.
Can I get hit with a surprise bill?
No. There's no overage on any plan, anywhere. Push past what your plan covers and things get slow — that's the whole penalty. We never quietly run your card for the difference.
What are you measuring over there?
Three numbers, once a minute: how busy the processor was, how much
memory your stuff is holding, how much disk you've filled. No
filenames, nothing about what's inside them, nothing about who visited.
The code doing the counting is plain readable JavaScript on your own
machine at /opt/platform/box-runtime/hostd-samples.js — go
read it, we'll wait.
What happens to my stuff if I cancel?
It stays put. Downgrades and cancellations land at the end of the period, and nothing gets deleted — machines you're not paying for go to sleep with everything intact. Extra domains just detach, ready whenever you come back.
Is the code mine?
All yours. Plain files on a machine you control — HTML, CSS, whatever else it wrote. Download the lot and host it wherever you please. Nothing here only works because we're underneath it.
The technical bit
For people who read the man page
Everything above holds whether or not you care about this part. If you do, here's the shape of it.
What am I actually getting, in specs?
A Linux machine with root, its own filesystem and its own IP-facing
hostname, bursting to 8 vCPU. Memory ceiling and disk depend on your
plan — see the pricing page. Not a container
with the sharp edges filed off: systemd is PID 1, so
systemctl, docker compose, and
apt all behave the way they do everywhere else, and
packages survive a stop/start.
What exactly does reset keep and what does it throw away?
It keeps /home, /root, and /srv
— your files, your site, your configuration in those trees — and
rebuilds the rest from the image. That's what makes it a reliable way
out of a broken system rather than a coin flip. Anything you care about
outside those three, move it or back it up.
How does my site stay up if the machine is asleep?
Requests come in through our edge, which wakes the machine and holds the connection until your web server answers. A cold wake is on the order of a second. Nothing to configure, and you never need a keep-alive for the website's sake — the wake rides the request. Keeping it awake for background work is a different question, and one we answer honestly above.
What happens to a long-running process when it sleeps?
It freezes where it stands and continues on the next wake — the machine is paused, not shut down, so nothing is killed and no state is lost. Claude is the exception: while it's working it holds the machine awake, which is why a long build finishes with the tab closed. Anything else you start yourself pauses once the last visitor leaves and picks up when the next one arrives. Wall-clock time passes while it's frozen, so code that assumes it ran continuously — a timer, a lease, a heartbeat to somewhere else — should expect a gap.
Can I expose something that isn't HTTP?
Not from the outside. Traffic reaches you over HTTPS through our edge, and that request is also what wakes the machine — so websites, APIs and WebSockets all work, while a raw TCP listener (a game server, a mail server) has nothing routing to it and nothing to wake it. Inside the box, bind whatever ports you like; it's the front door that's HTTP.
How does the custom-domain routing work?
You point one record at us, we issue a certificate for that hostname at
the edge, and requests reach your machine with the original
Host header intact — so name-based virtual hosts work
normally and which site answers stays your business. That's why we only
ever need the one record, and why we never need another.
Can I use my own stack, my own build, my own everything?
Yes — nothing about the platform assumes a framework. Nginx serves your files on day one because something has to, but replace it, put your own process in front, run several services, containerize the lot. The only contract is that something listens for HTTP.
What about SSH?
The browser terminal is the way in today, and it's a real one — tmux underneath, sessions that survive disconnects, your editor of choice. [PLACEHOLDER: confirm SSH availability before launch — it's in the "deliberately out of the walking skeleton" list.]
Is my machine isolated from everyone else's?
Yes — separate machine, separate filesystem, separate network identity. Your root is root on your machine and nowhere else, and nothing you install can reach another customer.