# Your first journey

This takes about ten minutes and uses a website. Phones and APIs work the same way once their platform is set up (see [Android and iPhone apps](/docs/mobile-apps) and [APIs and load testing](/docs/api-testing)).

## 1. Sign up

Create an account at [bitassure.app](/signup) with Google, GitHub, or an email address and a password. Every new account starts with 50 free credits, which last 30 days. A website run costs 1 credit, so that is plenty to try everything here. No card is needed.

If you signed up with an email address, BitAssure asks you to confirm it the first time you buy credits: it sends you a link, and once you have opened it you carry on where you were.

To see a run before setting anything up, press **Try it on our demo shop** on the dashboard. It adds a sample project with a journey already recorded against a small shop of ours, runs it, and opens the result with its video and report. Demo runs are free (up to 20 a day) and stay off your dashboard. The demo is a website only and its address is fixed, so no phone app, API or other website can be added to it. You can practise recording on it, up to 3 journeys of 5 scenarios, but it cannot be scheduled. Your own app goes in a project of its own.

You can also skip recording by hand: **Record with AI** on a journey shows how to connect Claude or another AI assistant, which then records the journey from your description (see [AI assistants](/docs/mcp)).

## 2. Create a project and a platform

1. On **Projects**, press **New project** and name it after your product.
2. Inside the project, press **New platform** and choose **Web** as the platform.
3. In **Base URL**, enter the website's address, for example `https://shop.example.com`, and press **Create**. Every recording starts here.

## 3. Record a journey

1. On the platform, press **New journey** and name it after what it does, for example "Sign in".
2. Press **Create and open**. The recorder opens a real Chrome on our side and shows you the page.
3. Click anything highlighted on the screen to choose it. The panel beside it shows what you can do with it:
   - **Events** move you through the app: **Click it**, **Type a value**, **Choose an option** and so on. Each one you use becomes a step.
   - **This should be…** adds a check: **Is visible**, **Is enabled**, **Reads exactly…**, **Contains…** and more (see [Checks](/docs/checks)).
4. Walk to the screen you care about and add a check or two there. For example, after signing in, choose the account name and press **Is visible**.

## 4. Save the scenario

The **Scenario name** box, above the save buttons, already holds a suggestion such as "Verify Accounts", taken from the screen. Keep it or type your own. It is the heading this part of the report will have.

- **Save and continue** saves this scenario and lets you carry on to the next screen in the same journey.
- **Save and end** saves it and closes the recorder.

Nothing is written until you save. Ending without saving leaves the journey as it was.

## 5. Run it

On the journey's page, press **Run journey**. BitAssure opens a fresh browser, walks your steps, judges each check where you added it, and records a video. A short journey takes well under a minute.

The run page shows every check as a sentence that held or did not, with the video beside it. Press **Download report** for the PDF.

## 6. Make it run by itself

- On the journey's **Schedule** tab, add a schedule: hourly, daily, on weekdays or weekly, at a time in your own time zone. If a scheduled run starts failing, everyone who has asked for it gets an email, and another when it passes again. See [Running and scheduling](/docs/running).
- To run it from your pipeline after every release, create an API key and follow [Running from CI](/docs/ci).