Start here

Getting started

What Yavaren does for your organisation and the order to set it up in.

Yavaren gives your organisation on-demand AI delivery engineers, called Tulaian. You connect a work tracker and your repositories, request engineers, and hand over stories. Each story comes back as a draft pull request that a person in your team reviews and merges. Yavaren never merges and never pushes to your main branch. For a new product, it deploys only by starting your own pipeline, and only after a person you named approves.

Finding your way

The bar at the top has the pages you use every day; Quality, Help and Organisation open the rest. To go straight to any page, press ⌘K (Mac) or Ctrl+K, or choose the search icon, and type part of its name. Each page has a (?) next to its title: it says what the page is for and what to do next. The bell at the top right lists your notifications, such as a pull request that waits for your review; choose one to open it.

The order to set things up in

The Getting started page (in Help) walks you through these steps in order. It shows how far you are, why each step is there, and a button that opens the exact place it is done. A new organisation's first admin starts there.

1. Your setup: choose how Yavaren runs for you. Yavaren cloud is recommended: nothing to install, ready in minutes. If your code and tokens must stay in your own network, choose hybrid runners or on-prem instead (see Cloud, on-prem and hybrid compared): Yavaren sets it up with you, and your work can start in Yavaren cloud meanwhile. You can change your choice later.
2. Connections: connect your work tracker and your code (see Connecting trackers and repositories). If you named them when you asked for access, the form starts with them.
3. Tokens: paste the token of each connection once (see Tokens: set once, never shown again).
4. Payment, where your organisation needs it.
5. Engineers: request the engineers you need (see Requesting engineers).
6. Project: which tracker, which repositories, which engineers (see Projects, pickup and governance). The tracker no project uses yet, and the repository that goes with it, are chosen for you.
7. Runners: in Yavaren cloud they are ready. In your own network you install them once (see Cloud, on-prem and hybrid compared).
8. First story: hand over a story, or turn on automatic pickup so approved stories are started for you.
9. First review: review the draft pull request that comes back (see Reviewing draft pull requests).
10. Your team (optional): invite the people who review pull requests and approve plans.

A step Yavaren cannot check from here, such as tokens kept in your own vault, is marked Check yourself and says how to check it.

You are not asked the same thing twice

• A new connection starts from what your earlier connections already say. For example, Azure Repos takes the organisation, project and token name of your Azure Boards connection. A second Jira project takes the site and sign-in, and another repository on the same host takes the owner and token name. Change anything that differs.
• On a connection you already have, Add another like this opens the form filled in from it. After a tracker, Also connect offers the code host of the same account.
• The connection name is optional: it is named after what it connects.
• A project starts with the tracker and repository that belong together, is named after the tracker's project, and suggests the stack of your last project. Requesting engineers chooses the code agent and licence you connected.

For the admins of your organisation.

For the admins of your organisation

As an admin you can also invite people, issue API keys, see the activity log and read your statements. These are under People, billing, activity in the navigation.