Publish your app

While you build, you try your app in the preview. Publishing puts a separate copy of it online, at its own address, for the people who will use it. It stays up while you keep building.

Publish for the first time#

1. 1 Press Publish in the top bar.
2. 2 Crisp runs a security check on your app first. See The security check. If it finds a critical problem, you fix it before you can publish.
3. 3 Choose whether to tick Start with my preview's data. If you tick it, the records you added while trying the app are copied into the live app, once. If you do not, your live app starts empty.
4. 4 Press Publish. You see the progress, for example Building your app and Starting the new version. You can keep working while this runs.
5. 5 When you see Your app is live, use Copy address or Open in a new tab.

Once your app is live, the top bar shows a Live label with its address and a copy button. On a phone, find them in the More menu.

Search readiness#

Right after your app goes live, Crisp opens it the way a search engine does and shows a short Search readiness summary in the Publish popover. It checks six basics: search results show your app's name and a short summary of it, search engines know your app's main address (so they do not list it twice), shared links show a title and a picture, search engines can find all your pages, and search engines know which pages to skip. The technical names sit behind Details.

If something is missing, press Fix it. Crisp asks the AI to fix exactly those things, then you publish again to check. When you use your own domain, your app's main address and its list of pages use your domain.

Your live app has its own data#

Your live app keeps its own data in its own database, created by the people who use it. The data in your preview is separate. Publishing a new version never replaces or copies the live data.

The only time data is copied is the first publish, and only if you tick Start with my preview's data. After that, nothing you do in the preview changes the live data.

Publish an update#

Keep changing your app in the chat as usual. The people using your live app see the version you published, unchanged. When you are happy with your changes, press Publish, then Publish again. The popover shows when you last published.

If the new version stores its data in a new way, for example with a new detail on each record, Crisp updates the live database first, before anyone sees the new version. If that update fails, nothing changes: the version that was live stays live, and the message says what went wrong. Press Fix with Crisp to ask Crisp to fix it, then publish again.

Go back to the previous version#

If an update causes a problem, press Publish, then Previous version, and confirm with Go back. The version you published before this one goes live again. It goes back one version, and appears only when there is an earlier version to go back to.

Going back changes the app, not its data. Your live data stays as it is now. If the earlier version was made before a change to how the data is stored, Crisp warns you that parts of it may not work with the data as it is now. To bring the data back to an earlier moment, see below.

If publishing fails, the version that was live before stays live. The message says what went wrong. Check that the app works in the preview, then press Try again.

Download or go back: your live data#

Once your app is live, press Publish to find Your live data.

• Download a copy saves all your live data as one file. It is SQL, which any PostgreSQL database can load. Nothing is kept on Crisp after the download.
• Go back to an earlier moment (coming soon) brings your live data back to how it was at a date and time you choose, as far back as four weeks (or your first publish, if that is later). Use it after a mistake, such as records deleted by accident. Anything saved after that moment is gone from your live app. Your code and your preview are not affected.

Going back keeps the data as it was just before, until the next time you go back, so a mistake here can be undone. Write to us if you need that.

Your live data is saved all the time and copied every day, so it is safe if a computer it runs on fails. At most the last minute of changes could be lost in that case.

When many people use your app#

Your live app runs more copies of itself when many people use it at once, and fewer when they leave. When nobody uses it, it sleeps and costs nothing to run; the first visit after a quiet time takes a moment longer while it wakes. The most copies that run at once depend on your plan: Free 4, Pro 10, Max 20.

How many apps you can publish#

Each plan includes a number of published apps at the same time: Free 1, Pro 10, Max 50. Publishing an app that is already live again never counts twice. See Plans.

Use your own domain#

On the Pro and Max plans, you can open your published app at a domain you own, such as example.com or shop.example.com. See Use your own domain.

Delete a published app#

Deleting the project deletes its published app too. The address stops working, and all the data saved in the app is deleted. Because this cannot be undone, Crisp asks you to type the project name first. See Projects.