Evidence over scores
A number tells you something is wrong somewhere. A quoted sentence with its source tells you what to do. We only ship the second kind.
01Company
Publishing accelerated.
Governance stayed manual.
That sentence is the whole company. Content Governance and DAM started as modules inside Siftly; the work they describe turned out to belong to a different person with a different problem, so we made it a different product.
Why it was split out
A different product, not a different tab.
- 01
Different work
Siftly is about being found. Governance is about what you already published being true.
- 02
Different buyer
The person who owns published risk is rarely the person who owns acquisition.
- 03
Same identity
We kept the Siftly sign-in. Nobody wanted to administer a second account for it.
- 04
Neutral boundary
A standalone tenant, with its own data boundary, that happens to trust the same session.
What we believe
Four positions the product is built on.
Each one costs us something — a simpler queue, a tidier dashboard, an easier demo. We think each one is worth what it costs.
Closure over detection
Anything can flag a page. The hard, useful part is following it until the published page changes and then proving that it did.
02Separation over convenience
Content, assets, and partnerships fail for different reasons and are decided by different people. Merging their queues would be tidier and worse.
03Closed by default
Every integration supplies nothing and sends nothing until an administrator turns it on. Unconfigured means off.
04Nobody has read most of it since the day it shipped.
Come and argue with us.
If you think we have the shape of this wrong, we would genuinely like to hear it.