Ship in minutes

Build and share a website in about 20 minutes

Describe what you want, let your coding agent build it, and get a link you can share with teammates who can open, use, and edit it with you.

Get started Browse examples

Your first site

From an idea to a shared link

Do one step at a time. Install once, describe what you want, paste the prompt into your coding agent, and come back for the link.

Install Simple Host

Give this request to the ChatGPT desktop app on Mac or Windows, Claude Code, Cursor, or another coding assistant. It will explain what it plans to install and ask you to approve before changing anything.

Every install option

Not sure if it's installed?

Paste this to your coding agent. It answers yes or no.

Do I have the Simple Host skills installed? Look in the folders you load skills from for simple-host, simple-host-builder, and fix-paths-for-subpath-hosting. Answer yes or no in one line. If yes, tell me the version. Do not install or change anything.

View the prompt

You do not need to read this. The prompt checks the released version and trust boundary before approval; existing installations use their verified updater.

Install the three Simple Host skills from {{SIMPLE_HOST_ORIGIN}}

Browser platform is unknown. Detect and verify the actual operating system and shell before continuing.

First check whether you can actually read and write files on my computer. If you cannot — an ordinary ChatGPT chat window cannot — then stop, do not guess, and do not work around it. Tell me plainly that this has to run in the ChatGPT desktop app's coding agent, the part that can open a folder and edit files, and that I can ask in Slack #simple-host-support if I cannot find it.

Work out my home folder using the shell you are actually in: $HOME on macOS or in PowerShell, %USERPROFILE% only in cmd. Install into exactly one folder:
  Claude Code            <home>/.claude/skills
  ChatGPT or Cursor      <home>/.agents/skills

1. Read {{SIMPLE_HOST_ORIGIN}}/skills/version as JSON. Download the /skills.zip it names, then check the file's size and SHA-256 against that manifest.
2. Copy the three folders (simple-host, simple-host-builder, fix-paths-for-subpath-hosting) straight into the skills folder, with no extra folder wrapped around them. Do not run anything out of the archive. Confirm all three SKILL.md files exist and none still says {{VERSION}}.
3. From the exact skills root you selected, directly read <selected-root>/simple-host/references/account-recovery.md completely. Do not rely on the newly copied skill being discoverable yet. Follow that file before account creation, including its existing-config check, exact-destination preflight, and single-call save-and-verify transaction. Ask me for my work email only when that workflow requires it.
4. Tell me my username, and that I may need a new chat or an app restart before the skills show up.

Before changing anything, tell me conversationally in one or two sentences that Simple Host will install its tools in the selected skills root and save publishing access in the resolved config path, then wait for one yes covering both. Still show and honor every approval required by the host, tool, sandbox, or operating system. If anything fails, say what happened without exposing credentials and tell me to ask in Slack #simple-host-support.

Describe what you want

Write it like you would to a colleague. Simple Host turns that one sentence into a detailed brief your coding agent can build from — you never write the technical prompt yourself.

What do you want to make?
If your site needs to remember things between visitors, Simple Host adds that to the brief for you.

Work email
Your email goes into the prompt so your agent can set up your account. It is remembered on this device for a day so you do not retype it, and is never sent to the AI, added to a URL, or included in analytics.
Let it work

Your agent will ask a few questions, then build the site. Which one are you using?
Find it and share it

When your agent finishes, it gives you a link. All your sites live here:

/sites/your-name/

This is where every site you publish will show up.

Share it to build together. Invite teammates as editors and they work on the same site — one link, one version history, and you can roll back any change. That is the point of publishing here rather than sending a file around.
See everything you can do

What you can make

Publish work people can act on

Simple Host is useful for the work between a document and a full product: quick to share, polished enough to use, and easy to update.

Plan

Make plans easier to follow

Publish project plans, launch checklists, dashboards, and research summaries as clear websites instead of another attachment.

Prototype

Turn an idea into something teammates can try

Share prototypes, workflow demos, and lightweight tools at a real link, then improve them as the conversation moves forward.

Coordinate

Keep a shared timeline up to date

Make an interactive Gantt chart where teammates can update dates, owners, dependencies, and progress from the published page.

Use the simple-host-builder skill to turn my project plan into an interactive shared Gantt chart. Let teammates update task dates, owners, dependencies, and status. Save only that project state with Simple Host's versioned shared state. Never store passwords, secrets, API keys, or personal data.

Shared site state is public and unauthenticated. Never save passwords, secrets, API keys, or personal data in it.

Made for shared work

One site, shared with editors

Invite trusted editors to the site you already published. Everyone works on the same canonical site while the owner keeps control of sharing, visibility, and deletion.

01The owner shares editing access.
02Editors update the same owner URL.
03Every publish joins one version history.

Good to know

A few first-time questions

Simple Host stays out of the way, but these details help before your first publish.

Where do I get help?

Ask in #simple-host-support on Slack. If your coding agent gets stuck installing or publishing, paste what it told you into the channel — that is usually enough to sort it out.

Are my sites public by default?

No. A new site is unlisted — it does not appear on the Showcase or in search until you choose to make it public. Anyone on your company network who has the direct link can still view it, so keep content internal either way.

What information can I put on a site?

Only information your company allows to be shared internally, plus anything that is already public. Do not host confidential material, personal data, or customer data. Every site requires sign-in, and a restricted site is visible only to the people on its viewer list, but treat anything you publish as visible to everyone in your company.

Can someone else change or overwrite my site?

No. Accounts come from your company sign-in, and only you, the members of your team, or an editor you added can change a site. Every deploy is backed up to S3 with the last five versions retained, so any change is one revert away, and access logs are available to security on request.

Is the shared data on my site private?

Each site gets a JSON store — that is what makes shared demos and trackers work. Writes are not authenticated today, so treat it as collaborative rather than protected, and never store passwords, secrets, or personal data in it. Every write is versioned with full history, so anything is one revert away.

What is Simple Host good for?

Prototypes, demos, internal tools, dashboards, and trackers — and as a canvas for AI-generated pages. It is static-only, so it is fast by construction and nothing runs server-side; up to 100 MB per site. Support and takedowns are best-effort through #simple-host-support, with no formal SLA.

Do I need to register first?

No. Your first publish request includes your work email, so the skill registers you and saves your API key locally as part of that same step.

Can I publish more than one website?

Yes. Each site gets its own shareable URL, and your assistant can list, update, inspect, or roll back the sites you own and the sites shared with you.

What if my existing site uses absolute paths?

Simple Host serves sites from a relative subpath. The deploy skill handles the right base-path build for supported frameworks and can fix plain HTML paths when needed.

What if the recommended installer is not compatible?

The install request falls back to the first-party ZIP, verifies its exact byte size and SHA-256, checks the archive, and installs all three skills into the one directory your assistant actually uses. The Install page also has manual steps.