Aiyoda

Aiyoda App Requirements

Everything you need to deploy and run Aiyoda successfully in your environment.

v3.5 · Updated 2026
📋
Before you begin, make sure your environment meets all minimum requirements below. Aiyoda runs as a .NET Core application on Windows with SQL Server as its data store or JSON/CSV files for exports. Check the firewall rules carefully to ensure successful device scanning across your network.
System Requirements
Minimum System Requirements
🖥️
Operating System
64-bit Windows Server 2019 or Windows 11 (Physical or Virtual)
⚙️
.NET Runtime
.NET Runtime Core 10
🧠
Memory
8 GB RAM minimum
💾
Free Disk Space
128 GB available disk space
Additional Requirements
🗄️
SQL Server
SQL Server 2019 Express Edition (minimum)
🛠️
SQL Management Studio
Required for database configuration & management (SSMS)
🔐
SQL Server Account
Dedicated SQL or Windows account for database access
📊
Power BI Desktop
Required for data visualizations and reporting dashboards
Active Directory & DNS

🏢 AIYODA APP SERVER

The device running the Aiyoda Console must be joined and connected to Active Directory. Device names must be resolvable in DNS for proper communication.

🎯 TARGET DEVICES

All target devices being scanned must have their device names resolvable in DNS. This is required for Aiyoda to locate and connect to them during a scan.

Firewall Rules
🏢 Aiyoda App Server — Outbound
▲ Outbound Rules
TCP 389 TCP 3268
LDAP — Active Directory queries
TCP 135 TCP 139 TCP 445
RPC / WMI — Windows remote management
TCP 22
SSH — Linux / MacOS remote access
TCP 443 /api/AiyodaAuth/authenticate
HTTPS — Must be open to internet for M365 & license verification
🎯 Target Devices — Inbound
▼ Inbound Rules
TCP 445 TCP 139 TCP 135
RPC / WMI — Allow Aiyoda server to query Windows devices
TCP 22
SSH — Allow Aiyoda server to connect to Linux/Mac targets
Network Traffic & File Sizes
< 20 KB
Average inventory output per device scan
Roughly the size of a Word document
💡 What this means for you

Aiyoda has a very lightweight network footprint. Each successful inventory scan produces less than 20 KB of data per device, making it safe to run across low-bandwidth network segments without concern for congestion.

Scan Types
🔍

First Scan

Initiates a complete full inventory scan across for all devices on the network.

🔄

Rescan

Re-initiates a scan targeting only devices that were not successfully inventoried in the previous run.

🗓️

Scheduled Scan

Allows you to define a recurring schedule so that scans run automatically at your desired interval.

Scan Methods
Supported Inventory Scan Methods
Active Directory Discovery
Windows Inventory Discovery
IP Range Inventory Discovery
Hyper-V Discovery
VMware Discovery
SQL Server Discovery
System Center Inventory Discovery
Microsoft 365 Discovery
Workgroup Inventory Discovery
Linux OS Discovery
MacOS Discovery
Credentials Required
Platform Credential Type Notes
Active Directory No credentials required Uses built in .Net libraries to get AD data
Windows Domain admin username & password Existing accounts can be used — no new accounts required
SQL Server Windows or SQL auth username & password Either Windows integrated or SQL Server authentication
Microsoft 365 Entra / Azure AD App Registration Create an App Registration with Microsoft Graph API permissions
MacOS Admin username & password Local admin account on the target device
Linux Admin / root username & password Root or sudo-capable account required for full inventory
VMware Admin / root username & password vCenter or ESXi admin credentials