Register interest in the product whose users are stuck, not in the one that sounds largest. Kiweely Nest, Kiweely Bridge, Kiweely Leaf, and Kiweely Roots are all coming next, on their own pages, and none of them is required to use the others. Kiweely Vine is live today. If the work is a consultant or developer building in the tenant this month, do not wait on an interest form. Install Vine.
The ecosystem page states the same order of reality: Vine is live today; Nest, Bridge, Leaf, and Roots are coming next. Leaf and Roots publish no price and no date. Nest and Bridge publish prices and still say they are coming next. An interest form is not an order.
Start here
Answer one question: who is blocked, and what are they trying to finish?
| If this is the blocked job | Register or open this | Status on the page | What the form is for |
|---|---|---|---|
| If this is the blocked jobConsultants or developers need to change the tenant now | Register or open thisVine, not an interest form | Status on the pageLive today | What the form is forUse it on Mac or Windows |
| If this is the blocked jobThe in-house Workday team is the bottleneck: tickets, routines, projects, approvals | Register or open thisNest | Status on the pageKiweely Nest is coming next | What the form is forBook a demo. It is not open for download |
| If this is the blocked jobEmployees need Workday answers inside Claude, ChatGPT, or Gemini | Register or open thisBridge | Status on the pageKiweely Bridge is coming next | What the form is forRegister interest |
| If this is the blocked jobEmployees need a page, a phone action, or an approval in Teams, Slack, DingTalk, or Lark | Register or open thisLeaf | Status on the pageComing next | What the form is forTell Leaf which screens and which channel |
| If this is the blocked jobPayroll, benefits, identity, finance, or a partner file has to run on a schedule | Register or open thisRoots | Status on the pageComing next | What the form is forName the integrations that cost the most |
If two rows are true, register for both. Do the row that hurts every week first. A company that wants a payroll file and a frontline phone screen is not choosing a platform. It is naming two jobs.
Nest first
Choose Nest when the buyer is a Workday director or HRIS admin and the pain is the team’s own queue. The page is a team of eleven specialists. You tell Kai the goal. He plans it and hands the parts out: core HCM, Financials, payroll, benefits, compensation, absence and time, recruiting and talent, reporting, integrations (including Studio and Extend), and security. You choose who joins.
The control that matters for a buyer: nothing changes until you approve it. Production asks every time, after a lower tenant. Routines only read. Colleagues send requests that arrive as tickets. The page’s price, for when it is on sale, is $999 per seat per month, one seat at least, with 20,000 Kiweely Credits a month in a shared balance. There is no free Nest plan. The start is a 30-day pilot whose $999 counts toward an annual contract, arranged with Kiweely. Until then the page says it is not open for download, so the action is a demo, not a download button.
Do not pick Nest first if nobody inside HRIS is waiting, and the real request is “let every employee ask Claude about their PTO.” That is Bridge. Do not pick Nest first to get a carrier file unattended tonight. Nest can include a technical specialist, and it is still coming next. A running integration platform is Roots, also coming next. Work that has to happen in Studio this week is Vine, which is live.
Bridge first
Choose Bridge when the audience is the whole company and the surface is an AI assistant they already open. The page is explicit: every employee, and the Workday and IT team that governs access. Claude, ChatGPT, and Gemini. Mac, Windows, web, and phone. No install on the laptop. The employee signs in on Workday and the call uses that person’s security.
Buyers who are comparing contracts can read the published bands without treating them as a live SKU: $499 a month up to 1,000 employees, $1,499 from 1,001 to 5,000, $3,999 from 5,001 to 20,000, quote above that, unlimited calls, Production and every sandbox and implementation tenant included. One person on their own Workday developer tenant is free, with sample data, no trial cutoff, and no card. A company tenant is still interest on the page, because Bridge is coming next.
Choose Bridge before Leaf when the deliverable is a sentence or a confirmed change in the assistant. Choose Leaf before Bridge when the deliverable is a layout. Choose Roots before Bridge when the deliverable must run at 1:00 a.m. with no one in the chat.
The interest form asks which assistants and which hosting you expect: Kiweely Cloud, a dedicated instance, self-hosted, or not sure yet. You can answer “not sure yet.” That is a better registration than a guessed architecture.
Leaf first
Choose Leaf when HRIS already knows the screen Workday does not have. The page’s examples are a single employee page for pay, time off, benefits, and onboarding; approvals in Teams, Slack, DingTalk, or Lark; a manager view of headcount and who is out; and a phone screen with three large actions in the worker’s language.
The buyer is usually the HRIS admin, not a developer. The page says you connect one Workday API client and describe the screen. Employees later use a Kiweely Leaf phone app, separate from the live Kiweely phone app that follows Vine and Nest. Your own developers’ web apps can appear as tiles. There is no price on the page. Do not wait for one. The form asks for the screens and the channel: browser, DingTalk, Feishu, or Lark, Teams or Slack, the Leaf phone app, several, or not sure yet.
Choose Leaf first if a frontline or manager experience is the reason you are looking. If the same project is really “answer questions in ChatGPT,” register for Bridge instead, or for both if you truly need both shapes.
Roots first
Choose Roots when the cost is an integration that breaks, not a screen that is ugly. The page is an integration platform outside the tenant. Agents design, build, test, and maintain the integration with you. You describe it. It is tested on Sandbox. Nothing reaches Production until you switch it on. The systems it names are payroll providers, benefits carriers and 834 files, Okta, Microsoft Entra ID, ServiceNow, NetSuite, Snowflake, and SFTP.
The operating rules are part of the buying decision. Payroll, benefits, and tax fixes wait for you after they are proved on Sandbox with the failed rows. Directory and reporting feeds can be repaired and turned back on, then the owner is told. You can move an integration between those two rules. Data is not kept after the run. Each integration has its own API client, scoped to what it reads. Hosting is Kiweely’s or yours on AWS, Azure, or Google Cloud.
There is no price and no date. The interest prompt is which integrations cost the most today. Answer with those names. A registration that says “all of our integrations” is harder to sequence than “the carrier file” or “joiners to the identity system.”
Do not register for Roots first if the integration must stay inside Workday Studio and someone needs it built now. That is Vine. Do not register for Roots first if the in-house team wants a specialist to own tickets and Studio work under an approval queue. That is Nest, coming next, and it is a team, not the runtime that sends last night’s file.
Vine is not an interest form
If the blocked person is a consultant, an Extend developer, or an admin who needs a business process, a report, security, an EIB, or a Studio integration changed in a tenant you already have, Vine is the product that is live. It runs on Mac and Windows, asks before it writes, and tests as the people who will use the change. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month. The pricing page adds the firm figure: $149 per seat a month.
Coming-next products do not backfill that job. Bridge, Leaf, and Roots sit outside the tenant and assume the fields and processes they call already exist.
What not to do
Do not register for all four coming-next products to “get in line,” with no job attached. The pages ask for different facts: Nest wants a demo of your Workday work, Bridge wants assistants and hosting, Leaf wants screens and a channel, Roots wants the expensive integrations. A blank registration does not tell Kiweely which early access helps you.
Do not treat a published price as a ship date. Nest and Bridge show prices so a buyer can see the shape of the offer. Their pages still say coming next. Leaf and Roots show neither price nor date. None of the four has an order button.
Do not pick from a feature list that crosses jobs. MCP on Bridge and on Roots is how an assistant reaches that product. It does not make Roots a substitute for employee chat, and it does not make Bridge a payroll run.
Frequently asked questions
We only have time to talk to one team. Which form?
The row in the table that matches this month’s blocked job. If employees are pasting Workday exports into chat, Bridge. If the floor will not use Workday’s screens, Leaf. If a feed fails and someone is on call, Roots. If HRIS cannot get through its own queue, Nest. If a builder is blocked today, Vine, and there is no form to wait on.
Can we register for Bridge and Leaf together?
Yes. They serve different moments. Bridge is the question in an assistant. Leaf is the screen or the phone action. The pages do not make one a prerequisite for the other.
What if we are still implementing Workday and have no Production tenant?
Bridge’s page says a company still implementing Workday pays its employee-band price for its implementation tenants, once the product is sold, and that non-production tenants are included. That is a pricing fact on a coming-next page, not a statement that Bridge is available in your implementation tenant today. Roots is tested on Sandbox before Production, and it is also coming next. For work you need done in the tenant now, Vine is the live product, including on a personal developer tenant.