Five groups touch one Workday tenant, and Kiweely gives each group its own product. Kiweely Vine is live today for consultants and developers. Kiweely Nest, Kiweely Bridge, Kiweely Leaf, and Kiweely Roots are coming next: the in-house Workday team, employee questions in Claude, ChatGPT, and Gemini, custom screens for the workforce, and integrations that run between Workday and the systems around it. None of them replaces Workday as the system of record. You can use one without buying the others.
An earlier note covered Vine, Nest, Bridge, and Leaf and left Roots off the map. Roots is the fifth job: a new integration platform outside the tenant, where agents design, build, test, and maintain integrations with you. Its page says Coming next, publishes no price and no date, and the way to start is to register interest.
The five jobs
| Product | Status on its page | Who it is for | The job | Where to start |
|---|---|---|---|---|
| ProductKiweely Vine | Status on its pageLive today | Who it is forWorkday consultants and developers | The jobBuilds, configures, and tests in the tenant, and asks before anything changes | Where to startMac and Windows. See Vine |
| ProductKiweely Nest | Status on its pageKiweely Nest is coming next | Who it is forIn-house Workday directors and admins | The jobEleven AI specialists. Tell Kai the goal. Nothing changes until you approve it | Where to startNot open for download. Book a demo |
| ProductKiweely Bridge | Status on its pageKiweely Bridge is coming next | Who it is forEvery employee, governed by the Workday and IT team | The jobWorkday inside Claude, ChatGPT, and Gemini | Where to startRegister interest |
| ProductKiweely Leaf | Status on its pageComing next | Who it is forIn-house HRIS teams, then the whole workforce | The jobScreens in your design, on live Workday data | Where to startRegister interest |
| ProductKiweely Roots | Status on its pageComing next | Who it is forIn-house HRIS and integration teams | The jobIntegrations outside the tenant, built and kept running with agents | Where to startRegister interest |
The ecosystem page uses the same split: Vine is live today, and Nest, Bridge, Leaf, and Roots are coming next. The Kiweely phone app is also live today, as a companion for Vine and Nest. It is not the Kiweely Leaf phone app, which is a separate app for employees and is coming next with Leaf. Other names on that page are marked as being explored, with no promise to ship.
Vine, live today
Vine is a desktop AI agent for Mac and Windows. It signs in to your tenants as you and does the Workday work you would do yourself: configuration and business processes in any task screen, security, reports and calculated fields, EIB data loads, Studio integrations, Orchestrations, and Extend apps, including on a Workday Open Developer account. It tests the work as the real people who use it and writes the design documents. By default it asks before any change, and you can see the client, the tenant, and the parameters before anything is written.
Vine leaves Production to you. Nest’s page states that contrast directly: Nest can work in every tenant, Production included, after you approve; Vine leaves Production to you.
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. On the pricing page, a company’s or a client’s tenant is $99 a month for one person, or $149 per seat a month for a firm. A personal Workday developer tenant stays the free starting point.
Nest, coming next
Nest is for the people who run Workday inside one company. The page describes a team of eleven specialists. You tell Kai the goal. He is the solution architect: he reads the tenant, makes the plan, and hands each part to a specialist covering core HCM, Financials, payroll, benefits, compensation, absence and time, recruiting and talent, reporting, integrations (Studio and Extend), and security. You choose who joins.
Nothing changes in the tenant until you approve it. Each approval shows what it is now and what it will be after. A change is built and tested in a lower tenant first. Bringing it to Production needs your recorded approval. A routine only reads and posts what it found. Any change it wants waits for you. The approval record says who approved it, when, and what changed.
Nest is not open for download. The page says the way to start is to book a demo. The published price, for when seats are on sale, is $999 per seat per month, with 20,000 Kiweely Credits a month in the company’s shared balance. There is no free or personal Nest plan. A 30-day pilot’s $999 counts toward an annual contract, and Kiweely arranges the pilot with you. Credits are the page’s own limit: at 80 percent Kai tells you once; at the limit, routines pause.
By default Nest uses your Workday sign-in in every tenant. You can give one specialist a different sign-in for one tenant, including an integration system user that can sign in to Workday.
Bridge, coming next
Bridge puts Workday inside Claude, ChatGPT, and Gemini for every employee, on Mac, Windows, the browser, and the phone. The Workday and IT team governs it. The page calls it one MCP connector, set up by an AI admin agent, with zero stored data. It does not need a Workday AI agreement, Agent System of Record, or Flex Credits.
Employees sign in on Workday. Bridge uses a user-delegated API client from the Register API Client task (Authorization Code Grant with PKCE), not an Integration System User. Every call runs under that worker’s security groups and domains. Reach on the page is REST, live WQL discovery, SOAP reads, custom RaaS reports, and admin-approved tasks. Reads are the default. Admins turn on writes one by one. Disabled tasks are absent from the tool list. An enabled write pauses for a browser card that shows now and after. The employee’s Workday password and MFA factor stay on Workday’s sign-in screen.
Custody claims on the page: no database of employee Workday tokens; each grant is sealed with AES-256-GCM and decrypted only in memory; responses stream through memory; logs keep timestamp, tenant ID, tool name, HTTP status, and latency. Hosting is Kiweely Cloud, a dedicated worker with a static outbound IP, or a self-hosted container in AWS, GCP, Azure, or Kubernetes.
Price on the page, per company per month, unlimited calls, Production and every non-production tenant included: $499 up to 1,000 employees, $1,499 from 1,001 to 5,000, $3,999 from 5,001 to 20,000, and a quote above 20,000 or for dedicated or self-hosted. One person on their own Workday developer tenant is free, with no trial cutoff and no card. That tenant holds sample data. Bridge is still coming next, so a company tenant starts as interest on the Bridge page, not as a live rollout.
Leaf, coming next
Leaf is the screen layer outside Workday: any employee experience, in your design, on live Workday data, in the browser, in Teams, and on the phone. The page’s examples are an employee page for pay, time off, benefits, and onboarding; approvals in Teams, Slack, DingTalk, or Lark; manager views for people who rarely open Workday; and a phone screen with three large actions in the worker’s language.
You connect the tenant once with one Workday API client, then describe the screen. Nothing reaches employees until you publish. Security lines on the page: zero HR data at rest; every call runs as the signed-in employee; no Workday Extend license, because it uses standard APIs from outside the tenant. Kiweely stores layouts, branding, and connection settings, not worker, compensation, or payroll records. A web app your developers host can be a tile in the Kiweely Leaf phone app, and those Workday calls still run as the signed-in employee.
The Leaf page publishes no price and no date. The way to start is the interest form: which screens, and which channel.
Roots, coming next
Roots is not another name for Studio, EIB, or Nest’s technical specialist. It is a platform outside the tenant. It reaches Workday through Workday’s standard APIs and connects Workday to the systems around it: payroll providers such as ADP and UKG, benefits carriers through 834 files and carrier APIs, identity and IT systems such as Okta, Microsoft Entra ID, and ServiceNow, and finance and data systems such as NetSuite, Snowflake, and SFTP files. Anything with an API or a file, in both directions, is the page’s scope.
You describe the integration. Roots reads both sides, builds it, and tests it on Sandbox with real data before anything touches Production. You switch it on. Nothing reaches Production until you say so. Each integration then runs as tested code. Agents design, build, test, and fix that code. They do not sit in the path of the data on every run.
When a run breaks, you choose the rule per integration. Payroll, benefits, and tax fixes are proved on Sandbox with the rows that failed, then wait for your approval. Directory and reporting feeds can be fixed, tested, and turned back on, with a note to the owner afterward. Every change shows before and after and can be reversed in one step.
Workday data passes through and is gone when the run ends. The page’s four facts: held only in flight; each integration has its own API client, scoped to what it reads; hosted by Kiweely or in your AWS, Azure, or Google Cloud; the run record is times, counts, and outcomes, never the records. Claude, ChatGPT, and Gemini can reach Roots over MCP, as the person asking, to check a run, start one, or ask for a change.
The Roots page publishes no price and no date. Register interest and name the integrations that cost the most today.
What shares a tenant, and what does not
A report or a business process is still built inside Workday. That is Vine today, or Nest when the in-house team wants the work done under approval. Bridge can then answer from what that employee is already allowed to see, and Leaf can place the same facts on a screen. Roots is the file or API that runs when nobody is in the chat: payroll changes, a carrier file, a joiner in the identity system.
Bridge’s page says it needs neither Vine nor Nest. Leaf does not need them either. Roots does not replace Studio. Vine still builds Studio integrations in your own Studio when that is where the integration should live.
Frequently asked questions
Which of the five can I use this week?
Vine, on Mac and Windows. Nest, Bridge, Leaf, and Roots are coming next. Nest is not open for download. Bridge, Leaf, and Roots take interest on their own pages. The Kiweely phone app is live as the companion for Vine and Nest.
Do I need all five?
No. Each product has its own page and its own start. Pick the job. A consultant who needs Extend or Studio work starts with Vine. A company that only wants employees to ask Workday questions in chat registers interest in Bridge.
Why is Roots not part of Nest or Bridge?
Nest’s technical specialist can work on integrations, Studio, and Extend as part of the in-house team, and that product is coming next. Bridge answers a person who is asking. Roots runs the integration itself, outside the tenant, on a schedule, and keeps no Workday records after the run. Those are different jobs, so they are different products.
Where are the prices?
Vine’s prices are on the pricing page. Nest and Bridge publish prices on their pages even though both are coming next. Leaf and Roots do not publish a price, a date, or an order button.