Where we are going
Direction, stated as trajectory rather than dated promises.
This page is direction, not a roadmap with dates. Dated roadmaps become commitments customers plan around and vendors quietly miss. What follows is the trajectory the platform is built to move along without re-architecture.
Continuous controls monitoring as the default
The industry is moving off point-in-time snapshots toward continuous validation. Watchtower's durable-findings model is already that shape: the question is always the current state of every condition and its history, not the result of the most recent scan. The direction is to deepen this: more frameworks maintained as living data, richer drift reasoning, and compliance content that stays machine-readable and standards-alignable rather than proprietary.
Verifiable by someone who does not trust us
Today the audit trail is verifiable by you. The direction is external anchoring: periodically committing chain digests to an independent third party so the trail is verifiable by someone who trusts neither you nor us. The audit model was designed so this can be added without rebuilding it, and it ships when a customer's assurance regime calls for it.
The write path stays narrow on purpose
Restore, templates, and change modeling already converge on one signed, audited primitive. As the platform does more on the write side, that convergence is a constraint we keep, not one we relax. The differentiator will continue to be that every change is provable and reversible, not that more of it happens without you.
Root of trust moving toward the customer
Self-hosting already keeps your data in your boundary. The direction is to push the root of trust further toward you, including customer-held key custody, so that even the platform operator's reach over your most sensitive material shrinks over time rather than grows.