Skip to content
Trust · Security

Security and privacy for skill data you can act on.

Pilots should not require a leap of faith.

Here is what is true today: AWS-hosted infrastructure, a DPA for pilots, and SSO when you are ready for a larger rollout.

What is true todaySecurity whitepaper

Narrow scope first. Broader controls when you need them.

What is true today

Here is what a pilot actually runs on.

Cloud foundation

Application and data run on AWS. Access is scoped; credentials are not logged in plain form.

Identity

SSO (SAML/OIDC) is available for larger rollouts. Pilots can start without enterprise IdP wiring.

Data agreements

For pilots we sign a DPA and limit scope. You control which teams and paths enter the system first.

A secure remote workstation
Enterprise-ready honesty

Narrow scope first. Broader controls when you need them.

A pilot should not require a leap of faith. Start with a DPA and limited teams, then add SSO and deeper architecture review as the rollout grows.

Security, Privacy & Architecture whitepaper

Architecture, privacy controls, and operational detail will be covered in a whitepaper. It is coming soon.

Coming soon
Start narrow

A pilot you can approve without a leap of faith.

Sign a DPA, limit scope, and add enterprise identity only when you need it.

Start a pilot
AWS-hostedDPA for pilotsSSO when ready