What's New
VEKTIS is actively evolving. This page tracks what’s changed with each release — what we shipped, why we built it, and how it helps you get more from your metrics. If something sparks an idea or you’d like to see us take a different approach, we’d love to hear from you.
Coming Soon
Section titled “Coming Soon”We’re always working on what’s next. Check back here for a preview of upcoming features as they enter testing.
March 11, 2026
Section titled “March 11, 2026”Summary
Section titled “Summary”Tracking development metrics is only useful if you can quickly tell whether things are going well — and trust the data behind that assessment. Until now, VEKTIS gave you the raw numbers, but left it to you to interpret whether a metric was trending in the right direction, whether your measurements were reliable, and how much overall impact your development work was having.
This release focuses on three things: giving you clear signals so you don’t have to interpret raw data yourself, protecting the integrity of the measurements those signals depend on, and making the platform easier to navigate as it grows.
We believe that making metric interpretation automatic and visible — rather than leaving it as a manual exercise — will help teams catch issues earlier and celebrate progress sooner. If you see opportunities to improve how we surface these insights, we’d love to hear from you.
In This Release
Section titled “In This Release”Knowing whether you’re on track shouldn’t require digging through data
Section titled “Knowing whether you’re on track shouldn’t require digging through data”The problem: Understanding whether your development work is delivering results means clicking into individual dev items, scanning multiple metrics, and mentally aggregating whether things are trending the right way. At the initiative level, there’s been no way to see the bigger picture without doing that work yourself for every dev item underneath it.
What we’re doing about it: Two new capabilities work together to surface clear signals at different levels of detail — so you can start with the big picture and drill down only when something needs attention.
Health Indicators
- Show the overall health of each initiative based on how its dev items are performing against their metrics
- Performance is weighted directionally — improvements and regressions are scored relative to what “better” means for each specific metric
- Navigate to any initiative to see its current health status and quickly identify which ones need attention versus which are on track
VEKTIS Impact Score
- Gives each dev item a single score representing the measurable impact of its post-release performance
- Metrics are evaluated using a dual-track scoring system — one track for metrics that are improving and another for those that are regressing
- Scores are grouped into zones so you can quickly understand the magnitude of impact
- View the score on any dev item’s detail page
Your metrics are only as good as the measurements behind them
Section titled “Your metrics are only as good as the measurements behind them”The problem: Baselines are the foundation of every health indicator and impact score. But early measurements can be volatile, measurement cadences can drift without anyone noticing, and not every metric fluctuation is meaningful. When the underlying data isn’t trustworthy, the signals built on top of it aren’t either.
What we’re doing about it: Three new safeguards work together to protect measurement quality — so you can trust the signals VEKTIS surfaces.
Burn-in baseline freeze
- Built for situations where baseline measurements weren’t possible before development — such as entirely new functionality that didn’t exist before or features too complex to measure prior to release
- When a dev item is released without baselines, VEKTIS collects your first few post-release measurements and uses them to establish a baseline automatically — so impact scoring can still work even without historical data
- While we encourage teams to track baseline data wherever possible — even through indirect measures like time-to-complete-a-task before and after development — burn-in ensures you’re never stuck without a scoring foundation when that isn’t feasible
Measurement regularity warnings
- Alerts you when your baseline measurements are being taken at irregular intervals
- Prompts you to establish a more regular cadence if timing between measurements is inconsistent
- Catching irregularities early helps you build habits that lead to more reliable data over time
Minimum meaningful change
- Define the threshold of metric change that actually matters for each dev item
- Set this value when creating or editing a dev item
- Changes below the threshold won’t be flagged as significant improvements or regressions — filtering out noise so you can focus on real impact
Getting the most out of VEKTIS should be effortless
Section titled “Getting the most out of VEKTIS should be effortless”The problem: As the platform grows with new capabilities, it should be easy to find answers, understand what’s available, and feel oriented — whether you’re a new team member or exploring a feature for the first time.
What we’re doing about it: A combination of documentation, expanded access, and interface refinements designed to reduce friction across the board.
Documentation site
- You’re already here — comprehensive guides and reference material are available throughout this site
- Browse guides on getting started, managing dev items, working with metrics, and more
Team visibility for all roles
- The users list in Settings is now accessible to everyone, not just administrators
- See who else on your team is using VEKTIS to make collaboration and communication easier
Interface improvements
- Notifications and prompts now use clearer, friendlier language throughout
- Clickable elements consistently show a pointer cursor so it’s obvious what you can interact with
- Background colors are uniform across all views for a more polished experience