Give your agent
a real machine.
You already pay for Claude Code, Codex or Antigravity. Right now it can write anything and deploy nothing. Point it at a Helstify machine and it gets a filesystem, a terminal, a domain and a database. You get an editor in the browser, open on the same files.
Try a name. See how it reads.
Type an idea and this shows you the shape of the shortlist your council would bring back.
Hosting has not changed since 2009. Your agent has.
Every host still sells the same thing: an empty machine and the login for it. That was a reasonable product while the only thing that could operate a server was a person.
An IP address, a root password, and good luck.
A URL. You are already looking at the files.
You SSH in. Everything happens at a prompt you have to know.
You ask in a sentence, or you edit the file yourself. Both work.
Runs on your laptop and cannot reach the machine.
Runs on the machine, with the terminal and the filesystem.
You copy the log out and paste it into a chat window.
It reads its own logs and tells you what it found.
You wire up a pipeline, then you maintain the pipeline.
It builds, checks the endpoint answers, then swaps the port.
You are the on-call engineer.
It restarts what fell over and leaves you the log to read.
Same hardware, same root, same Linux. The difference is who is holding the keyboard at two in the morning.
Runtimes, databases, self-hosted tools, voice and game servers. Ask for one by name and it lands on the machine you already pay for.
Five executives, a tester, and a chair who hears them out. They argue among themselves so you get one decision, not five opinions.
Nobody has to be awake at 3am. Agents watch what is running, restart what falls over, and leave the log open for you.
Jobs a business needs doing, like invoicing or taking bookings. Name one in a sentence and your council wires it up.
Open a tab.
It is all already there.
A file tree, a real editor and a terminal, pointed at the machine that is serving your site. Beside them, the agent working on the same files. No local checkout, no key to lose, nothing to install.
Your files, not a copy
The tree is the container's own filesystem. Save and it is live. There is no deploy step between the editor and the machine.
The agent is docked, not elsewhere
It reads the same files you have open. You can hand it the thing you are stuck on without describing it first.
You can always take over
Every line an agent writes is a line you can edit by hand, mid-build. It carries on from where you stopped.
You decide what it may do
without asking you.
Handing a machine to an agent is a real decision, so it is made with switches rather than a paragraph of reassurance. Turn one off and the council has to come back and ask. Changes apply to the next thing you say to it, not to some future session.
- Enforced, not requested
- The rows marked enforced are applied outside the model. It is not asked to behave; it is not given the tool.
- A ceiling on one message
- An agent can work for a long time on a single instruction, and that time bills to your AI plan. You set the limit.
- Revocable, and logged
- Take a permission back whenever you like. Everything done under it stays readable afterwards.
Your agent is idle right now.
It can write the whole thing and it has nowhere to put it. Give it a machine and watch the first build happen in front of you.
No card. Your code stays yours. Leave whenever.
Normally this is three bills, three logins and a lost weekend
See the full platform →Naming the thing
Before a line is written, your council puts names on the table, argues for the ones worth keeping, and lets you settle it. You never start at a blank page.
Learn more →Domains and DNS
Point a domain at the machine and then stop thinking about it. Your council sets the records, nameservers and certificates, and keeps them in order, so you never have to find out what any of them mean.
Learn more →The machine, and a way in
A whole server, not a slice of one: mail on your domain, your services, anything from the catalogue below. Plus the editor and the terminal above, so you are never locked out of your own box.
Learn more →90 things you can ask for by name
Nothing here is an add-on, and nothing here costs extra. It all runs on the machine your plan already includes, and the same council that runs everything else keeps an eye on it.
There is no order form and no one-click marketplace. You ask, the way you would ask a colleague: “put a Gitea and a Redis on this box”. Your council installs it, wires it up, and sends you back the address.
Idea → live
Monday a sentence,
Friday a business
- MON You describe the idea. It gets scored six ways, honestly, and that includes being told when the answer is no.
- TUE You settle on a name and get the domain pointed at the machine that will hold it.
- WED A real server exists, with your domain on it and mail arriving.
- THU Your own agent builds the site on the machine while you watch in the browser editor. You can change anything it writes, mid-build.
- FRI You stop driving. The council takes over the inbox, the DNS and the deployments, and reports back from one panel.
Helstify is new, so let us be straight about the chart: it draws the path we are describing. It is not a customer's real numbers. We would rather admit that than make one up.
See how it works →How it goes, in order
Full breakdown →01 Describe
Say what you want, in your own words. A whole business, or one piece of software you need somewhere to live.
02 Validate
Your council argues it out across six angles, tells you where it is weak, and decides what it needs to run on.
03 Name & Claim
Settle on a name you want to keep, and get the domain pointed at your machine.
04 Connect & Build
Plug in your Claude Code, Codex or Antigravity plan. It builds on your own server while you watch in the browser editor, and you can edit anything it writes.
05 Operate
They keep it alive: mail, updates, restarts, the 3am work. You decide what they may do without asking first.
One machine. Everything the business needs on it.
Each of these is named after the job, not after a product. You say what the business needs doing; your council works out what software does it, and puts that on your machine. It picks from the same list you can pick from yourself.
- PLATFORM & HOSTING
- 19
- RUNNING THE BUSINESS
- 15
- SELL & GET PAID
- 14
- MARKETING & GROWTH
- 14
- CONTENT & MEDIA
- 14
- CUSTOMERS & SUPPORT
- 13
- MONEY & PAPERWORK
- 12
- DATA & INSIGHT
- 12
- SECURITY & ACCESS
- 12
- PEOPLE & TEAM
- 11
- COMMUNICATION
- 10
You are already paying for most of this.
Not to us. To six different companies, on six different renewal dates, with six dashboards to log into when something goes wrong at the weekend.
One machine, one bill, one login. The database, the mailboxes, the backups and the monitoring are on it already, and so is the crew that runs them.
$ over a year, and five fewer things to remember to cancel.
The left-hand figures are typical list prices for each piece, kept deliberately on the low side. They are an illustration of a common stack, not a quote and not any particular company's pricing. The figure on the right is what this store charges.
Pick the plan that fits where you are
Every plan is a real machine, with a crew on it and the editor open in front of it. Paying more buys more of the council's time, more room for what you run, and more seats on the account. Everything listed above is on all three. There is no second invoice.
Starter
Your idea, built and live on the internet — and the council on hand to advise while you run it.
- One business, built and hosted
- Domain, DNS and TLS configured for you
- Real mailboxes on your own domain
- AI council in an advisory seat
- Community support
2 billing options available
Add to cartOperator
Hand over the parts you still do by hand — the domain, the inbox, the deployments — and let the council work on the server itself.
- Everything in Starter
- Council works directly on your server
- More room: larger container, higher limits
- Additional team seats
- Email support
2 billing options available
Add to cartStudio
For agencies and studios running a shelf of businesses with a team on the account.
- Everything in Operator
- The largest container we run
- Team seats with fine-grained permissions
- Priority support
2 billing options available
Add to cartBring your own AI plan
More about agents →Point your Claude Code plan at the box. It scaffolds, it builds, and then it keeps the site and backend running.
Bring the Codex subscription you already have and let it drive builds and the ongoing engineering.
Link Antigravity to run builds and hands-off operations on your own quota, at your own price.
The questions
people ask first
Contact the team →
A real server your AI coding agent can actually operate, with a browser editor open on the same files. You bring the Claude Code, Codex or Antigravity plan you already pay for; we provide the machine it runs on and the panel you watch it through.
Yes. Connect a GitHub repository and the container pushes and pulls like any other checkout, so you can work locally while the agent works on the machine against the same history. The browser editor is there for when you do not want to clone anything, not as the only way in.
Your own site and backend, and anything from the list further up this page: language runtimes, databases and caches, self-hosted tools like Gitea, Grafana and Uptime Kuma, and voice servers. You ask for one in ordinary words and your council sets it up.
Yes, and that is deliberate. We drive your plan on your behalf inside your container, with the permissions you set. You pay the AI company directly, at their price. We would rather not be a reseller standing between you and your own quota.
Your business runs in its own container, not alongside anyone else's. Secrets are encrypted, scoped to what needs them, and revocable. They are never written to logs, and every action an agent takes is recorded where you can read it back.
Within limits you set, yes. They work through tools we issue, which are rate-limited, and you can read what they sent or withdraw the permission whenever you like.
You take the domain, the code and the data with you. They were yours throughout, and there is no stage at which we hold them hostage.
On Starter, the community. On Operator, us over email. On Studio, us first, ahead of the queue.
Ten minutes, and something is on the internet.
No region to pick, no instance size to guess at, no support ticket to open before anything can start.
The timings describe a normal run rather than a guarantee. A big import or a slow upstream registrar will take longer, and the panel tells you which step it is on rather than showing you a spinner.
Say it once.
Watch it get built.
Connect the plan you already pay for. The first hour costs you nothing.