Guide
Your first deploy
Once your AI client is connected, a deploy is one request in a conversation. This is what to ask, what happens and what you get.
1. Ask
Say what you want and give it a name, the slug. For example:
Make a one-page site for the running club with the route and the start time,
and deploy it to hyad as running-club.A slug is lowercase letters, digits and single hyphens. The first deploy to a free slug makes you the app's owner. If you name no slug, the assistant picks one or asks.
The same works for a SvelteKit app with server code: "Make a guestbook as a SvelteKit app on hyad, with the entries in the app database."
2. What happens
The assistant reads hyad's guides for the kind of app, then writes the code in its own workspace.
It builds the app there and uploads the result. hyad never builds anything; it serves what was uploaded.
It commits the source to the app's own private git repository, so the next session can continue from there.
hyad makes the upload the app's first version and answers with its address.
3. Where it lives
The app is live at its own address:
https://running-club.hyad.appYour apps, their versions and their usage are listed under Apps in your account.
4. Private or public
New apps are private. To change that, tell your assistant, for example "make running-club public". It asks you before it opens an app.
| Visibility | Who can open the app |
|---|---|
private (new apps) | You, and the people who were granted access to it. |
signed-in | Anyone signed in with a verified hyad account. |
public | Anyone, without signing in. What most websites want. |
Access for individual people to a private app is granted by a hyad admin.
5. Visitors sign in
A visitor of a private or signed-in app is sent to the hyad sign-in and comes back to the app signed in. They need a hyad account; anyone can create one. A visitor without access to a private app is told so.
On a public app nobody has to sign in. The app can still offer sign-in, for example to let people write to its database.
6. Change it, or go back
Ask for a change. The next deploy is a new version that replaces the whole site.
The last 10 versions are kept. "Go back to the previous version of running-club" makes it live again at once, or use the app's page in your account.
Env vars and the database belong to the app, not to a version: going back keeps them.
Stopping an app takes it offline and keeps everything; starting brings it back. Deleting removes it for good, and the assistant asks you first.