How Rekhu works

#The parts

Rekhu has a few parts that you meet in the same order every time you add a site or an app. Once you know them, every other page of these docs is about one of them.

• The account is your company on rekhu.com. It holds the credit, the people on your team, your clients, your projects and your library of templates and files.
• A project is one site or one app, with everything Rekhu knows about it.
• A key connects one site or app to its project. It is made on the project and shown once.
• The plugin or package runs on the site or app itself. It does the work there, with the tools of that platform.
• A chat is where you ask for work, in plain words.
• Credit pays for every step Rekhu takes.

#The account

The account is the company, not the person. Colleagues join it under Team, clients get their own sign-in under Clients, and the owner sees everything: projects, people, credit and invoices. See Team and Clients.

Account-wide settings live under Preferences: the language and tone Rekhu writes in, the limits it keeps on every site, knowledge and skills for every project, and where reports go.

#Projects

Make one project per site or app. A project keeps:

• its chats, one for each piece of work;
• its knowledge and skills, which Rekhu reads before every answer;
• its files, such as templates, notes and pictures;
• its schedules, jobs that run on their own;
• its activity, the log of every change on the site;
• its connection: the key, the tool switches and the backups.

The project belongs to the team. A chat inside it belongs to the person who opened it until they share it. See Projects and chats.

#Project types

When you make a project, you choose what it is. That decides what you install.

A Laravel app and an Odoo database can have both: Rekhu Builder for you, and Rekhu Assistant for the people who use the app. Each has its own key. See Rekhu Assistant.

#Keys

A key belongs to one project and one site. The plugin or package sends it with every call, so the account knows which site asks and can meter the work per site. Your usage shows every site on its own line for that reason.

A key is shown once, when it is made. If it is lost, make a new one: the old one stops working. See Sites and keys.

#The plugin or package

The plugin or package is Rekhu's hand on the site. It knows the platform it runs on: on WordPress it builds Elementor pages, builds forms, installs plugins and reads the site's health; on Laravel it reads routes, models, logs and tests. It runs only the tools the project allows. The WordPress plugin updates itself from the account.

Your files live in the account, not on the site. When Rekhu needs a template or a picture, the site fetches it from the project's files or the library.

#Chats

You give work in a chat, the way you would to a colleague:

Change the opening hours on the contact page to Monday to Friday, 9 to 17.

Rekhu reads the project's knowledge and the site, uses the tools it needs, checks what it did, and answers with what changed. New pages and articles are made as drafts. A change to a page your visitors already see is asked first, saved beforehand and checked afterwards. See Changes to live pages.

#Credit

The account has one prepaid credit for every product and every site. Each step Rekhu takes is paid from it, at the price shown in the account. There is no subscription, and credit you top up does not expire. See Credit and usage.

#How one piece of work goes

1. You ask. A message in a project's chat, or a schedule whose moment came.
2. Rekhu reads. The account's and the project's knowledge, the skills that fit the message, and the site as it is now.
3. Rekhu works on the site. Through the plugin or package, with the tools the project allows.
4. Rekhu checks. It goes through the steps of the skill it followed, and opens any live page it changed to check it.
5. You see the result. The answer says what changed, drafts have a preview link, and the Activity tab keeps the log.

#Next

• Sites and keys: what a key may do, and how to connect or disconnect a site.
• Projects and chats: working in a project day to day.