FAQs

Yorki is an AI app builder. You describe an app in your own words, and Yorki writes the code, runs it in a live preview and publishes it at its own web address. See How Yorki works.

No. You describe what you want and ask for changes in plain language. If you do code, you can read every file and export the project.

Websites, booking and membership sites, tools for you or your team, personal apps, and interactive things such as games, quizzes and drawing tools. See What you can build.

Yorki builds mobile-friendly web apps that run in the browser on any phone and can be added to the home screen. It does not produce apps for the App Store or Play Store.

Sign up with your email or Google and answer two short questions. Access is approved by hand during the alpha, usually the same day, and you get an email when you are in. See Your account.

It depends on the size of the app. A first build takes longer than a small change. The chat shows every step while it runs, and the preview appears as soon as the first pages are ready.

Build changes your app. Chat answers questions without changing anything. Plan writes a complete plan to review before building. See Build, Chat and Plan.

A running build cannot be stopped, but it never costs anything if it does not deliver. Requests you send while it runs wait in a queue, where you can reorder or cancel them.

Open the version history from the icon at the top of the chat and restore an earlier version. Restoring is free and nothing is deleted. See Versions and restoring.

Yes. Ask for it in Build mode, such as "Switch to a dark theme", or use Edit in the preview for small changes like a heading's size. See Making changes.

You can read every file in the Code view. Saving changes by hand is coming soon. Until then, ask for the change in the chat. See Code and export.

Yes. Yorki keeps project notes that every request reads, and you can write a specification with rules that always apply. See Project notes and specification.

The backend Yorki adds to your app: a database for records, storage for uploaded files and user accounts with sign-in. See Turn on cloud.

No. Once enabled, cloud stays on for the project.

They are two separate clouds. The first time you publish, the preview's data is copied to the published app, without test accounts. After that each keeps its own data, and publishing updates only the published cloud's structure.

Yes. Under Settings, Cloud, Sign-up you can allow anyone with the link, or only email addresses you list or keep in one of your app's tables. See Who can create an account.

Yes, once you add your own Google sign-in keys under Settings, Cloud, Sign-in. See Sign-in for your users.

250 MB of records and 10 GB of uploaded files, each upload up to 25 MB. You are told from 80 %; at the limit your app keeps working and can be read, but new data is not saved until you free space. See Cloud.

Yes. Published apps' clouds are backed up every night, and a backup is taken before any update that changes live data.

On its own address ending in yorki.app, such as my-studio.yorki.app, from the moment you publish. See Publish your app.

Not yet. Custom domains are coming later in the alpha.

No. The address is fixed at the first publish and stays yours, even while the app is offline. Choose it with care.

Open the publish dialog and choose Unpublish this app. The address and the data stay yours, and publishing again brings the app back.

No. Every published app shows a small Built with Yorki badge in the bottom-right corner, linking to Yorki. Visitors can close it, and it comes back the next time the page loads. It is added when you publish, so the preview does not show it.

Yorki collects them under Settings, Errors and emails you about new ones, at most once an hour. It can also prepare fixes for you. See Errors and automatic fixes.

Yes, during the alpha. Every tester gets a monthly allowance of 100 credits. Paid plans come later, and testers hear about them first.

The unit Yorki counts its work in. Each request is made of AI calls. A call such as writing code or generating an image costs 1 credit; a light call such as a question, the project notes or a Chat reply costs half a credit, and the design review half a credit per page it looks at. See Credits.

No. A request that fails, is stopped or is refused costs nothing.

On the 1st of each month at 00:00 UTC. Unused credits do not carry over.

You do. Your apps and their code are yours, and you can export them at any time. See the terms of use.

No. Yorki does not train AI models on your content, and only works with AI providers that do not train on it either. See the privacy policy.

Write to [email protected] from the email address on your account. You can delete single projects yourself under Settings, General.

Write to [email protected], or use Report a problem at the bottom of the app's sidebar, which can include a screenshot. A person reads every message and replies by email. See the support page.

The name of your project, what you did, what you expected and what happened instead. A screenshot helps. For a published app, include its address.

Press Fix it on the notice above the composer, or describe what you were doing. The error details travel with your next message either way. See When something goes wrong.

Use Forgot password? on the sign-in page to choose a new password. If you signed up with Google, use Continue with Google. If you are still stuck, write to [email protected] from the email address on your account.

Credits reset on the 1st of each month. If you need more before then, write to [email protected]. See Credits.

The email Yorki sent you explains why. Your project and its data are unchanged. If you think it is a mistake, write to [email protected]. See report abuse.

Write to [email protected]. Every suggestion is read, and the ones that come up often shape what comes next.