SecTeer ships in small, verifiable increments across four components, the agent, the scheduling engine, the backend, and the console. Below is what landed recently, what we're building now, and what we're investigating next.
Because the backend, scheduling engine, and console version separately, a fix to inspection processing does not wait on a console release. In the last six months we published 60+ tagged releases across the stack.
The admin UI, policies, approvals, reporting, and host detail. 14 releases in the period.
APIs, authentication, inspection rules, and tenant management. 28 releases in the period.
Inspection processing, job scheduling, update rings, and history generation. 24 releases.
Authentication, SSO handling, and tenant-level service messaging.
Grouped by the problem it solves rather than by version number. Every item below is live in production today.
A patch that never completes a reboot is never really applied. Restart policy became a first-class object with branding and real-world scheduling.
Manual host grouping breaks the moment your estate grows. Tags now populate themselves.
Coverage work concentrated on WinGet-sourced packages and on giving admins room to customise what ships.
The scheduling engine received sustained performance work across fourteen releases, the least visible and most valuable kind of change.
Keeping the stack current is part of the security promise, not a chore deferred to later.
A long run of fixes aimed at the screens administrators live in every day.
Dated commitments only where we have them. Everything in Exploring is genuinely open, and customer input moves items between columns.
Actively in development, expected within the current quarter.
Scoped and committed, not yet dated.
Open questions where customer input carries the most weight.
The complete log is published for customers in the console under Help → Release notes. Recent highlights:
Looking for something specific, or want a feature considered? Tell us what you need.