Answer your board from anywhere.
AI4Kanban runs on your machine and stops when it needs a person: a card ready for review, or a question only a person can answer. Cloud carries those two moments to whoever on the board can act on them — their desktop, and their Slack or Lark — records the decision, and hands it back to the machine of whoever made it.
01 · Your board
A card reaches ready, or asks a question only a person can answer.
02 · Cloud
One event reaches everyone it is for — a review goes to the board's members, a question to its owners — in the app and in the Slack or Lark conversation each of them connects.
03 · A machine
The decision comes back to the machine of whoever made it, and the board builds or resolves the card where it has always run.
No board event is sent until you sign in. Cloud is off until you sign in with GitHub inside the app. The boards you open on that machine then raise their events, and each board has one switch for its notifications. On a board you share, that switch is yours on every machine you open it on. Sign out and the machine raises none.
What stays here, and what an event carries
Stays on your machine
- The repository — Cloud is never given access to it.
- The agent, and the work it does — every run happens here.
- A Local board — every card is a Markdown file in your own repository, and it is what a new install starts on.
Cloud runs no agent and reads no repository. It holds a board only where you asked it to — a Cloud board, which you can export as Markdown or delete outright, whenever you like.
Goes with each event
- The card's number and title
- Its opening paragraph
- Its review notes — the card's
Worth notingsections, which is what judging a build off a title alone is missing. - The questions it is asking — with their options.
Enough to decide from, and nothing else off the card.
What Cloud does not do
- No per-card permissions — a workspace has two roles and no third. An owner runs its name, its members and its machines, and is who a question is put to; a member does everything else on the board, and may answer any question they can see. Nothing is locked to one person card by card, and no card names who has to decide it.
- No way to invite somebody who is not in the preview — an owner adds a GitHub handle we have already admitted. Anyone else presses Request an invite first.
- No board in the browser — there is nothing to read or edit on the web.
- No agent run by Cloud — it builds nothing and writes nothing to your repository.
- No always-on machine — a decision you make while your own machine is off is recorded and waits, and runs once one of your machines is reachable again. It never runs on a teammate's.
Invite only, and free while the preview lasts
01 Sign in with GitHub, inside the app.
Configuration → Cloud. It says straight away whether your account is in the preview.
02 If it is not, ask from the refusal itself.
Press Request an invite there. That is the only way to ask: this page carries no form, no waitlist and no address to write to.
03 We approve it, and you are in.
We read every request by hand. Approving admits your account on the spot and emails you to say so — there is nothing to paste and nothing to sign in for a second time. No date is promised for a reply.
What Cloud holds
- The events your board published — with the decision and the answers recorded against each one.
- Your board's folder name — the name only, so a message can say which board it came from.
- A record of the machine that runs your board's work
- One Slack connection, one Lark connection — if you connect them.
Never your repository, the path your board sits at, a credential, or a model key.
The full text is in the Privacy Policy and the Terms of Service.