Getting started

Kedalia builds a web application for your team from a conversation, then puts it online. This page follows a first application, from its name to its first publication.

On this page

Create the application

In “Applications”, click “New application”, at the top right of the list. The page that opens shows “Start from”: “Start from scratch” or one of the templates, described below. Click the one you want: the rest of the form opens right under it, and a second click on the same one closes it. Give a short, meaningful name, with capitals, spaces and accents if you like, for example “Staff certificates”. The application's address is drawn from it and shows under the field (staff-certificates); the name is the one the application shows. Click “Create application”. As long as your organisation has no application, this form shows directly on the “Applications” page. If someone on your team creates an application while you are filling in this form, it stays in place with what you typed, and a line above it says who created it. On a phone, “Start from” is a list: each template has its screenshot, and “View” opens it full size; the form opens right under the one you tap.

When you start from scratch, “Technology” picks the application's base, above the name: one of the technologies offered, each with what it is good for. None is ticked in advance: “Create application” without a technology shows “Choose a technology.” under the list, and nothing is created. A Next.js application publishes a public home page from its creation, and the choice says so. A template brings its own technology: “Technology” does not show.

The creation conversation opens at once. Within a minute or two, the application is “Live” at its address, which “Open” opens and the icon next to it copies: it already handles accounts, sign-in and administration, nothing more. Its home page invites you to describe your idea to the assistant, “Your turn!”, until your first request.

Start from a template

A template is an application already built with Kedalia for a common need: sales follow-up, expense reports, an equipment inventory… Pick one under “Start from”, give a name, then click “Use this template”.

Your application starts with the template's code, never with its data: its database is empty, only your account is in it. Creating it takes a few minutes, the time to build and test it; the conversation opens as soon as it is ready. At first it carries the template's name, in its pages and its e-mails: the assistant offers to change it.

The conversation starts with what the application already does, and where putting it online stands. Open the preview to go through its pages: they are empty, so add a few rows to try it out; the online application will know nothing of them. Then tell the assistant what is different for you: the roles, the information to keep, the approval steps, the words of your trade. No need to describe what it already does. The rest is the same as a creation: the plan, its execution, the preview, then “Publish”.

A later change to the template does not touch your application: it only applies to the applications created after it.

“Catalogue and quotes” is a template of its own, built on Next.js: the product or service pages you publish, with their photo, are public pages, open to anyone without an account and found by search engines, each with a quote request form. An unpublished page and the rest of the application, the requests received included, need a sign-in.

Describe what you need

In the message box, write what the application is for, who will use it and what it must manage, then click “Send”. The assistant sums up what it understood and asks its questions, one at a time; answer them in plain words. For a description that hits the mark the first time, read Asking well.

Until its first publication, a line at the head of the conversation shows where the app stands — “Describe › Plan › Execute › Publish” — and says the next step, naming the button to click. It goes away once the app is published.

Request the plan, then execute it

Once the assistant has understood, click “Request the plan”. The plan arrives within a few minutes: what the application will do, what is left for later, and “How to check”. When the assistant made a choice of its own that you had not stated (a rule, a default value, a limit), a line “Decided without asking you” says so, at the end of what will change: read it. If it suits you, click “Execute the plan”.

The assistant then builds the application and tries it out itself; it reports in a few lines where it stands. For a first version, allow about ten minutes. You can close the page: the work goes on, and the result waits for you. The last message sums up what was done, followed by “Change saved, not published yet”: nothing has changed for the users yet.

Try it in the preview

Click “Preview”: the built application shows next to the conversation. It runs there with test data and a test account, not those of your live application, and opens already signed in with that account, an administrator. The “Test account” button gives its login and password, which the copy buttons pick up for you: to sign in again after signing out, or in an older application, which opens on its sign-in page. Signing in with your Kedalia account is not available in the preview.

The data you type in and the files you upload there, photos and documents, stay from one start of the preview to the next. A test version has its own.

On a large screen, the preview opens by itself with the conversation the first time you open an application or a test version. To keep it closed on that first opening, untick “Open the preview with the conversation” in “Account”. In the conversation, the ✕ at the end of its bar closes it, and the “Preview” tab on the right edge of the screen opens it again: that choice is remembered for this application or test version, in this browser, even after the page is loaded again.

While the assistant changes the application, a line under the preview's bar says so: the preview may change while it works, and it reloads when the assistant is done, if the application changed.

Above the preview, a bar like a browser's. Its icons give their name when you hover them: “Reload” refreshes it, “Open in a tab” shows it full size, and the page shown is written beside them. The tab it opens carries a badge in its bottom right corner saying it is not the live app; its cross hides it until the page is next loaded. On a large screen, “Computer width”, “Tablet width” and “Phone width” show the app at each of these sizes. “Point” picks out an element: click it in the preview, it goes into your message as a label, where the cursor was; write what should change right after it. Its cross, or Backspace, removes it. For a small touch-up, then click “Adjust directly”.

On a phone, the bar holds on one line: “Reload”, “Point”, “Full screen” and “…”, which gathers “Open in a tab”, “Test account”, “E-mails” and the test data notice. “Full screen” hides Kedalia's bar and the tabs: the application takes the whole screen under the preview's bar. To leave it, tap “Leave full screen”, use the phone's back gesture, or press Escape on a keyboard. An element picked with “Point” takes you back to the conversation, and reloading the page brings back the usual view.

In the conversation, the menu folds to its icons to make room for the preview; the button at the top left opens it again. To widen the conversation or the preview, drag the border between them, or reach it with Tab and use the arrow keys: Kedalia remembers the width on this browser.

The e-mails the application sends from the preview (sign-up, forgotten password, notifications) do not leave: they are kept beside it, under the “E-mails” button, with their count. Open one to see it as it will look, or as “Plain text”. “Send it to me” sends it to you alone, at your Kedalia account's address, to see how it renders in your mailbox: its subject starts with “[Preview]”, and its links only work inside the preview. “Delete” removes the open e-mail from the list, for you and the assistant alike. The assistant reads these e-mails too when it tries the application. One exception: a sending server saved in the e-mail settings of the preview's application really sends, to real recipients.

Publish

When the result suits you, click “Publish”. The number in brackets counts the saved changes waiting. Kedalia asks for confirmation: “Publish to the live application?”.

Publishing goes through “Preparing”, “Testing”, “Starting up” and then “Live”, in about two minutes; meanwhile, the site stays online on the previous version. If the tests fail, nothing changes online, and “Make the tests pass” asks the assistant to fix the application. The same button shows on the application's card in “Applications”: you stay on the list, and the card reads “The assistant is working” during the fix.

Sign in to your application

Open the application with “Open”, on its row of the Applications page, then click “Sign in with Kedalia”: you are signed in with your Kedalia account, with no other password. The live application starts with empty data: the preview's data is not there.

The application speaks English, French, Spanish and Polish. It starts in the language of your Kedalia account; each of its users picks their own on their account page, their e-mails included, and an administrator of the application changes its default language in its Settings, under “Language”. Before signing in, a language picker sits under the form. An application created before 3 November 2026 keeps its language: to translate it, ask the assistant, in its conversation.

Also choose a password of the application's own, on your account page: it is the one you will need if you ever export the application, since an exported copy has no sign-in with Kedalia. Your colleagues get their accounts from the application's user administration page.

The application's e-mails (welcome, forgotten password…) go out under its name, which also shows at the top of its pages and in the browser tab. For a clearer name, ask the assistant, in the application's conversation. The sending address does not change. “Rename”, in the “…” menu of its card in “Applications”, only renames the card, in your list.

In the list of applications

The “Applications” page shows one card per application. Next to its name, a coloured badge gives its state: “Up”, the step in progress with a spinning icon, or “Failed at …” in red. “The assistant is working” joins it while the assistant is busy: a click opens the conversation. “Paused” says it is stopped and no longer counts in your tier (see The subscription). Below comes the application's address; hover the ⓘ icon after it to see how to sign in. Then the date and time of its last activity and who created it (“Last activity on … at … · created by …”, the time alone on the same day).

During a creation or a publication, the card also shows the steps, “Preparing”, “Testing”, “Starting up” and “Live”; once the application is up, they are gone. After a failure, one sentence says what to do: “Click “Edit” and ask the assistant to fix this.” when the code failed, “Retry the creation from the « … » menu.” when the creation did.

On the card, “Open”, right of “Up”, shows the application in a new tab. On the Business tier, “Kanban” comes first and opens its board; a line parts it from the buttons that change the application. “Edit” opens its conversation with the assistant, and “Create a test version” prepares one. The “…” menu holds the rest: “Settings”, “Domains”, depending on your tier, “Rename”, “Download the code only”, “Export everything (code, history, data, guide)”, “Retry the creation” after a failed creation, and last “Delete…”, in red. Only the person who created the application and the organisation's administrators can delete it: for a colleague, “Delete…” is greyed out, with “Reserved for its author and the administrators”. The application's test versions are listed under its card (see Test versions).

Applications that need your attention, failed or suspended, come first in the list, then those in progress, then those that are up.

An application's pages

At the top of the screen, beside the application's name, tabs lead to its pages: “Conversation”, “Kanban” on the Business tier, “Domains” depending on your tier, and “Settings”. A click on its name goes back to its conversation.

“Settings” holds, in order:

  • Name: the application's name in your list (its address does not change); for a test version, its title.
  • Changes, for an administrator of your organisation: “Change only through a test version” (see Test versions).
  • Code: “Download the code only”, without the history or the data, and “Export everything”, with them (see Exporting).
  • Application AI, for an administrator of your organisation, depending on your tier: its switch and its monthly cap, as on the “Applications” tab of “AI usage”.
  • Delete, for its author and the organisation's administrators (greyed out for others, with the reason), and “Retry the creation” after a failed creation.

What next

After the first publication, this conversation changes the live app: on the next “Publish”, your users will see everything that changed in it, mistakes included. A red banner says so from the opening of each conversation, with the “Create a test version” button to try things safely first. For each new change, start with “New”, at the head of the conversation: the assistant starts afresh from the updated application.