Home

Aivana product guide

Find the product that fits your task.

Start with the problem you want to solve. Compare audiences, workflows and requirements, then explore the product or discuss a suitable starting point.

Compare at a glance

Decision support in Azure DevOps

AIVANA Decision Intelligence

Who is it for?
Product owners, project leads and delivery teams
What does it help with?
Investigate release risks, dependencies and acceptance gaps with source evidence; use decision options and seven team widgets.
What do you need?
Azure DevOps Services with the installed extension and current project permissions. Shared history requires an activated team service and explicit roles.
Current scope
Development preview; agree team service activation

Rule-based support without AI in this edition. No automatic release approvals or work-item writes.

Diagrams and architecture decisions

Diagramora

Who is it for?
Development, architecture and process teams
What does it help with?
Turn language, code, SQL and documents into editable diagrams; explore dependencies, scenarios and decisions in the local model.
What do you need?
Local editor or Diagramora plugin in Codex and supported input files. Cloud and collaboration require explicit configuration.
Current scope
Local editor and Codex plugin; optional hybrid cloud deployment

Analysis is based on modeled relationships and metadata, not live monitoring. Local editing does not upload documents automatically.

Document processing and back office

LISA

Who is it for?
Back-office, finance and multi-tenant teams
What does it help with?
Extract documents from email and PDF intake, assign tenants, review data and archive them in a structured way.
What do you need?
Define mailbox or PDF intake, tenant rules and roles. SharePoint and accounting connectors require suitable licences, permissions and configuration.
Current scope
Documented core scope; process automation under development

SharePoint export has no reverse synchronisation. Banking does not include transfers or transaction reconciliation. S-Firm connectivity and payment feedback require additional integration validation.

Project reporting in Power BI

Aivana Project Intelligence

Who is it for?
Project leads, PMO and resource managers
What does it help with?
Review schedules, progress, dependencies and capacity together.
What do you need?
Power BI with suitable project fields, measures and supplied forecasts. Validate the package and deployment conditions for your environment.
Current scope
Confirm package and deployment scope

Analyses supplied report data; does not write to source data.

Financial reporting in Power BI

Aivana Financial Reporting

Who is it for?
Controlling, finance and management
What does it help with?
Compare actuals, budget, forecast and prior year, then explain variances with contextual comments.
What do you need?
Power BI with suitable financial data. Persistent comments additionally require Fabric SQL; configure metadata, certificates and tenant permissions.
Current scope
Documented V1 scope; validate integration

V1 covers the financial matrix and comments. Planning and writeback are extension points.

Financial analysis and scenarios

Aivana Finoryx

Who is it for?
Finance and Power BI teams
What does it help with?
Inspect calculations, compare scenarios and explore targets and actions with explicit assumptions.
What do you need?
Power BI, suitable financial data and scenario assumptions. Validate host acceptance and export permissions.
Current scope
Development release; host acceptance pending

Scenario drafts remain local; source data is unchanged.

Service, projects and delivery

AXYNTORA

Who is it for?
MSPs, software companies and internal IT teams
What does it help with?
Connect service cases, projects and delivery workflows in one shared work context.
What do you need?
Define a specific starting workflow and pilot scope. Validate data sources, Azure DevOps connectivity and other integrations for the intended deployment.
Current scope
In development and expansion; agree pilot scope

The twelve product areas include capabilities under development. Availability is agreed for your deployment.

Remote access and recovery

Relayne

Who is it for?
IT administrators, MSPs and support teams
What does it help with?
Connect remote sessions, diagnosis, clone rehearsals and approved recovery with traceable evidence.
What do you need?
Native Windows workbench. Recovery requires suitable Hyper-V/WinRM infrastructure; Mac VNC requires a trusted LAN or VPN.
Current scope
In development; validate pilot environment

Development distribution is unsigned. Validate compatibility and live acceptance in your environment; Mac VNC is unencrypted.

Medical knowledge workflows

MedGuide Pro

Who is it for?
Medical teams
What does it help with?
Bring together guideline research, structured documentation and specialty learning paths.
What do you need?
Discuss the intended clinical workflow and integration with existing EHR systems.
Current scope
Enquire about the specific feature and deployment scope

The detail page describes the offering. Requirements and availability for your specific use case are discussed together.

Procurement and contract workflows

OrderAI

Who is it for?
Procurement and contract management teams
What does it help with?
Work with contracts, supplier risks, spend and procurement documents in context.
What do you need?
Discuss existing contract and procurement data and the intended ERP integration for your starting workflow.
Current scope
Enquire about the specific feature and deployment scope

The detail page describes the offering. Required modules and integrations are agreed for your workflow.

Compare at a glance

Swipe horizontally to see all columns.

Compare at a glance
ProductWho is it for?What does it help with?Current scope
AIVANA Decision IntelligenceProduct owners, project leads and delivery teamsInvestigate release risks, dependencies and acceptance gaps with source evidence; use decision options and seven team widgets.Development preview; agree team service activation
DiagramoraDevelopment, architecture and process teamsTurn language, code, SQL and documents into editable diagrams; explore dependencies, scenarios and decisions in the local model.Local editor and Codex plugin; optional hybrid cloud deployment
LISABack-office, finance and multi-tenant teamsExtract documents from email and PDF intake, assign tenants, review data and archive them in a structured way.Documented core scope; process automation under development
Aivana Project IntelligenceProject leads, PMO and resource managersReview schedules, progress, dependencies and capacity together.Confirm package and deployment scope
Aivana Financial ReportingControlling, finance and managementCompare actuals, budget, forecast and prior year, then explain variances with contextual comments.Documented V1 scope; validate integration
Aivana FinoryxFinance and Power BI teamsInspect calculations, compare scenarios and explore targets and actions with explicit assumptions.Development release; host acceptance pending
AXYNTORAMSPs, software companies and internal IT teamsConnect service cases, projects and delivery workflows in one shared work context.In development and expansion; agree pilot scope
RelayneIT administrators, MSPs and support teamsConnect remote sessions, diagnosis, clone rehearsals and approved recovery with traceable evidence.In development; validate pilot environment
MedGuide ProMedical teamsBring together guideline research, structured documentation and specialty learning paths.Enquire about the specific feature and deployment scope
OrderAIProcurement and contract management teamsWork with contracts, supplier risks, spend and procurement documents in context.Enquire about the specific feature and deployment scope

A clear starting point, agreed together.

A useful first conversation starts with your workflow. These steps help define a suitable scope before deployment.

01

Describe your task

Bring a specific report, project or operational case. Example data is enough for the initial conversation.

02

Check the environment

Together we review data, systems, permissions and the product capabilities needed for your use case.

03

Agree the next step

Clarify pilot or trial availability, scope, licence terms and acceptance criteria before starting.

Product status and integration limits are shown openly. Availability, introduction and support are discussed for the agreed scope; no fixed response time or deployment date is promised here.

Not sure which product fits?

Tell us what you want to improve. We can help identify a suitable starting point.

Discuss your requirements