Skip to main content

v0.1.0

Release date: 2026-07-24


Summary

Factor Fifty v0.1.0 introduces a new executive overview with customer budgets and forecasting, security remediation tracking, historical savings insights, and reliability improvements across cloud imports and deployments.

Executive Overview and Budgets

  • Executive overview — a consolidated view of spend trends, savings impact, cost drivers, optimisation opportunities, security posture, and NIS2 readiness.
  • Customer budgets — executive budgets can be configured and monitored from the overview.
  • Budget health — current spend and forecast are presented against the configured budget to highlight risk early.

Financial Dashboard Improvements

  • Monthly forecasting — projected spend is calculated from the cost posted so far in the current month.
  • Period comparisons — spend changes are easier to understand through consistent comparisons with previous periods.
  • Provider and currency consistency — cost and savings figures are presented more consistently across AWS and Azure views.

Security Remediation Workflow

  • Track remediation work — findings can be assigned and moved through open, in-progress, resolved, and accepted-risk states.
  • Document accepted risk — teams can record a reason and expiry date when accepting a security risk.
  • Clear ownership — assignees and remediation status make follow-up work visible to the wider team.

Rightsizing and Savings

  • Historical savings — review realised savings over time and inspect the resources behind the totals.
  • Improved exports — expanded PDF and Excel exports support sharing and offline analysis.
  • More reliable recommendations — provider-aware validation and calculation improvements make recommendations and savings figures more dependable.

Canvas, Imports, and Deployment Reliability

  • Existing-cloud adoption — improved import mapping makes it easier to bring existing infrastructure into Canvas.
  • Safer validation — stronger dependency, field, and Terraform import ID checks surface configuration issues earlier.
  • More reliable processing — queue routing and deployment pipeline improvements reduce failures during imports and deployments.