Read the employment record
Workers, status, termination dates, departments, and the application entitlements Rippling already holds. This half is always available and needs no vendor credential.
Stop paying for seats nobody uses
Rippling knows who works here and what they were given. It does not know whether any of it is being used. Sluice joins those two halves, prices the gap, and reclaims the seat through Rippling — so the de-provisioning lands in the same audit log as the hire.
Read-only against every vendor. Sluice never revokes on the vendor side — only through Rippling.
Workers, status, termination dates, departments, and the application entitlements Rippling already holds. This half is always available and needs no vendor credential.
Ten connectors read activity directly from the vendor, read-only. Where a vendor exposes nothing, Sluice says so on the finding rather than guessing.
The holder is asked before anything is taken away. Revocation goes through Rippling's group exclusion, so the change is executed and recorded where the rest of their access lives.
Every tool in this category reports a number. The difference is whether you can act on it.
Seven of the ten vendors have seats that cost nothing despite looking provisioned — Slack's fair billing, a free Zoom Basic licence, a Datadog account on a per-host contract, a Salesforce user already deactivated. Those findings still appear as an access risk, priced at zero. The recoverable total is money you can actually stop spending.
Where a vendor exposes no activity data, the finding says so instead of inferring disuse. A revocation proposal built on a missing field is how somebody loses access they still need.
Auto-apply is off by default and, when enabled, is limited to findings that are provable from Rippling alone. Everything else waits for a person. The copilot stops at a preview and cannot complete a write.
Roles resolve from Rippling group membership on every request. Remove someone in Rippling and they lose Sluice immediately — a tool built to find orphaned accounts should not create one.
Some sources need an enterprise plan on the vendor's side. Sluice reports which, per connector, rather than failing quietly.
Metered on seats under management, not headcount — so a customer who acts on the findings meters fewer seats next month. That is the whole shape of it: the better this works for you, the less it costs.
We price per deployment rather than publishing a rate card, because what this is worth depends on how many seats you are carrying and how much of the waste is recoverable. Tell us roughly how many people you have in Rippling and which vendors you pay for, and we will come back with a number and the reasoning behind it.
No per-user minimum, no charge for the people Sluice finds nothing wrong with.