KANAP is now Kadratis
KANAP is now called Kadratis™. The software, its open source license and the hosting and support offer do not change.
Read the article →Thoughts on AI, IT, and how Kadratis helps CIOs and their teams.
KANAP is now called Kadratis™. The software, its open source license and the hosting and support offer do not change.
Read the article →26.11.1 takes care of your first hour in Kadratis: a guided start in a workspace ready to use, Kad answering your questions about using Kadratis and importing your spreadsheets, and one keyboard-friendly way to create every record. A tour of the release.
Windows Server 2012, SQL Server 2016, Ubuntu 20.04: the end of support date is known, what depends on it rarely is. The Kadratis end of support report names the servers and applications affected, early enough to budget the migration.
A SQL Server Always On, a vSphere farm: describe the cluster once. Where your applications belong depending on the kind of cluster, what the members inherit, and impact views that count right.
26.10.8 adds Excel import / export to every list in Kadratis, making onboarding and bulk data updates easier. A new “History” tab brings the audit log information into each record. Kad gets better. A tour of the release.
SQL Server, vSphere, Active Directory, Entra ID: what runs between your applications and your servers is missing from most IT registries. With a prefilled catalog, Kadratis makes it the link that connects end of support, vulnerabilities, privileged access and costs.
A year after an outage, the auditor or the insurer asks for details. When it started, who decided what, who did what, whether the right parties were notified. An incident register must be able to answer these questions, and it gets you ready for NIS2 at the same time.
26.10.7 lets you limit a person to chosen companies or cost centers, in read or edit, everywhere in Kadratis. Server clusters now host applications and carry connections. A tour of the release.
Every week brings its share of critical vulnerabilities. The real question is: which ones affect your business applications, and who has to act? Kadratis can help, from the published CVE to the recorded decision, including identifying the servers and applications affected.
26.10.6 adds technologies to Kadratis, a layer between applications and servers, and vulnerability management. Published vulnerabilities and end of support now reach the business applications they affect. A tour of the release.
Everyone enters amounts in their own currency, Kadratis consolidates them in the group's: automatic exchange rates, aligned with your budget rates if you wish, and totals you can trust.
Computed deadlines, recorded renewal decisions, commitments compared with the budget: IT contracts under control in Kadratis.
Budget a service the way you buy it, in people, days and prices: Kadratis derives the FTE, the cost per FTE and the daily rate, ready for the committee.
Operating and capital spending in one place: IT builds its budget simply, and comes to the review with finance ready.
Kadratis now ships in numbered, dated versions, about one a month, with release notes and a documented upgrade. Here is what that gives you, and a tour of the product as it stands today.
Business and cyber criticality, data, recovery plan: classifying every application is the work that comes before any NIS2 effort. A method and a tool, without the spreadsheet.
The infrastructure team keeps Netbox current. Kadratis reads it, keeps its asset records in step without retyping, and adds what Netbox does not know: applications, contracts, costs.
The CIO, the project manager, the team lead and the engineer each have their own questions. Kadratis' portfolio reports answer them in one click.
Chargeback says who pays; an analytics dimension says what the spend is for: security, cloud, licences. How to use it in the IT budget.
Allocating IT costs across companies and departments with clear, checkable rules, and turning them into chargeback reports.
The reports that get an IT budget through the committee: key figures, trends, chargeback, then freezing the approved version.
Next year's budget from the expected landing: copy what does not change, preview the copy, then rework only the lines that matter.
Firming up the current year's IT budget landing, item by item, so it becomes a solid base for next year's budget.