Skip to content
hyad

hyad

Ask your AI assistant to build something. It is live at your-app.hyad.app.

Static sites and SvelteKit apps over MCP: your assistant builds locally and uploads the output. Each app gets sign-in, a document database, env vars, versions with instant rollback and a private git repository. New apps are private. You describe the app in your own words. Your AI assistant writes it and hyad puts it online at its own web address. This site shows you each step and why it happens. New apps are private: only you can open them until you share them. Tell your AI assistant what you want. It makes the app and puts it online; it only asks you when a decision is yours, such as the name. Only you can open a new app until you share it.

Not a developer? Pick how much this site explainsChange how much this site explains

For you

Who is reading?

Pick the one that fits you best. The pages of this site follow it.

The pages follow your choice. It is kept only in this browser. If you create an account from here, hyad saves it as your setting. You can change it any time.

How it works

Three steps, one conversation Three steps

  1. Add the MCP server. Remote MCP over streamable HTTP, OAuth sign-in, no API key. In Claude Code:

    claude mcp add --transport http hyad https://mcp.hyad.app/mcp

    Add Hyad to your AI. Add Hyad once to Claude, ChatGPT or another assistant that lets you add a connector by its web address. You sign in and click Allow. Paste this web address into Claude or ChatGPT, sign in and click Allow.

    https://mcp.hyad.app/mcp

    Behind the curtain. This gives your assistant a few tools to work on hyad for you, with your account's rights and no more. You can disconnect it at any time in your account.

  2. Ask for an app. "Deploy a SvelteKit guestbook to hyad as guestbook, entries in the app database." The assistant reads hyad's guide, builds locally, pushes the source to the app's private repo and uploads the build output. hyad never builds.

    Ask for something. "Make a page for the book club with the next three dates, and put it on hyad as book-club."

    Behind the curtain. The assistant writes the code on its side, turns it into a finished website and sends that to hyad. It also saves the code in the app's own private storage place, so a later chat can carry on where this one stopped.

  3. Open it. Live at guestbook.hyad.app, private until you change its visibility. Every deploy is a version; rollback is instant.

    Open it. It is live at book-club.hyad.app. Only you can open it until you say who else may.

    Behind the curtain. hyad keeps the last 10 versions of every app. If a change goes wrong, say "go back to the previous version" and the old one is live again at once.

Your first deploy, step by step Your first app, step by step

Every app

What every app gets

Private
New apps are private. Visitors sign in with a hyad account and need access. Open an app to every signed-in account, or to everyone, when you want.
Sign-in
Visitors sign in with hyad. A SvelteKit app knows who is signed in and whether they are an admin of the app.
Database
A live database per app: document collections, realtime updates, per-user and public data, backups. Nothing to create, no API key.
Env vars
API keys and other secrets a SvelteKit app needs. You type the value on a hyad page; your assistant never sees it.
Versions
Every deploy is a new version. The last 10 are kept, and going back to one is instant.
Source
Every app has its own private git repository, so a later session picks up where the last one stopped.
Private
Only you can open a new app. When you want, open it to people with a hyad account, or to everyone.
Sign-in
Visitors can sign in, so the app knows who is using it.
Storage for its data
A place where the app keeps what people enter, such as sign-ups or scores, and shows changes as they happen. Nothing to set up. The app can keep what people enter, such as sign-ups or scores. Nothing to set up.
Secret settings
Passwords or keys for other services that the app needs, called env vars. You type them on a hyad page; your assistant never sees them. Passwords or keys the app needs. You type them on a hyad page; your assistant never sees them.
Earlier versions
Every change is kept as a version. The last 10 stay, and going back to one takes a moment.
Saved code
The app's code is saved in a private folder on GitHub (a repository). In a new chat, say "continue with" and the app's name, and the assistant carries on from there. The app's code is saved for you. In a new chat, say "continue with" and the app's name.

Access

Who can deploy Who can put apps online

Anyone can create an account. New accounts can deploy once an admin enables it; until then, hyad refuses to connect an AI client to the account. Anyone can create an account. An admin then lets your account put apps online; until that happens, connecting your assistant is refused. This keeps the test small while hyad is new. Anyone can create an account. An admin then lets your account put apps online; until then, connecting your assistant is refused.

hyad is in testing. Billing is not live yet: testers use it free. Plans and limits