# Desde > A local editor that turns clicks on your running prototype into real source > edits, and a self-hosted viewer that wraps a built prototype in async review. Desde is pre-release and runs from a source checkout; nothing is published to a package registry yet. It supports Vue 3 and React projects built with Vite. Every page below is also available as raw markdown by replacing the trailing slash with `.md` — for example `/docs/concepts/branch-mode.md`. ## Overview - [What is Desde?](https://desde.design/docs.md): Desde is two apps for runnable prototypes. A local editor that changes real source code, and a self-hosted app for review. ## Get started - [Editor on your Mac](https://desde.design/docs/quickstart/editor.md): Download the Editor, open a prototype, and change a real component in a few minutes. - [Try the Viewer](https://desde.design/docs/quickstart/viewer.md): One command gets you a running Viewer with a demo prototype in it. Open it, leave a comment, see what your team would see. - [Editor and Viewer together](https://desde.design/docs/quickstart/both.md): Connect a prototype you are authoring in the Editor to a Viewer project, so comments are shared between them. ## Editor guide - [A tour of the Editor](https://desde.design/docs/editor/tour.md): A tour of the Editor screen: the live prototype, the four-tab right rail, the header controls, and the tool picker that decides what a click does. - [Select and inspect](https://desde.design/docs/editor/select-and-inspect.md): Click something in your prototype, then read what it is, its options, and where its style really comes from. - [Making changes](https://desde.design/docs/editor/editing.md): Change the words, the variant, the spacing or the structure of anything on screen. Every change lands in your real source, ready to commit. - [Ask the AI](https://desde.design/docs/editor/chat.md): Describe a change in words and the AI makes it in your source, with the prototype in view. - [Comments on the prototype](https://desde.design/docs/editor/annotations.md): Leave a comment pinned to anything in the prototype, reply, resolve, and hand it to the AI to fix. - [Commit, branch and push](https://desde.design/docs/editor/git.md): Desde writes straight to your files. How to undo, commit a checkpoint, work on a branch, publish it, and push it to GitHub. - [Updating the Editor](https://desde.design/docs/editor/updating.md): The Editor keeps itself up to date. What it does on its own, what it asks you first, and how to check by hand. - [When Desde says no](https://desde.design/docs/editor/limits.md): What a refusal means, why it happens, and what to try instead: the short version of every case you're likely to hit. ## Viewer guide - [Deploy the Viewer](https://desde.design/docs/viewer/deploy.md): Put the Viewer somewhere your team can reach it. Run the container, give it a stable address, and keep its data on a disk you back up. - [Where to run it](https://desde.design/docs/viewer/deploy/where-to-run-it.md): The Viewer ships as a container. Hand it to a host that runs containers, attach a disk, and you are done. This page names the hosts that work, the settings to fill in, and the ones that cannot run it. - [Where prototypes are served](https://desde.design/docs/viewer/deploy/prototype-addresses.md): Each prototype should get its own address. On your own machine this happens with no setup. On a real deployment, one wildcard DNS record and certificate does it; this page is the detail, and the fallbacks when you cannot. - [HTTPS and a reverse proxy](https://desde.design/docs/viewer/deploy/reverse-proxy.md): The Viewer speaks plain HTTP. Put a proxy that terminates TLS in front of it, and set the two values that keep cookies and rate limiting correct behind it. - [Build the image yourself](https://desde.design/docs/viewer/deploy/build-the-image.md): Only if you changed the source or must build images in-house. Two things about the Dockerfile will bite you if you skip them. - [Run without Docker](https://desde.design/docs/viewer/deploy/without-docker.md): A systemd unit that runs the Viewer from a checkout, the four settings that unit gets wrong by default, and how to update it later. - [Backups and disk space](https://desde.design/docs/viewer/deploy/backups.md): What to copy so a backup actually restores, and the one thing nothing cleans up: every build you ever ran stays on disk. - [Upgrading](https://desde.design/docs/viewer/deploy/upgrading.md): Replace the container with a newer image. Everything you keep is in the data folder, and the new version picks it up where the old one left off. Take a backup first: migrations only go forward. - [The GitHub App](https://desde.design/docs/viewer/github-app.md): What the Viewer's GitHub App does, where its credentials live, and how to recover a deployment that can no longer connect to it. - [Deploy a prototype](https://desde.design/docs/viewer/deploy-a-prototype.md): Connect a GitHub repository or upload a build, set the build commands, and get a link your team can review. - [Email server](https://desde.design/docs/viewer/email.md): Connect an SMTP server so the Viewer can send comment mentions, sign-in links, and invites, with settings for common providers. - [Reviewing a prototype](https://desde.design/docs/viewer/reviewing.md): Open a deployed prototype, pin comments to elements, reply, mention teammates, and resolve threads. - [Builds](https://desde.design/docs/viewer/builds.md): Deploy a prototype, watch the build log, and read what a failed build is telling you. - [Members and tokens](https://desde.design/docs/viewer/members-and-tokens.md): Instance roles, how sign-in and invites work, per-project access, why a denied read looks like a 404, and the dsv_ machine tokens that scripts and the Editor use. - [Securing your Viewer](https://desde.design/docs/viewer/security.md): Who can get in, what each person can reach, and where on your network to run it. - [Serving prototypes](https://desde.design/docs/viewer/serving.md): Where a deployed prototype is served from, why some apps show their own 404 there, and the two fixes that make a build load everywhere. ## How Desde works - [How a click becomes a change](https://desde.design/docs/concepts/how-it-works.md): The short version of what Desde does: it runs your real prototype, knows where everything came from, and writes changes straight into your source. - [Why most changes are instant](https://desde.design/docs/concepts/deterministic-editing.md): Most edits in Desde never touch an AI model, which is why they are instant, exact, and never invented. - [Your design system, understood](https://desde.design/docs/concepts/design-system-grounding.md): Desde reads your component library automatically, so an edit uses your components' real options instead of a one-off override. - [Glossary](https://desde.design/docs/concepts/glossary.md): Plain definitions for the words Desde uses in its screens and in these docs. ## For engineers - [Run the Editor from a checkout](https://desde.design/docs/reference/run-from-a-checkout.md): The command-line path: clone the Desde repository, build the Editor's interface, and start it against a prototype. - [Attach mode](https://desde.design/docs/reference/attach-mode.md): Run the Editor against a dev server it does not own. When you need it, what you add to your own config, and why the stamper must never reach a production build. - [CLI reference](https://desde.design/docs/reference/cli.md): Every command, flag, default and exit code of the desde command line tool, as the argument parser actually reads them. - [Editor configuration](https://desde.design/docs/reference/editor-config.md): The two Editor config files, which keys belong in each, what every key defaults to, and why a key in the wrong file does nothing at all. - [Viewer configuration](https://desde.design/docs/reference/viewer-config.md): Every environment variable the Viewer reads, with its default, its effect, and the three groups that are all-or-nothing at boot. - [Viewer HTTP API](https://desde.design/docs/reference/api.md): Every route under /api/v1, what it does, what credential it needs, and curl examples for the calls a self-hoster actually makes. - [Troubleshooting](https://desde.design/docs/reference/troubleshooting.md): Symptoms you will actually see from the Editor and the Viewer, what causes each one, and what to do about it. - [Technical glossary](https://desde.design/docs/reference/glossary.md): Terms from the Editor's and Viewer's internals, for engineers. ## Legal - [Privacy policy](https://desde.design/docs/legal/privacy.md): What happens to your data on this website, in the Editor, on a self-hosted Viewer, and on the public demo. In plain terms.