Frequently asked questions

Do I need to know how to code?

No. The assistant asks its questions and presents a plan in plain language before writing a single line of code. To start well: Getting started and Asking well.

Who owns the code?

You do, along with its database: the Export button hands you everything whenever you wish. See Exporting.

Can Kedalia take over an existing application?

Yes, after a study of the application and on a quote. Its code can stay on GitHub, or Kedalia hosts it with its data and its domain name: both ways are described on the website. Contact us with its form to get a quote.

Why no credits?

So that your budget stays predictable. With credits, every request made to the assistant is charged; with Kedalia, the price of your tier stays the same from one month to the next.

What if I use the assistant a lot?

The use of the assistant included in your tier renews automatically. When it runs out, the conversation's gauge shows the time at which it becomes available again, and no overage is ever charged. If your needs call for it, you can ask us for a higher tier. The details: Assistant usage.

What if the application does not work as expected?

Report it in the same conversation: the assistant fixes it, the tests run again, then the new version goes online.

Can I close the page while the assistant works?

Yes. The plan, the implementation and the deployment carry on without you: the conversation reminds you, “You can close this page — the work carries on; come back here later.” When you come back, the result is waiting in the conversation.

While it works, “Send” stays greyed out: you can prepare your next message in the message box, and send it once it has finished. To interrupt it, click “Stop”, next to it.

Can two colleagues work on the same application?

Yes. Each has their own conversation with the assistant, but both change the same application: “Deploy” puts online every saved change, whichever conversation made it. However, the application is built by only one conversation at a time: while the assistant implements a colleague's plan, your request may be refused with “The application is busy with another operation. Try again in a moment.” Wait for their implementation to finish, then send it again.

To work each on your own side without getting in each other's way, use “Create a test version”: each test version has its own address and its own conversation (see Test versions). On the Premium tier, the Kanban also shares the team's work.

What if I stop?

You export your applications before leaving: they run elsewhere, without us.

What if Kedalia stops?

Once exported, your applications run on any server: they depend on no service of Kedalia's own.

Reporting a problem or suggesting an improvement

In the menu, open “Feedback”. Choose “Bug” or “Improvement” under “What is this about?”, write your message, then click “Send”. Say what you did, what you expected and what happened instead: the Kedalia team receives your message by email. Kedalia confirms: “Thank you, your report has been sent.”

A problem in the application itself goes to the assistant first, in the conversation.