Yorki

Turn on cloud

What cloud gives your app, when to turn it on, and what happens when you do.

Cloud is the backend Yorki can add to your app. It gives your app three things, with no setup:

  • Sign-ins: people can create accounts and sign in to your app.
  • Saved data: your app stores real records, such as orders, bookings and messages.
  • File uploads: photos and files, kept safely with your app.

Without cloud, an app can show information but cannot remember anything people enter. A form would forget what was typed as soon as the page reloads.

When you need it

Turn on cloud when your app should:

  • let people create an account or sign in;
  • save what people enter, such as bookings, orders, sign-ups or messages;
  • keep things across visits and devices, such as favourites or progress;
  • let people upload photos or files.

A brochure site or a portfolio without forms does not need it.

Turn it on

There are two ways:

  • Ask for it. When a request needs saved data, Yorki turns cloud on as part of the build. Before the first such build it asks who can do what.
  • Turn it on yourself. Open Settings, Cloud, Overview and press Enable cloud. Your next request can then use sign-ins and store real data.

If a build turned cloud on and the build did not work out, cloud goes back off with the rest of that request, unless your app was already published with it.

Two clouds: preview and published

Your app has two separate clouds:

  • The preview cloud is used by the preview while you build and test. Try things freely: test accounts and test records live here.
  • The published cloud is used by your live app. It starts the first time you publish with cloud on.

On that first publish, the data in your preview cloud is copied to the published cloud, so what you see in the preview is what your visitors see. Test accounts are left out. After that, each publish updates the structure of the published cloud, such as new tables or fields, and leaves its data alone.

What you can see and manage

When cloud is on, Settings, Cloud has these pages:

PageWhat it shows
OverviewThat cloud is on, and live counts of tables and users
TablesThe records your app stores, one table per kind. You can add, edit and delete rows, upload files, delete many rows at once, and export or import a table as CSV
UsersThe people who signed up, when they joined and whether their email is verified. You can verify someone, set a password, send a password reset email or delete a user
Who can do whatThe rules that decide who may read, add, change and remove records. See Who can do what
Sign-inEmail and password, and Google sign-in. See Sign-in for your users
Sign-upWhether anyone can create an account or only people you list. See Who can create an account
LogsThe requests your cloud handled. See Cloud logs and usage
UsageHow busy your cloud is and how much it stores
BackupsThe copies of your live app's data, and restoring one
ActivityThe changes made to your live app's data from these pages

Once your app is published, Tables, Users, Logs, Usage and Who can do what show your published cloud, with a Published / Preview switch at the top to look at the preview cloud instead. Before the app is published they show the preview cloud: people who sign up in your published app appear once it is published.

Your app's live data

Once your app is published, Tables and Users show the real accounts and records of your live app. You can look through them, search, change a row, upload or remove a file, mark someone as verified, set a password or send a password reset email, and delete one row or many.

  • Deleting many rows. Select the rows and press Delete selected. On the published cloud a safety copy of all your data is saved first; you can restore it under Backups.
  • The structure stays with your app. Tables and fields come from your app's code. To add a table or a field, ask Yorki in the chat; these pages change the data, not the structure.
  • Sign-up and other settings stay on their own pages (Sign-up, Sign-in).
  • When your cloud is full, new rows and uploads are refused here too. Deleting rows and removing files always works.
  • Your data stays yours. Yorki reads your app's data only to show it to you on these pages. It is never sent to an AI model.
  • Two-factor sign-in. These pages open your users' data, so we suggest you turn on two-factor authentication for your Yorki account (see Your account page).

Backups and restore

Backups lists the copies of your live app's data: one taken every night, a safety copy taken before you delete many rows or import a file (the newest three are kept), and copies Yorki takes before a change to your cloud.

To go back to a copy, press Restore next to it. Your live app's data goes back to that moment: changes made since then are lost, files removed since then may not come back, and your app is unavailable for a few seconds. Only copies taken after your app's last publish can be restored, so the data always matches the tables your app expects. The page shows when the restore has finished.

Backups cannot be downloaded: they hold your cloud's own keys. To take your data with you, use the downloads below.

Download or import data

  • Export CSV in a table downloads its rows as a CSV file (up to 50,000 rows). Files appear as their file names and linked rows as their ids.
  • Download all data under Settings, Export downloads every table as CSV files in one zip, from the published or the preview cloud (up to 50,000 rows per table and 200 MB in all; a larger download ends with a note saying where it stopped).
  • Import CSV in a table adds rows from a CSV file of up to 5 MB and 5,000 rows. The first row names the columns, and each must be a field of the table; files cannot be imported. On the published cloud a safety copy is saved first. Rows go in 50 at a time; if a group is refused, the import stops there and the rows before it stay.

Activity

Activity lists the last 100 changes made to your live app's data from these pages, newest first: edits, deletes, imports, exports, safety copies, restores and invitations, with the time. It never shows the data itself.

Looking after the published cloud

  • Backups. The published cloud is backed up every night. See Backups and restore.
  • Updates. Yorki keeps the cloud's software up to date for you. Overview shows "Cloud software: up to date", or when an update is scheduled. Updates run in a quiet hour, with a backup first.
  • Unpublishing. Taking your app offline stops its cloud but keeps the data. Publishing again brings it back.
  • Sign-in emails. The published cloud sends the account confirmation, password reset and email change emails from mail.yorki.app; people confirm their email before their first sign-in. The preview cloud sends none. See Sign-in emails. Once the app is published you can also invite people from Sign-up: Yorki creates their account and the cloud sends them a link to set their password (Invite someone). A cloud sends up to 200 sign-in emails a day; past that, sending pauses until Yorki looks at it.

Uploads in your app

File uploads in a Yorki app accept images and PDF files up to 5 MB by default. Ask Yorki if your app needs other types or larger files, up to 25 MB per file on your plan.

How much your cloud can store

Each cloud has room for 250 MB of records (the database) and 10 GB of uploaded files, with each upload up to 25 MB. The request log and the backups never count. Settings, Cloud, Usage shows how much is used.

  • From 80 % of either, a notice appears above the composer and you get an email.
  • When one is full, your app stays online and everything can still be read, but new records (or new uploads) are not saved. Delete what you no longer need; saving resumes on its own once you are below 95 %.
  • Your plan includes one cloud. A site without sign-in or saved data needs none. An extra cloud is $8.99 a month; contact support to add one.
Was this page helpful?

Last updated 12 October 2026