# Getting started with Vraelis

> **Historical. This product is retired.** This page describes the earlier browser-testing product and is kept only as history. Its service, API, console and accounts are closed: do not run the install commands or call the endpoints shown here.

Write one sentence about your deployed app, approve the plan, and read your first decision.

- **Outcome:** You have run one check on your live app and read its answer.
- **Does not do:** Vraelis checks what a browser can reach on a public address. It does not read your code, your database or a device's firmware.

Vraelis checks whether a deployed web app does what someone says it does. You write one sentence about what should work, a person approves the plan Vraelis writes from it, and a real browser tries it on the live app. The answer is Verified, Failed or Blocked, with the evidence. This guide takes you from an empty account to that first answer.

## 1. Name the deployed app

Give Vraelis the public https address where the app runs: production, staging or a preview deployment. For a connected device, that is the web control panel or dashboard that runs it. Localhost and private addresses are refused before anything runs. You confirm ownership of the app before a check can start.

## 2. Write what should work

One sentence: what a user can do, and what should be true afterwards. "A signed-in user can cancel their plan from Billing and then sees Cancelled" is a good claim. "Test the billing page" is not, because it names no outcome.

The same works for a connected device, through the web control panel that runs it: "After an operator presses Return home, the panel shows Landed, and still does after a reload." Vraelis checks what the panel reports. Reading the device itself, its firmware, sensors or telemetry, is next and not built yet.

## 3. Approve the plan

Vraelis turns the sentence into requirements and the browser steps that would prove them, and shows you both. Nothing runs until a person approves that exact plan. If no check could prove the claim, Vraelis says so and charges nothing.

## 4. Read the answer

Verified means the claim held on the live app. Failed means it did not, with what was expected, what was observed, and a repair prompt. Blocked means no decision could be reached, so none is claimed. Every answer carries its steps, screenshots, console errors and failed requests.

> **Four ways in.** The same check runs from the console, the CLI, CI through the API, and AI assistants over MCP. Start in whichever you already have open.

---

Vraelis documentation, Earlier references. https://docs.vraelis.com/getting-started