Skip to content
Devora

Documentation

Everything you need to run Devora

From installing the desktop app to planning your first change — plus an honest, always-current view of what is connected.

Quick start

Devora is a desktop application. In short: download it, sign in, pick a model, and start asking questions about your project. Here is the full path from zero to your first AI-assisted change:

  1. Download and install Devora on a supported machine.
  2. Launch the app and sign in with your Devora account.
  3. Select an AI model from the models your account permits.
  4. Open a workspace folder, then ask, plan, or build.
  5. Review each proposed change and run your tests.

Every suggestion Devora makes is explicit and reviewable — you decide what reaches your code.

Installation

Installers are published on the download page with a stable version number, release notes, and a SHA-256 checksum so you can verify the file you downloaded. The packaged installer includes everything the app needs — you do not need to install a browser runtime or any other dependency first.

While the first public build is being finalized, the download page shows a “Coming soon” state instead of a placeholder download. We only ever publish installers through verified HTTPS release URLs on that page.

Account and sign-in

Your Devora account is the same on the website and in the desktop app — one account, one subscription, enforced device limits. Signing in on a new device enrolls it with your account; you can review enrolled devices any time from your dashboard.

Forgot your password? Use the password recovery page. For anything else account-related, contact support.

Ask, Plan, Build

Ask is for questions: “what does this function do?”, “where is auth handled?”, “why is this test failing?”. Ask reads the relevant parts of your workspace and answers in context.

Plan is for larger changes: describe the outcome you want, and Devora produces a structured, step-by-step plan — files involved, order of changes, and risks — before anything is modified.

Build executes an approved plan step by step, showing diffs as it goes. You can pause, adjust, or reject at any step, and nothing is committed without your explicit approval.

Model selection

Devora lets you choose between the AI models your account has permission to use. The list you see in the app is enforced by your account — it reflects your current plan and entitlements, and it updates automatically when either changes.

If a model appears unavailable, it is not part of your current plan or it is temporarily out of capacity. Check your subscription status for details.

Skills

Skills are named, reusable workflows: a repeatable set of steps Devora follows on command. Capture your project onboarding routine, a pre-release checklist, or a review process once, then invoke it in any workspace with a single instruction.

Skills live with your account, so the workflows you build travel with you across projects and machines.

Troubleshooting

Installer warnings: if SmartScreen warns about an unsigned build, verify the SHA-256 checksum published with the release before running it. Signing status per release is listed on the download page.

Sign-in issues: confirm your credentials work on the website first. If the app still cannot sign in, check your plan's device limit on the devices page, then contact support.

Anything else: the support form reaches the team directly — include your OS version and what you expected to happen.

Integration status

We keep this section truthful and current. It reflects what this website is actually connected to right now — the real Devora API, verified against the server source:

  • Live: real sign-in through PocketBase identities, device-bound sessions, the account overview with your enrolled devices, remote sign-out, per-device usage, service health, and the download page fed by the API’s client config.
  • Depends on configuration: sign-in and registration activate as soon as the website’s server key and session secret are set for the deployment (environment variables — see the deployment guide).
  • Pending upstream: billing and subscription state — the Devora API does not expose billing routes yet, and our payment provider is still in approval. Nothing is faked here in the meantime.
  • Pending release: desktop installers publish here first, with checksums and release notes, once the stable build is ready.

Questions about any of this? Tell us what you need and we will prioritize it.