Publish to the web

Publishing puts your app online, at an address anyone can open. It is free on every plan, takes seconds, and you can do it as often as you like.

Press Publish, at the top right of the editor, and choose Publish to web. The same menu has Publish to app stores, Export to GitHub and Export to GitLab; the last two are on a paid plan.

The button waits while a build is still running and while Setherion double-checks that the new version opens, so a version that crashes is never what goes online.

The address

Your website URL is offered from the name of the app, on setherion.app. The pencil changes it. Use lower-case letters, numbers and hyphens, up to 40 characters.

Save renames the app to that name. It does not check that the address is free: that happens when you press Continue. If another app already has the address, publishing stops with a message and you choose a different one. When the address comes from the app's name and is taken, Setherion adds a few characters to it by itself.

An address belongs to the first app that publishes to it, until that app is taken offline or deleted. If you change the address and publish, the app goes to the new address.

+ Add custom domain puts the app on a domain of your own, like coffeeshop.com, on a paid plan. Before the first publish it reads "Publish it first. You can connect a domain of your own right after." See Custom domains.

Visibility

Who may open the published app:

Workspace and Custom are on the Business plan, for apps on their setherion.app address, and an editor of the app can change them. The plan that counts is the one paying for the app. On any other plan the two choices show a Business label and open the upgrade offer.

An app on a domain of its own cannot be private yet, and a private app cannot be put on a domain of its own: make it public first. Going back to Public is always allowed.

What a visitor to a private app sees

Someone who opens the address is sent to a Setherion sign-in page. They sign in with their own Setherion account; there is no password for the app and no list of email addresses. If the account is allowed, the app opens and stays open on that browser for eight hours. If not, they see "You do not have access to this app" and are told who to ask: the workspace owner for Workspace, or the owner of the app for Custom.

With Custom, you add people with the faces at the top of the editor, the Share window. See Share one app. Changing the setting takes effect within seconds.

A private app is hidden from search engines, and its Agent integrations always need an account.

Security

The last security scan of the app, and what it found. Scan reads the code before it goes out, Scan again after a first scan, and the price in credits is on the button. When issues were found the button is View issues, and when nothing has changed since the last scan it says it is up to date. A scan never blocks a publish.

The switch under it scans by itself after each publish of changed code, at the same price each time. It is off until you turn it on, so nothing is spent without your say.

Whatever the scan says, a secret key written into the app's code is never published: the publish is refused, with the kind of key and the file and line it was found on, so a key cannot go online by mistake. Take it out of the code and add the service under Connectors instead.

Before it goes out

When something would not work once the app is online, the window says so in a row of its own, with Fix. For example, an app whose sign-in and saving use a Supabase that is not connected to it: Fix offers to connect it, or to move the app to Setherion's backend, which needs no setup.

Two checks run before that, on every build and change, without anything for you to do:

• A hidden test. The new version is opened out of sight and must paint and stay up. If it crashes, Setherion sends it back for repair up to three times, free of charge, and your screen keeps the previous version until one passes.
• A phone-width check. The home page is measured at the width of a phone. If something sticks out, a bar offers a request for the chat. Nothing is spent until you send it.

Continue

Continue publishes. In a few seconds the window says Your app is live! (or Your app is updated!, or Already up to date when nothing has changed since the last publish), with the address, Open, a button to copy the link, and one to connect a domain.

• Publishing again replaces what is online with what you have now. Nothing you have not published is visible to anyone but you. A browser may keep the old version for a moment: refresh the page hard.
• Each change in the chat gets a version card, and the newest one has Publish this version, so you always know which version goes online.
• If the security scan switch is on, the window checks the code after publishing and tells you how many issues it found.

Take it offline

To take the app down, open Manage, then Overview, then Take offline. The live site stops working at once and its address is freed for others. Publishing again brings the app back, and a custom domain has to be connected again. See Overview.