What's new

What changes in Kedalia, the most recent first.

On this page

2026-11-18

  • The Business tier is on quote. On the Pricing page, at sign-up and on “Subscription”, its card no longer shows a price: “Contact us” or “Request a quote” asks for a quote, and the Kedalia team sets the tier on your organisation once the quote is accepted. An organisation already subscribed to Business keeps it; if it leaves it, coming back will go through a quote. See Subscription.
  • A single “Other offers” row below the tiers. The Hosting tier, on the left, and the Made to measure offer, on the right, share one row, on the Pricing page as on “Subscription”; at sign-up, Made to measure is alone on it. See Signing up.

2026-11-17

  • One page for AI usage. “Assistant usage” and “Usage” become “AI usage”, a single menu entry: its “Assistant” tab shows the assistant's usage, its “Applications” tab the balance and your applications' AI, for the organisation's administrators. The old links lead nowhere now: go through the menu. See Assistant usage and AI in your applications.
  • “Usage” starts simple. While it has nothing to follow (no application whose AI is managed here, no top-up), the page says what it will be for and offers “Create an application”, with no balance at zero and no top-up. Its “Balance” card lists top-ups only: the tier's payment is on “Subscription”. See AI in your applications.
  • You choose the technology of an application started from scratch. On “New application”, “Start from scratch” no longer offers “The organisation’s”, which nobody may have chosen: no technology is ticked in advance, and “Create application” asks you to pick one. See Getting started.
  • No more typing your e-mail again to pay. Stripe's form comes with the e-mail already filled in: the account's at sign-up, then that of the administrator who paid first; Stripe sends its receipts there. See Signing up.
  • The card is typed in Kedalia. A payment (the tier, at sign-up as on “Subscription”, a balance top-up, a card change) opens Kedalia's “Payment” page: Stripe's secure form shows there, in Kedalia's colours, and “Go back” returns without paying anything. See The subscription.
  • At the end of the contract, no application stays online any more. After a cancellation, as 30 days after a suspension for non-payment, all your applications are stopped, their code and their data kept for the time it takes to export them. To keep them online, the “Cancel” window of a Pro or Business subscription offers “Move to Hosting”, with its price. The terms of sale move to version 3.4. See The subscription.
  • The welcome e-mail says who invites you. Its subject and its first sentence name the administrator who invites you and your team: “Julie invites you to Kedalia, for UX Tour”. The button to choose your password comes right below. See The team.
  • One word for the tests. The conversation, the Kanban and the Applications page say “tests”, like the publication's “Testing” step. After a failure, the button is called “Make the tests pass”: the assistant fixes the code, without weakening or removing a test. On the Kanban, a card says “Updating” while its test version updates, then “Tests running” in “To approve”. See Going live and The Kanban.
  • A paused application is exported whole. An application paused by your tier, after a change of tier or a cancellation, offers “Prepare the full export”: Kedalia restarts it for a few minutes, prepares the export (code, database, documents), then pauses it again. “Download the export” then hands it to you for 7 days. See Exporting.

2026-11-16

  • A new application's home page hands over to you. It says “Your turn!” and invites you to describe your idea to the assistant, until your first request. See Getting started.
  • “Made to measure” on the “Subscription” page. The made-to-measure card sits beside the three plans, as on the Pricing page. “Request a quote” opens a window to describe what you need; an e-mail confirms it went. See Subscription.
  • Pro holds four applications, and the terms of sale move to version 3.3. An organisation that moves to Pro runs four applications, test versions included, instead of two. The terms of sale say what happens at the end of a contract: one application stays online for 30 days, the time to export it, then everything is stopped and deleted. See The subscription.
  • Nothing to change, no plan. When the application already does what you ask, “Request the plan” no longer offers a plan to execute for nothing: the assistant tells you so in a sentence or two, with what already does it. See Asking well.
  • A publication on GitHub goes out on its own. When the repository requires a review, Kedalia merges the change request within minutes of its approval, with nothing to do by hand on GitHub; when the repository accepts only one way of merging, Kedalia first gathers the card into a single change if needed. See The Kanban.
  • Kedalia says “e-mail” everywhere. No more “mail” and “email” beside “e-mail”: in the preview, the button is called “E-mails”; on the team page, the envelope says “Send the welcome e-mail again”. See Getting started.
  • A card is renamed from the Kanban and from its conversation. A “Rename” pencil on the card, on hover, and at the top of its conversation opens the same window as in “Applications”; a published card is renamed too, its title only. A waiting card has the same pencil, which opens its window. A refused rename no longer changes anything. See Test versions and The Kanban.
  • The assistant's gauge spells out its day. Under the message box, it says “Comes back fully on Monday at 12:00 PM” instead of “Comes back · fully back at Mon 12:00 PM”, and the “Assistant usage” page “frees up on Thursday at 02:30 PM”. See Assistant usage.
  • The “Subscription” page is redone. Your tier at the top of the page, with the next due date, the card, “Change card” and “Cancel”; below, a single “Change tier” on the tiers' cards, Discovery included; “Extra applications” and “Latest payments” collapsed. See The subscription.
  • The European models are chosen before paying. Without a subscription, a tier is chosen with one click, then “Pay”; if it includes the European models, the models choice appears below the cards and applies with the payment. See The subscription.
  • The delete window of an application says everything that goes. Its code, its data, its address and its custom domains, its test versions, its conversations with the assistant and its Kanban, under a red “Delete” button; an application whose code stays on GitHub keeps it there. See Export.
  • A test version where nothing was built is deleted with a plain confirmation. On the Kanban as in “Applications”, there is no longer a title or name to type as long as the assistant has built nothing in it. See The Kanban.
  • Opening access to support now asks for a confirmation. “Allow support for 72 hours” first opens a dialog that says what support will be able to do for 72 hours: open your applications, read your conversations with the assistant and their code, and act on them like an administrator of your team. See The team.
  • Attempts also count per connection. From one IP address, 30 wrong passwords in 15 minutes lock password sign-in for 15 minutes, the right one included; no more than 10 "forgot password" links nor 5 sign-ups an hour. The limit per e-mail address stays the same.

2026-11-15

  • Signing up takes two steps: the plan, then the account. A “Made to measure” offer joins the three plans, from €389 excl. VAT on quote, and the plans' details unfold on demand, on the Pricing page too. The passwords of the sign-in, the sign-up and the forgotten password show with a click on the eye. See Signing up.
  • An eighth template, “Catalogue and quotes”. Your products or services as public pages that search engines find, a quote request without an account on each, and the requests followed from new to won or lost. See Getting started.
  • The creation form opens under what you pick. On “New application”, click “Start from scratch” or a template: the name and “Create application” open right under it. See Getting started.
  • Every member picks the technology of a new application. On “New application”, “Technology” offers the organisation’s, already ticked, or one of the other technologies offered. See Getting started.
  • The Preview stays closed for the whole publication. From “Publish” on, no “Preview” button, neither on the edge of the screen nor on a phone, until publishing ends: the page follows its progress. “Ready to resume” no longer asks you to check the Preview. See Test versions.
  • After a cancellation, your applications can still be exported for 30 days. The organisation is locked, but the “Subscription” page says until when, lists your applications and offers “Download the code only” and “Export everything”. See Exporting.
  • The European models are included in the Pro and Business plans. The Pricing page has a “European models” row; the choice is made on the “Subscription” page, “Models” section, and is no longer asked at sign-up. An organisation already on the European models keeps them. See Subscription.

2026-11-13

  • The Pricing page compares the three tiers. Monthly or yearly prices, and every feature of each tier: members, applications, assistant usage caps, server, e-mails, domain names, code access, privacy.
  • The tiers are now Discovery, Pro and Business — and Discovery is payable too. The free tier becomes a paid one: "Subscribe" offers it like the others, at the displayed price excluding VAT. The four tiers' prices are set in Settings → Plans and written to Stripe; a price change needs 60 days' notice (T&Cs, art. 4). See The subscription.
  • The site no longer promises a free trial. The button becomes “Try Kedalia” and a demo is requested through the form: the Discovery tier is now paid like the others, at the price shown on the “Subscription” page.
  • At an open sign-up, you choose your plan and pay right away. The “Create an account” page compares the three plans and opens the payment page; without a choice, the account is created locked and only the organisation's “Subscription” page answers, until paid. See Signing up.
  • At sign-up you choose where your data go: the United States or the European Union. “My data stay in the European Union (European models only)” appears only when the installation offers the European models; the choice can be changed later in “Models” on the “Subscription” page.
  • The “Subscription” page shows the same comparison as the Pricing page, the current plan marked, and a “Models” section for the American or European models choice. See The subscription.

2026-11-12

  • Moving down or cancelling, even with too many applications. “Move to this tier at the end of the period” and “Cancel” are always offered: if your applications do not fit in the tier you choose, tick the ones that stay online; the others are stopped at the end of the paid period, their code, data and conversation kept. “Remove at the end of the period” lowers your extra applications the same way. A stopped application shows “Paused”, and its visitors read that it is stopped; moving back up relaunches it by itself. An organisation whose tier stays unpaid moves to the Discovery tier 30 days after the suspension, which is then lifted; a stopped application takes no publication until it is relaunched. See The subscription.
  • “Publish” waits for the GitHub tests instead of stopping. On an app whose code stays on GitHub, when the update with the live app runs the tests again, the publication waits for them and goes out by itself as soon as they have passed, at most two hours after the click. On the Kanban, “Publish” also offers to publish now or after the tests while they run, and a stopped publication says where nothing was published. See Test versions.
  • “Analyse” reads each test's error, and steps aside once the analysis is done. On an app whose code stays on GitHub, the assistant now receives the error message of each failed test, even in a long report, and says whether the test or the app needs fixing. Once that failure is analysed, the button disappears and comes back at the next failure. See The Kanban.
  • The Hosting tier and extra applications. For a finished application, the Hosting tier (€29 excluding VAT per month) keeps two applications online, with no assistant usage period: each request is deducted from the organisation's balance. On any paid tier, “Extra applications” adds applications at €5 excluding VAT per month each, prorated. See The subscription.
  • The tier is paid by card, from the “Subscription” page. Monthly, or yearly with two months free: its administrators subscribe, move up at once or down at the end of the paid period, change card and cancel, without leaving Kedalia. A refused payment is a formal notice, and the assistant is suspended only 15 days later. Next to “Top up automatically”, a sentence says what the box authorises. See The subscription.
  • Your applications' AI is prepaid, from a balance. For an organisation that pays by card, the window that switches an application's AI on asks for a first payment when the balance is empty: “Pay and switch on” opens a secure payment page, then the AI comes on when you are back. The “Balance” card of “Usage” shows the balance, “Top up”, the automatic top-up, the saved card and the latest payments. With the balance used up, the AI goes off and the application's row says so; a top-up switches it back on. See AI in your applications.
  • The Discovery tier says so in the conversation. On the Discovery tier, the assistant uses a simpler model, and a banner at the top of each conversation says so. A paid tier gives you the full assistant. See Assistant usage.

2026-11-11

  • Forms speak Kedalia's language. A field left empty or filled in wrongly says so under itself, in your language, instead of a browser bubble. In “New conversation”, “Abandon the changes” is set apart, and a message confirms the abandon.
  • The assistant's usage reads day by day. The “Assistant usage” page now shows the share of the week used each day, by application, by kind of work or by person, when the 5-hour period frees up, what a published change costs, the hours the team works and the request log. A sentence warns when the pace of the last few days would fill the week, and an e-mail goes to the administrators at 80% then at 100%. A request counts for the person who made it. See Assistant usage.
  • Switching on an application's AI asks first. A window says its calls will be billed on top of your tier, and offers its cap for the month. The button of a paused test version says “Relaunch”.
  • “Download the code only” and “Export everything”. In an application's “…” menu, the two commands say what they hand you: “Export everything (code, history, data, guide)”. On a phone, that menu fits the screen.
  • After the first publication, Kedalia suggests what comes next. Under “Your application is up to date online.”, a line says “What next? Try it, then say what is missing.”, with “Next change”, which opens a new conversation. In “Applications”, “Last activity” gives the time too.
  • The language picker has a new look. At the top of the site and of the sign-in, sign-up and password pages, a globe followed by the language's code (“EN”) opens the list of the four languages, yours ticked. At the bottom of the site, they are written out: one click is enough. In Kedalia, click your name at the bottom of the menu: “Language” and “Theme” are together there, even with the menu folded. Your role, under your name, still opens on a click.
  • A publication ends on “up to date online”. Once the application is live after “Publish”, the conversation says “Your application is up to date online.”, with “Open” and a button that copies its address; older publications only say “The tests passed.”. On a large screen, the “Preview” tab on the right edge is larger and blue, and while the assistant works, a line under the preview's bar says it reloads when the assistant is done, if the application changes. The tooltip of “Adjust directly” starts with what it brings: a small fix, without a plan, faster and cheaper. See Going live.
  • “Live · latest update failed” explains itself on hover. The pill says why: the tests of the latest update failed, or it could not start; the site stays on its previous version. It also names the button that answers it, “Analyse”, “Fix” or “Retry”. The first two turn pale blue and sit just right of the pill, and “Analyse the tests” is now “Analyse” everywhere, the conversation included. See Kanban.

2026-11-10

  • A test version's row stays readable. In “Applications”, its state and “Open” no longer drop under its name: when “Publish” is greyed out, the reason shows when you hover the button instead of being written next to it, and “by …” no longer follows it, the row already saying who created it. When its checks failed, “Fix” sets the assistant to work on the test version. See Test versions.
  • “Publish” stays clickable while the tests run. While a test version's tests run, the bar says “Up” and “Tests running”, and “Publish” offers “Publish now” or “Publish after the tests”: the publication then starts by itself as soon as they pass, and can be cancelled from the conversation. See Test versions.
  • A preview opened in a tab says so. “Open in a tab” shows a badge in the bottom right corner: “Preview: this is not the live application. Test data.” Its cross hides it until the page is next loaded. See Getting started.
  • The plan says what the assistant decided on its own. When it made a choice you had not stated, a line “Decided without asking you” says so before you execute the plan. The plan also always starts with its title, and the assistant names the buttons, “Request the plan” or “Adjust directly”. See Getting started.
  • In the preview, “Sign-in details” becomes “Test account”. Open, it first says what this account is for: the preview signs you in with it, and it lets you sign in again after signing out. A test version keeps “Sign-in details”. See Getting started.
  • A card set aside frees its place. On the Kanban, a started card set aside in one of your team's columns pauses its test version: it no longer counts in your tier, its test data is kept, and “Relaunch the test version” puts it back online; left set aside, it pauses again after 12 hours with no activity. An organisation's count no longer includes paused versions. A card already set aside before this update pauses 12 hours after it, unless something happens on it in between. See The Kanban.
  • On a phone, publishing stays in view. While a test version is being published, a line stuck at the top of the screen says where it stands, even while you read the bottom of the conversation; tap it to go back to the “Publishing into” frame. See Test versions.

2026-11-09

  • A card's conversation tells its Kanban column again and changes it. The “Kanban column” list is back at the top of the conversation, beside “Publish”, when the bar has room for it: queue the card once the plan is read, take it out of the queue, put it in a column of your team. On a phone, or when the bar is too narrow (menu open), the card changes column from the Kanban. See The Kanban.
  • On the “Domains” page, the failure of “Verify” stays under the name, and a refused name stays in the field. The name's row says “Last check at 7:01 PM:” followed by what to fix, instead of a message that vanishes; it clears at the next check, with another action or on a reload. A refused name is no longer wiped: correct it without retyping. For a bare domain, a sentence explains why it is an A record, and recommends ALIAS or ANAME if your provider offers them. See Domains.
  • On the “Team” page, “Invite” is at the top and the roles are explained. The “Invite” button, next to the number of members, goes down to the form; it is greyed when every seat is taken, with the reason right below. Under the choice of role, one line says what a member does and what an organisation admin does. At the bottom of the menu, clicking your role shows the same explanation. See The team.
  • For an app whose code stays on GitHub, all its tests pass before publishing. Kedalia reads every test GitHub runs on the test version, not only its own, and “Publish” waits until they have passed. If one fails, the assistant says which one and proposes to fix the test or the app, depending on what changed. See The Kanban.
  • A start-up that fails after “Publish” retries by itself. When the new version does not start the first time, Kedalia retries it twice at most, and the “Publishing into” frame says “Attempt” followed by the number. If the start-up still fails, “Retry the start-up” is now in the test version's own conversation, with no detour through the application's. See Going live.
  • A closed preview stays closed. On a large screen, the preview's ✕ and the “Preview” tab that reopens it are remembered for each application and each test version, in this browser, even after the page is loaded again. The “Open the preview with the conversation” box in “Account” decides the first opening. See Getting started.

2026-11-07

  • On a computer screen, the Kanban shows all its columns or says which ones overflow. The menu folds on arrival on the Kanban (≡ opens it), a shadow on the row's edge marks the columns off-screen, and each column carries a “Your turn” or “The assistant's turn” badge saying who must act. See The Kanban.
  • On a phone, the preview goes full screen. The “Full screen” button, in the preview's bar, hides Kedalia's bar and the tabs: the application takes the whole screen. “Leave full screen”, the back gesture or Escape leave it. The bar now holds on one line; its rarer tools are in “…”. On a large screen, nothing changes. See Getting started.
  • When the assistant stops before the end, the conversation says why and what is kept. The artificial intelligence service did not answer, the work was cut off, or the reason is unknown: it is written. Instead of two “Continue the implementation” buttons there is one, by the message box, with what is kept and what continuing counts above it. If the service did not answer, the assistant tries again once by itself after a minute. See Assistant usage.
  • An application or a test version can now only be deleted by its author or an administrator. A member deletes what they created; on a colleague's work, “Delete…” is greyed out, with “Reserved for its author and the administrators”, and the bin of a Kanban card does not show. On a colleague's test version, “Publish” is followed by their name. See Your team and Test versions.
  • On a phone, the creation page puts the name first and “Create” stays at the foot of the screen. “Start from” becomes a list of templates with their screenshot, and “View” opens one full size before you choose it. On a large screen nothing changes. See Getting started.
  • On “Applications”, the creation form no longer disappears when a teammate creates an application. While you fill it in, it stays in place with what you typed, and a line above says who created the application that arrived in the meantime. See Getting started.
  • “Discuss” is “Send” again, and a few other words change. In the conversation, the button is called “Send”; its tooltip still says nothing is changed yet. In the menu, “Feedback” becomes “Report a problem”, and “Account” says “Conversation” instead of “AI assistant”. The messages that stop the assistant talk about your usage, no longer about a budget or a sliding window, and say what to do. See Assistant usage.
  • On a touch screen, buttons and menus are easier to tap. On a phone or a tablet they are at least 44 px under the finger, as accessibility guidelines recommend: “…”, “Edit”, menu entries, the lists you pick from, the close crosses. With a mouse, nothing changes.
  • An application started from a template says where putting it online stands. Its first conversation no longer calls it “already online” while it is being tested: it says it will be in a few minutes, with an empty database, and that the preview is empty too, ready for a few trial rows. See Getting started.

2026-11-06

  • The Preview closes as soon as “Publish” is clicked. The publication is followed in the “Publishing into” frame of the conversation, with a single sentence: the site stays on the previous version until the start-up is over. See Test versions.
  • The conversation's gauge reads shorter, and an application's date no longer moves when its conversation is opened. Under the message box it says “Comes back · fully back at 10:00 PM · Details” (and “available again at …” when the period is full). On the Applications page, “Created … by …” stays shown until the conversation has a message. See Assistant usage.
  • “Retry” next to a failed start-up. When the start-up fails while the checks passed, one click puts the same version live again, from “Applications” or the application's pages. See Going live.
  • An application's address can be copied from the Applications page, with the icon next to “Open”. “Published” gives the day when it is not today, the support access says when it ends in your own time (“until Monday 9 November at 19:09”) and the Consumption page names its months in words.
  • On the Kanban, a published card's border says where it stands. In “Live”: amber dashes while publishing, green once live, red on a failure, with “See the error” or “See why” leading to its conversation. A legend under the column says it in words, and a live card stays so even if the app stops later. See The Kanban.
  • A long conversation summarises itself while you are away. Left a few minutes without a message, it summarises itself while the assistant still remembers it at a lower cost, and says so: “Conversation summarised to stay fast”. Your next message then costs much less. The “Long conversation” banner of 2026-11-04 now shows only when the summary could not be made. See Assistant usage.
  • An application's pages have their tabs. At the top of the screen, beside its name: “Conversation”, “Kanban”, “Domains” and a new “Settings” tab (name, code, application AI, deletion). On the Applications page, “Kanban” comes first on the application's line, parted from “Edit”. See Getting started.
  • Requiring test versions. An administrator of your organisation can set an application so that it is changed through test versions only, for everyone. See Test versions.
  • The access to the code explained, and closable. “Open the access”, in “Team”, first says what it does, and “Close the access” deletes it. See Team.
  • The conversation guides you to the first publication. As long as an app has never been published, a line at the head of its conversation shows the current step — “Describe › Plan › Execute › Publish” — and what to do next. See Getting started.
  • The red banner comes before the change. Once the app is published, every conversation of the live app opens on the banner that warns you, with the “Create a test version” button inside it.
  • “Plan ready to read” on the Applications page. When the assistant has finished a plan, the app's line says so; a click opens the conversation on the plan. See Asking well.
  • The assistant's gauge in one sentence. Under the message box, it says when the usage will be fully back, and “Details” opens both periods on a click. See Assistant usage.
  • One word for going live: “Publish”. In the live application's conversation, the “Deploy” button becomes “Publish (1 change)”, and the line after it says “Publishing”, then “Published at” followed by the time. A test version updates itself instead: “Updating the test version…”, then “Test version up to date”. The “Deployment” step is now called “Start-up”. On the Kanban, tickets become waiting cards: “Add a card”, at the top of one of your team's columns. See Going live and Kanban.

2026-11-05

  • “Ask for a change” has its button on the Kanban. A card of “To approve” offers it beside “Publish”: it opens the “What should change?” window, as dragging into “Queued” does, and works from the keyboard and on a phone. See Kanban.
  • Domains read well on a phone. A name's two DNS lines show as blocks, their whole value on screen, and a “Copy” button goes with each name and each value. See Domains.
  • A test version's header fits a phone. “Publish” stays on screen, the reason a “Publish” is greyed out goes under it, and the open credentials take the whole width. The “Kanban column” list leaves the conversation: a card changes column from the Kanban. See Kanban.
  • “Published” waits for the end of going live. A published test version keeps its progress line — tests, then start-up — to the end, instead of showing “Published into” as soon as the versions are combined. See Test versions.
  • “Assistant usage” becomes a dashboard. The menu page still shows your whole organisation's two sliding periods, and adds your own usage — your share of each period as a percentage, your conversations per month. Your organisation's administrator also sees each member's share there, and Kedalia's global administrator every organisation with the cost in euros. The old “Assistant usage” sections of Settings and of the organisation page are gone; the organisation page keeps a link to the dashboard filtered on it. See Assistant usage.

2026-11-04

  • A long conversation says so. Above the message field it shows the least each message costs of your usage over 5 h. Left more than five minutes without a message, it goes “on standby”: the banner warns that the next message will cost more, and offers a new conversation. See Assistant usage.
  • “Make the tests pass” on the Applications page. When the tests of an application's latest update failed, the button also shows on its card, next to “Edit”: the assistant starts fixing without you leaving the list, and the card reads “The assistant is working”. See Getting started.
  • The assistant's gauge has its own page. “Assistant usage”, in the menu, shows the two sliding periods — “over 5 h” and “over 7 days” — as a percentage of what your tier includes, for your whole organisation, without opening a conversation. See Assistant usage.
  • A test version starts from what the Preview shows. A new test version starts from the app as the “Preview” shows it: a change saved but not deployed yet is in it, instead of being left out. See Test versions.
  • Test versions follow the live app. After each change of the live app, its test versions used in the last 14 days receive it on their own, one at a time, then are installed again. When both changed the same files, nothing is changed and the conversation offers “Combine both versions”. See Test versions.
  • A Kedalia restart no longer cuts the assistant's work. If Kedalia restarts while the assistant is writing a plan or changing the application, the conversation says so at once, the work already done is kept, and the assistant picks up by itself as soon as it can, for ten minutes at most; after that, “Continue” starts it again. During the restart, the page shows “Kedalia is not responding” and comes back by itself. See Assistant usage.

2026-11-03

  • “AI assistant” becomes “Edit”. On the Applications page, the button that opens an application's conversation is called “Edit”; “Edit with the AI assistant” on hover. In a test version's “…” menu, “Edit the test version” becomes “Rename”. On a published test version, the button says “Read back”: its conversation reads back without changes. See Getting started.

  • Kanban: an icon once the assistant has answered. In “In discussion”, a card the assistant has already answered carries, right of its title, an icon of two bubbles: “Talked with the assistant” on hover. See Kanban.

  • “Open” and “Kanban” closer at hand. On the Applications page, “Open” sits right of the “Up” state, on the card as on a test version's row. On the Business tier, “Kanban” is a button right of “Edit”, no longer an entry of the “…” menu. See Getting started.

  • Send the welcome mail again. On the “Team” page, the envelope icon of a colleague who has not chosen their password yet sends them the welcome mail again, with a fresh link valid for 7 days. See Your team.

  • Publishing can be followed to the end. After “Publish”, the window closes at once and the publication is followed in the test version's conversation, in four steps, up to “Your changes have been live since” followed by the time. A failure of the checks or of the deployment is stated, with “See the error” and “Fix in” followed by the application's name, and the application shows “Live · latest update failed” instead of “Up” in green. When the live app changed the same files, publishing pauses while the assistant combines both versions, then “Resume publishing” finishes it. See Test versions.

  • “Publish” says what it is waiting for. When greyed out, the button writes its reason next to it: nothing to publish, the assistant is working, checks failed, or the live app is being updated. This holds in the conversation, in “Applications” and on the Kanban. After the click, the message says “Publishing started: tests, then going live, about 4 min.”, and a refused publication no longer shows tests running. See Test versions.

  • Your applications in four languages. A new application starts in your account's language, and also speaks English, French, Spanish and Polish: each user picks their own on their account page, their e-mails included, and an administrator changes the default language in its Settings. The models too. See Getting started.

2026-11-02

  • “Adjust directly” during an update. When a test version runs its checks again after a delivery, the button no longer stays greyed out: the adjustment you write waits above the box, with a “Cancel” button, and goes ahead by itself as soon as possible, on every tier. See Asking well.
  • A clearer Applications page. Each card shows the application's state in a coloured badge, its address, its last activity and who created it; after a failure, one sentence says what to do. “Open”, “AI assistant” and “Create a test version” stay on the card, the rest moves into its “…” menu. “New application”, at the top right, opens a page of its own, and the applications that need your attention come first. See Getting started.
  • Close a reopened test version again. If nothing has been done in it since it was reopened, “Close again” replaces “Publish”: it goes back to published without touching the live app, and frees its place. In “Applications”, “Publish” is greyed out on a test version without any change, as in its conversation. See Test versions.
  • A dark theme. Kedalia now follows the light or dark setting of your computer or phone. To force it, pick “Light”, “Dark” or “System” beside the language choice: at the bottom of the menu, on the sign-in page or in the site's footer. The choice is kept on this browser. The Preview of your applications and your e-mails still show as your users see them.
  • Start from a template. In “Applications”, “New application” offers templates: applications already built with Kedalia for a common need (flex office, sales follow-up, expense reports, equipment inventory…). Yours starts with their code, without any data, then the assistant adapts it to your team. See Getting started.
  • An application name as you write it. “New application” takes capitals, spaces and accents: “My Kitchen” gives the address my-kitchen, shown under the field, and stays the name of its card and the one the application shows. See Getting started.
  • A suspended application says so. If Kedalia takes an application offline after a notice of illegal content, its card carries the "Suspended" badge with the date and the reasons, and its visitors land on a page saying it is suspended. Your administrators get the reasons by e-mail, and can reply to contest. See Security and data.
  • “Move to…” puts it at the bottom of the column. On a touch screen, the ticket or card you move to a column now lands after what it already holds, no longer at the top. See Kanban.

2026-11-01

  • The terms of sale move to version 2. They now describe your applications' AI and its price, your domain names, what you owe the people who use your applications, and how illegal content is reported. By creating an account, you declare that you are acting for your business. See Security and data.

2026-10-31

  • AI in your applications. Your applications can summarise a text, read a document or sort requests with Kedalia's AI, with no key to provide. An administrator of the organisation switches it on application by application in the new “Usage” page, which also shows what is billed each month and each application's cap. See AI in your applications.
  • The waiting line says what the assistant is doing. While it works, “The assistant is working…” becomes “The assistant is reading your application…”, “…changing your application…”, “…checking its work…”, “…trying the application…” or “…reading a web page…”, depending on what it is doing at that moment, always on a single line. See Frequently asked questions.
  • A preview email can be deleted. Under the preview's “Emails” button, “Delete” removes the open email from the list, for you and the assistant alike. See Getting started.
  • A message you have not sent waits for you. What you wrote in the message box without sending it, with its attached files, comes back when you return to the conversation, even after closing the browser. It stays in this browser until you send it or sign out. See Asking well.
  • Another service's keys are entered in the application. When a change uses another service (online payment, a map, text messages…), the assistant adds a field to the application's settings, most often in the “Configuration” section, and tells you what to paste there. The key stays yours and changes without a new request. See Asking well.
  • The AI assistant on a phone. Its buttons take a short name there: “Adjust”, “Plan”, “Continue”, “Test version”, “Fix”, and “Sign-in details” becomes a key. The “Conversation” and “Preview” tabs stay at the top of the screen while you read, with “New conversation” as an icon beside them, and the message box stays at the bottom. The live app's warning fits on one line: tap it to read it in full. The preview fills the screen under the tabs, and the buttons are easier to tap.
  • Each tab keeps its organisation. If your account belongs to several organisations, switching organisation in one tab no longer affects your other open tabs: each one goes on showing, and changing, the organisation it was showing. The organisation you chose last is still the one you land in when you sign in and in a new tab.

2026-10-30

  • “Publish” tries again by itself. If the live app changes while publishing, Kedalia adds its changes to the test version and starts again, up to three times, instead of asking for another click. When the assistant has to combine both versions, the message now says plainly that nothing is published yet and what to do next. See test version.
  • “Publish” follows your GitHub repository's rules. If the repository refuses one way of merging, Kedalia tries the others. If it refuses them all, the message says so instead of speaking of a conflict, and the change request stays open on GitHub. See Kanban.
  • A card merged on GitHub goes “Live”. When the change request “Publish” opened is accepted directly on GitHub, the card moves to “Live” by itself within five minutes, instead of still offering “Publish”. See Kanban.

2026-10-29

  • A description takes attached files. The paperclip, “Attach files”, adds images, PDFs, spreadsheets, documents or ZIP archives to the description of a ticket or a card, and a long pasted text becomes “pasted-1.txt” there, as in a message. The ticket sends them to the assistant with its words when it starts; those added later go with your next message. See Kanban.

2026-10-27

  • The preview's emails can be read instead of getting lost. What the application sends from the preview goes nowhere: the “Emails” button shows them, and “Send it to me” sends you one, marked “[Preview]”, to see how it renders in your mailbox. The assistant reads them too, to check a sign-up or a forgotten password.
  • A long pasted text becomes an attached file. Pasted into the message box, a text of 4,000 characters or more becomes “pasted-1.txt”, which the assistant reads in full: a long specification goes through uncut. The description of a ticket or a card now holds up to 100,000 characters. See Asking well.
  • The export says why it is refused. When the application is not running, the export icon gives the reason instead of “The export failed. Try again.”. See Export.
  • The welcome email sets the password in one click. A colleague you invite gets a “Choose my password” button, valid for 7 days, without going through “Forgot password?”; the email also tells them they can sign in with Google if their address is a Google account.

2026-10-26

  • Each panel has its own buttons. The top of the page keeps the application's name, its state and its main action, “Create a test version” or “Publish”. “New”, for a new conversation, and “Abandon the changes” move to the head of the conversation. The preview closes with the ✕ at the end of its bar and opens again with the “Preview” tab on the right edge of the screen.

2026-10-25

  • In a shared conversation, each message says who wrote it. A colleague's request carries their name, and “The assistant is working for Marie…” says whom it is working for. When the application is busy with a colleague's implementation, the refusal names them.
  • Every test version updates itself, whatever your tier. When the assistant has finished, the change is installed on the test version without going through “Deploy”, which stays on the live app only. Its conversation belongs to your whole organisation, and “Create a test version” asks for a title. Your existing test versions take their name as their title.

2026-10-23

  • More room for the preview and the conversation. In the AI assistant, the menu folds to its icons and a single thin bar stays at the top; the preview takes the whole height and the rest of the width. Drag the border to widen one or the other: the width is remembered on this browser.
  • The preview has a browser bar: the page shown, “Reload”, “Open in a tab”, and three widths, computer, tablet and phone.
  • A lighter interface. Pages sit on a light grey background, what you read in white panels; the assistant's answers show without a frame, and the message box gathers its buttons. “A question?”, the help's assistant, moves to the menu, under “Help”, on every page.

2026-10-22

  • A reopened test version or card starts again from the live app. A “Conversation reopened” line marks what is already live in the conversation; the card is back in “In discussion”, and “Publish” waits for a new change instead of offering to publish what already is.
  • Making an inactive account active again takes a seat of your tier, as an invitation does.
  • The refusal to remove the organisation's last administrator is shown in your language.

2026-10-21

  • “Reopen” asks for confirmation. A published test version or card only reopens after a window that recalls what it involves: a few minutes of preparation, fresh test data, a place in your tier.
  • Two buttons of the conversation are renamed. “Send” is now “Discuss”: the assistant answers, nothing is changed yet. “Apply as a correction” is now “Adjust directly”: a small touch-up to what was just delivered, without a new plan.
  • A card's column, in its conversation. Beside “Publish”, a list tells where the card stands on the Kanban and moves it: into the queue, out of it, or to a column of your team.
  • The Kanban scrolls by itself when you drag a card or a ticket near its edge, instead of scrolling the page, which no longer widens with an empty margin on the right.
  • The preview at the opening of the AI assistant is a setting of your account. Untick “Open the preview with the AI assistant” in “Account” for it to stay closed. “Hide the preview”, in the conversation, now only lasts until the page is loaded again.

2026-10-20

  • An SVG logo can be attached to a message too. The assistant puts it in the application. An SVG that holds code is refused: attach a PNG export of it instead.
  • Photos and your logo in the application. Ask the assistant for a photo: it picks one from a free image bank (Unsplash, Pexels or Wikimedia Commons) and saves it in the application, instead of linking it from another site. A photo from Wikimedia Commons is shown with its author and licence. Attach your logo or your photos to a message and ask it to put them in place.
  • “Apply as a correction” without writing your request again. Once you have discussed it with the assistant, click the button with the box empty: what you asked since the delivery is applied directly.
  • The pencil on a card, in “Applications”, now only renames the card. To change the name the application shows at the top of its pages and the name of its emails, ask its AI assistant.
  • A conversation's buttons move to the top of the page, beside its name: “Publish”, “New conversation” and “Abandon the changes”. “Make the tests pass” shows in the conversation, under the message that reports their failure.

2026-10-17

  • “Publish” no longer takes you away from the conversation. The window stays open on “Publishing…”, then the test version's conversation stays on screen, read-only, and follows the live app's update.
  • A published test version reopens: “Reopen the conversation” in its conversation, “Reopen” on its row in “Applications” or on its Kanban card. It is recreated from the live app, and the conversation carries on with the assistant where it had stopped.
  • “Publish” is also on a test version's row, in “Applications”. Once published, its “AI assistant” button opens its conversation again, read-only.

2026-10-15

  • Kanban: “Ask for a change” leaves the cards. Drag the card into “Queued”, or write the change in its conversation, then “Apply as a correction”.
  • Kanban: a card dragged from “To approve” into “In discussion” opens its conversation, to talk it over with the assistant. A new plan brings it back there.
  • The preview opens already signed in, with its administrator test account, and a test version lets you in with “Sign in with Kedalia”: each member of the organisation gets an administrator account in their own name there. The sign-in details fold under a “Sign-in details” button. For applications created from today.
  • Board cards no longer show their test version's sign-in details: they are at the top of its conversation. A “Kanban” button, at the top of the page beside the application's name, replaces the “Back to the board” link.
  • On the Applications page, a test version shows its title once, then its address before “Up”.
  • After you send a message, a long conversation goes down to “The assistant is working…”: you had to scroll to see it.
  • In a test version, the username and password sit beside its address, at the top of the conversation. In the preview, they move to the left of the buttons; “Reload” and “Open in a tab” become icons there, named when you hover them.
  • A greyed-out “Publish” tells why when you hover it, instead of a line under the buttons. A card with no description no longer shows “Add a description”: the pencil beside “Description” adds one.
  • “Try a change” is now “Create a test version”. In the live app's conversation, the button now sits at the top, beside its name and “Preview”.

2026-10-14

  • Kanban: the “To clarify” column is now called “In discussion”: that is where you clarify the request with the assistant, then approve its plan.

2026-10-13

  • The terms of sale and the data processing agreement are online, each on its own page, with a table of contents. The sign-up page recalls them under its button.
  • The legal information reads like the help: a table of contents, airier sections, and tables that scroll on a phone.
  • After 10 wrong passwords in 15 minutes on an address, password sign-in on that address waits 15 minutes, and the message says so. An address receives no more than 3 “forgot password” links an hour.

2026-10-12

  • An application's address, next to its name, is now in colour, followed by an arrow: a click opens it in a new tab.
  • The “Assistant usage” gauge now sits under the conversation's message box, where a message spends it.
  • “Point” puts a label into your message, where the cursor was: write what should change right after it, and point at several elements in one message. The label cannot be edited, its cross removes it, and the conversation shows it as is.
  • Publishing a card the live app has moved past: Kedalia first adds the live app's changes to the card, and renumbers the card's database changes above its own. When both changed the same files, the assistant combines the two versions instead of an error message: check the result in the “Preview”, then publish again.
  • Kanban: “Undo start”: a card in “In discussion” started by mistake becomes a ticket again, at the top of “Backlog”. Its test version and its conversation are deleted; “Discuss with the assistant” opens a new one.
  • “Point” on an image calls it “Image”, with its description or its file name, even when a layer covers it or when it is a background: no more nameless “Element”.
  • A card kept in one of your team's columns takes a place among its tickets: drag it above or below one of them to prioritise it. A new card arrives at the top of "In discussion".
  • In a ticket's window, the “Start” button is now called “Discuss with the assistant”: it turns the ticket into a card, and the assistant reads it as soon as its test version is ready.
  • While the assistant works, the waiting line says what it is doing when nothing else moves on screen: "The assistant is reading the application's code…", or, during the plan, "The assistant is finishing the plan…".
  • The address of an application that does not exist, or no longer does, opens a page that says so instead of a technical error: a deleted or renamed application, or a typo.
  • Two database changes at the same time: when a card delivers first, Kedalia renumbers the other conversation's change itself and delivers it; that conversation's preview starts over with fresh test data.
  • Checks that could not run because of an incident on our servers are run again once by themselves, and no longer offer to fix an application that has nothing wrong.

2026-10-11

  • A card and the app's conversation at the same time: when both change the database, the one that delivers second no longer loses its work: Kedalia renumbers its change and delivers it. Each also checks the app in its own browser, without disturbing the other.
  • A card's conversation on a laptop always keeps room for several messages: the page scrolls when the description and the credentials take up the screen's height.
  • What Kedalia refuses stays typed: the name of a new app, a colleague's invitation and the display name are no longer wiped after a refusal; just correct them.

2026-10-08

  • The help assistant follows you everywhere: the round button at the bottom right of every page opens and closes it; the conversation stays when you change pages. It leaves the bottom of the help pages.
  • Kanban: the card keeps its description: once a ticket is started, its description stays at the top of the card's conversation, apart from the exchanges with the assistant. The pencil keeps it up to date, and the assistant reads the new version with your next message or your next plan request.

2026-10-07

  • A question? Ask the assistant: at the bottom of every help page, the assistant answers from these pages. The "fast" intelligence level also moves to a newer model, more capable for the same use.
  • Display name: the pencil on an application's card, in “Applications”, sets the name its emails (welcome, forgotten password…) go out under.
  • “Request the plan” takes your last detail along: what is written in the message box goes with the request, no need to send it first.
  • “Point”: the line added to your message names the page in plain words, for example “home page”.
  • The assistant's progress lines are written in your language and in your words, throughout the build.
  • Signing up with Google: the account takes the language of the page you sign up from.
  • Help is here: these pages explain Kedalia in the words on your screen, and are kept up to date with every change you will notice.