Concepts

A short tour of the nouns. Each links to the page that covers it in depth.

Project

The unit of everything. A project is a set of files (the app), a chat history, a version history, a private database, and at most one running sandbox and one live deployment. Projects are private to the account that owns them.

Version

Every accepted change bumps the project's version. Versions are immutable snapshots of all files; you can revert to any of them from the builder. Manual edits you save in the editor also create versions.

Change set

What the model proposes in response to a prompt: one or more file operations (create, update, delete), each shown as a diff. A change set is pending until you act on it. Accepting writes it to the project (and the running sandbox); rejecting discards it. You can accept some files and reject others.

Sandbox

The isolated container that runs your app's dev server for the preview. One per project, started on demand, stopped automatically after 30 minutes without activity. Sandboxes run under gVisor with dropped capabilities and hard CPU, memory and process limits — see Isolation.

Preview

Your app, as served by the sandbox, at https://preview--<slug>.apps.qyant.dev. Only the project owner (signed in) can open it. Hot reload works, so accepted changes appear in a few seconds. See Live preview.

Deployment

A production build of a specific version, served publicly at https://<slug>.apps.qyant.dev. Deploying again replaces the previous deployment with a brief overlap, never a gap. See Deploy.

Database

Each project has its own Postgres database and its own role. The connection string is placed in the project's .env as DATABASE_URL, and the same database serves both preview and deployment. See Database.

Credits

One credit is one AI request (one prompt you send). Plans include a monthly number of credits and a monthly AI allowance; both reset on the first of the month. See Plans & credits.

Model and thinking level

Which model answers, and how much it reasons before answering. Both are per-request choices in the builder. See Models & thinking.

Slug

The URL-safe name derived from your project name, used in preview and deployment hostnames. Slugs are unique across all of Qyant and permanent for the life of the project.