Do our documents and screens leave the company?

Kitewell runs on your own PCs and servers, and Descarty never receives your business data. You choose the AI model: a cloud API, or an in-house or local model with an OpenAI-compatible API. With an in-house model, no data leaves the company. With a cloud model, what the AI reads is sent to the model's provider.

What if the AI misreads something?

A person checks what the AI produced before the work goes on. In a sheet, every value the AI reads shows the quote it came from, and rows below your confidence threshold go to a person. Reviewers can send work back with notes on what to fix, and who approved what is kept in the run history.

What happens when a screen changes or a run stops?

When a screen changes, the AI reads it again, relearns the step, and carries on. The relearned step is saved, and later runs repeat it. If a run still stops, ask the assistant right there, and it finds the cause and proposes a fix. A proposal is not saved until a person applies it.

What happens to the RPA and systems we use today?

Keep them. Kitewell operates screens the way a person does, so it works with systems that have no API. Move the robots that keep stopping and the work you gave up automating because it needs judgment, and leave fast, fixed processing in your current RPA.

¥14,800 per computer per month, or ¥148,000 per computer when paid yearly, before tax. A computer costs the same whether it builds or runs. You can try it free for 14 days. The one-month onboarding, where we build your first job together, is ¥500,000 before tax, credited to the first year if you go on.

Collect orders and due dates from supplier portals

Every morning, collect new orders and delivery date changes from several customers' supplier portals and, after review, record them in the sales system.

Try free for 14 days Book a 30-minute demo

Runs on your own PCs and servers
Use Azure OpenAI, Amazon Bedrock, Google Vertex AI, or an in-house model
Its engine is Descarty's open-source Dagu (GPL-3.0)

The problem today

Staff sign in to a different portal for each customer, check orders and delivery date changes, and copy them into the sales system. RPA automated this, but the robots stop whenever a portal's screens change, and only the person who built them can fix them.

In depth: Collecting orders from each customer's Web-EDI in one list

The workflow in Kitewell

Sign in to each customer's supplier portalWeb
Collect the order list and delivery date changesWeb
AI identifies what changed since the last runAI judgment
The owner reviews changed ordersApproval
Record them in the sales system and post the result to TeamsAutomatic

What AI does

Compares with the previous run to identify new orders, quantity changes, and delivery date changes, and summarizes them.

Where people decide

The owner reviews only changed orders before they are recorded in the sales system.

Features used

This work, run in Kitewell

On October 19, 2026, Kitewell ran the part that collects order CSVs from three stand-in ordering sites and merges them into one list. The sites were built for the test.

The first run: collecting from the three sites succeeded in 15, 14, and 14 seconds, and merging into the order list in under a second (Japanese screens) — The first run: orders collected from three sites and merged into one list (Japanese screens)

The run's "Waiting for you" panel asking for the 6-digit code the food distributor sent (Japanese screens) — On a site that asks for a one-time code, the run stops and asks for it, then carries on once it is entered (Japanese screens)

Prove Kitewell on your own systems

Try it free for 14 days on your own PC. To see it working first, ask for a 30-minute demo. There is also a one-month onboarding (¥500,000 before tax), where we build your first job together.

What to check when you try this work

Whether sign-in and order collection run reliably on each portal
How far the workflow keeps running without changes when a screen changes
How to record orders in the sales system: screen, API, or CSV import

How the onboarding runs

Week 1Requirements and success criteria
Weeks 2 to 3Build
Week 4Verify on production screens
Final dayReport

One-month onboarding

Length: One month
Cost: ¥500,000 (tax excluded). Your staff build, with the developer beside them
If you go on to a license: The onboarding fee is credited to the first year's contract
Without the onboarding: At Team scale, start on Team monthly (¥14,800 per computer a month, tax excluded), and cancel in any month

You can try it first on your own PC, in the free 14-day trial.

Book a 30-minute demo Ask about onboarding

See how the onboarding runs and its terms

Frequently asked questions

Do our documents and screens leave the company?: Kitewell runs on your own PCs and servers, and Descarty never receives your business data. You choose the AI model: a cloud API, or an in-house or local model with an OpenAI-compatible API. With an in-house model, no data leaves the company. With a cloud model, what the AI reads is sent to the model's provider.
What if the AI misreads something?: A person checks what the AI produced before the work goes on. In a sheet, every value the AI reads shows the quote it came from, and rows below your confidence threshold go to a person. Reviewers can send work back with notes on what to fix, and who approved what is kept in the run history.
What happens when a screen changes or a run stops?: When a screen changes, the AI reads it again, relearns the step, and carries on. The relearned step is saved, and later runs repeat it. If a run still stops, ask the assistant right there, and it finds the cause and proposes a fix. A proposal is not saved until a person applies it.
What happens to the RPA and systems we use today?: Keep them. Kitewell operates screens the way a person does, so it works with systems that have no API. Move the robots that keep stopping and the work you gave up automating because it needs judgment, and leave fast, fixed processing in your current RPA.
What does it cost?: ¥14,800 per computer per month, or ¥148,000 per computer when paid yearly, before tax. A computer costs the same whether it builds or runs. You can try it free for 14 days. The one-month onboarding, where we build your first job together, is ¥500,000 before tax, credited to the first year if you go on.

See this work in a demo

A 30-minute demo shows this workflow running. The 14-day free trial lets you check it on your own systems.