Having used the platform extensively, this reviewer appreciates that Draftt transforms technical debt into actionable fixes with clear ownership and importance. There are still gaps in coverage, requiring reliance on manual checks for some areas.
View Full ReviewWe've been running Draftt for over a year across our cloud environments. The part that actually changed how we work is the tech debt side. Before, tracking what was end-of-life or heading there (managed services, database engines, runtimes, images) meant someone sweeping each environment by hand and dropping the results into a spreadsheet that was stale within a week. Draftt keeps that list current on its own. The bigger win for us is prioritization and ownership. It tells us which findings actually matter and which team owns them, so the work lands somewhere instead of sitting in a shared backlog nobody picks up. Review collected by and hosted on G2.com.
Nothing major. Early on the volume of findings was more than we could act on at once, but that was mostly us catching up on a backlog we'd been ignoring for a while, and the prioritization made it manageable. Review collected by and hosted on G2.com.
Honestly the biggest thing for me is not having to track EOL stuff in spreadsheets anymore. We manage a bunch of EKS clusters and between Kubernetes versions, certs, Terraform modules and everything else, something was always sneaking up on us and becoming urgent. Draftt just shows all of it — what's expiring, what it'll cost us if we sit on it (the extended
Setup was quick and also the team is great — we asked
for a couple of things and they actually showed up in the product a few weeks later. Doesn't happen a lot with vendors. Review collected by and hosted on G2.com.
we still have a couple of things that are still on the roadmap and we have yet to use Review collected by and hosted on G2.com.
Pricing provided by Draftt.
