Where we stand — including what isn't built yet
Capital-program owners and regulated industries need a straight answer on data handling and control, not a marketing page. This is that answer, kept current as Sage's governance layer is built.
Data in transit & at rest
Connections to P6 EPPM and supporting systems are encrypted in transit. Credentials and configuration data are encrypted at rest and never written into prompts or model training data.
Credential handling
P6 EPPM API access uses scoped service credentials, stored in a secrets manager rather than in application code, with rotation supported per client environment.
Scoped access
Sage connects through the same P6 EPPM REST API surface a human integration would use, and is deployed per client instance rather than pooled across customers.
Point-in-time reporting
Every read, write, and recalculation Sage performs corresponds to a specific action a human scheduler could take in the P6 client — nothing happens off-schedule or outside the tool surface.
Current governance status
This is the single most important thing to understand about Sage before any production or regulated deployment.
"Today, when Sage calls a P6 write tool, it executes immediately against the live database — there is no approval step in front of it. Reaching Phase 5 (audit trail, rollback, approval workflows) is what turns a proven operational capability into a governed one, and that work has not started yet."
Common security & governance questions
Yes, today — this is the core governance gap and the reason we're publishing it here rather than waiting for a sales conversation to surface it. Every write in Sage's proof points executed immediately, with no approval step in front of it. Closing that gap with an audit trail, rollback, and approval workflow is Phase 5 of our roadmap, and it has not started yet.
Not yet. We are actively scoping a SOC 2 Type II process as part of our near-term roadmap and will publish status here as it progresses.
Sage is deployed per client environment against your own P6 EPPM instance using scoped service credentials. We do not pool client schedule data into a shared model or shared database.
Because there is no automated rollback yet, recovery today relies on standard P6 practices — baselines, backups, and manual correction by a scheduler. This is precisely why we recommend piloting Sage in a reviewed, human-in-the-loop configuration until Phase 5 governance ships.
Yes — for regulated environments (pharmaceutical CQV, government, mission-critical) we recommend starting with a scoped, reviewed configuration rather than open live-write access, ahead of the full Phase 5 approval workflow.
Want the full technical detail?
Request our security documentation or talk to our team about scoping a governed, reviewed pilot.