Security teams rarely argue about the mapping. They argue about the network the mapping runs on. Kiweely Roots (coming next) publishes two answers and no others: hosted by Kiweely, or in your own AWS, Azure, or Google Cloud.
The two places a run can live
| Kiweely’s cloud | Your AWS, Azure, or Google Cloud | |
|---|---|---|
| Who runs the integration | Kiweely’s cloudKiweely | Your AWS, Azure, or Google CloudYou, on a cloud account you already operate |
| What the page says is kept after a run | Kiweely’s cloudNothing. Times, counts, and outcomes only | Your AWS, Azure, or Google CloudThe same sentence. The host does not change it |
| Workday access | Kiweely’s cloudEach integration has its own API client, scoped to what it reads | Your AWS, Azure, or Google CloudThe same |
| When it fits | Kiweely’s cloudThe review accepts a vendor-operated integration platform that does not retain the records | Your AWS, Azure, or Google CloudThe review requires the process to run inside a network you control |
Both options are the same product. Agents still design, build, test, and maintain the integration with you. The integration still runs as tested code. Sandbox still comes first. Payroll, benefits, and tax fixes still wait for your approval after they are proven on Sandbox. Directory and reporting feeds can still be fixed and turned back on with a note to the owner. You can still move any integration between those two rules.
The data path does not pick up a database because you changed hosts. Nothing kept after a run means read, sent, and deleted inside the run, in either place.
When the review says “VPC”
A review that says the integration has to run inside a VPC you control is asking for the second column. Your AWS, Azure, or Google Cloud is the published way to put the run on your side of the account boundary.
The Roots page does not go further than that sentence. It does not describe a peering product, a private-link attachment, a dedicated tenancy, a fixed outbound address for an allow list, or a Kubernetes layout. It does not publish a price, a region list, or an install guide. Those are questions for the interest form, not features you can hold the page to.
Use this split when you write the review answer:
- If the requirement is “no copy of HR data at rest in the vendor,” both columns match the published retention rule. Confirm the host with whoever has to sign.
- If the requirement is “the process runs in our cloud account,” choose your AWS, Azure, or Google Cloud.
- If the requirement is a specific network control the page does not name, say so in the interest form. Do not assume the customer-cloud option includes it.
Workday’s own integration tools stay inside the tenant, on Workday’s cloud. That is a third place, and it is not Roots. Roots is outside the tenant and reaches Workday through standard APIs. Choosing Roots does not move Workday. It chooses where the integration between Workday and the other system runs.
What you are not choosing
You are not choosing whether an agent sits on the live file. The page says no: the run is tested code. You are not choosing a different retention rule per cloud. You are not choosing a price. The page has none.
You are choosing who operates the place the run passes through, and you are telling Roots which integrations cost you the most today. Register interest on the Roots page. It is coming next. Early access is a note back to you, not a tenant you can turn on this week.