Apps

When you start a new project, Syndai builds it and puts it online for you. You do not pick a host or press a deploy button. When the change lands, the project goes live on syndai.app.

What gets hosted

Syndai reads your request and picks one of two shapes. It tells you which one in the first run.

• A website. Pages that anyone can open. No sign-in.
• An app. People sign in, and the data they add is saved.

Each later change to the project goes live when it lands, too.

The Apps page

Open Apps in the left rail of your workspace. It lists every site and app in the workspace. Each row shows:

• the link, and an Open button;
• whether it is a website or an app;
• its state, such as live, publishing, or failed;
• when it last changed, and the credits it used this month.

Open a row to manage it. You can see who has joined, change who can get in, read the waitlist, and turn auto-update on or off. Owners can also take an app offline with Unpublish. If a deploy fails, the row says why and gives you a Retry button.

Find the live link

When a run goes live, the run itself shows a line that says Live at, with the address and an Open button. The run's Receipt tab has the same link. You can always come back to it from the Apps page.

Repositories that host themselves

Some repositories already deploy themselves, for example from GitHub Actions to their own server. Syndai does not take that over. It merges the change, if you let it. Then it waits for your deploy and links the result on the run.

Two things make this work well.

Tell GitHub your live address. Add a url to the production environment in your deploy workflow:

environment:
  name: production
  url: https://www.example.com

Without it, Syndai can see that the deploy ran, but not where. The run says so and offers a follow-up run that adds the line for you.

Protect your main branch first. Turn on required checks for main before you let Syndai merge on its own. With no required checks, Syndai only has its own checks and a short wait to go on.

Syndai never rolls back a site it does not run. If your live page looks wrong after a change, the run stops and shows you a Revert button. You choose. If your site blocks bots or asks for a challenge, Syndai treats that as "can't tell" and does not count it as a failure.

For developers and agents

You can do all of this without the portal. The API lists your apps, returns the live link on each run, and sends a coding.run.land_changed webhook when a change goes live, is held, fails, or is rolled back. Agents can do the same through the Syndai MCP server with an API key, and its list_apps tool finds an app to change next. See the API reference and the developers page for the details.