Read-only by design. Hosted where you need it.
ARKYPEL runs as one collector inside your perimeter. It reads the records your network already keeps and observes industrial zones without touching them. Analytics and the console run on your site, in the ARKYPEL cloud, or fully air-gapped. Here is exactly what it needs, and what it never does.
Four commitments, built into how it works.
We read. We never write.
Every integration uses a read-only account, role or API token your IT team already knows how to issue. ARKYPEL changes nothing in your systems.
Hosted where you decide.
On premises, in the ARKYPEL cloud, or fully air-gapped. On premises and air-gapped, nothing leaves the site.
No agent required.
One collector VM and read-only access are enough to start, with no network change. Traffic capture is optional and limited to the segments you choose.
Observed, never probed.
Industrial zones only ever see passive observation. ARKYPEL never sends an active packet to an industrial device.
One collector on your site. Three ways to host the rest.
What we ask your IT team for. All of it read-only.
Credentials, not cabling. Each source is optional: the more of them ARKYPEL can read, the more witnesses each asset has.
| Source | Access | What it is read for |
|---|---|---|
| Switch tables | SNMP, read-only. | MAC address, Switch, port, VLAN, ARP (IP to MAC), LLDP / CDP neighbors |
| Directory | LDAP, read-only account. | Computer objects, Operating system and version, Last logon, Organizational unit, Service accounts |
| DHCP | Lease export or read-only API. | Lease, Hostname, Vendor class, Requested options |
| Hypervisor | Read-only role. | Virtual machines, Hosts, Guest OS, Port groups |
| Wi-Fi controllers and RADIUS | Read-only account or log export. | Associated clients, SSID, 802.1X identity |
| Vulnerability scanners | Read-only API token. | Scanned hosts, Open services, Findings |
| IT service management | Read-only API token. | Declared assets, Owner, Business service |
| Endpoint security | Read-only API token. | Managed endpoints, Agent health |
| Network capture (optional) | Targeted SPAN or TAP on chosen segments. | How devices behave on industrial segments or zones with unknowns. |
The full list of systems ARKYPEL reads, with what each one tells us, is on How Discovery works.
Ordered by cost and safety. Each zone gets only what it can take.
ARKYPEL starts with what is already recorded, then observes, and only asks where doubt remains. What it is allowed to do depends on the zone.
| Method | IT zones | Industrial zones |
|---|---|---|
| Read existing recordsSwitch tables, directory, DHCP, virtualization, your tools. | Yes | Yes |
| Passive observationIdentify devices from how they already talk. Nothing is sent. | Yes | Yes |
| One targeted questionOne lightweight query per uncertain IT device, then stop. | Yes | Never |
| Credentialed inspectionOnly on the servers you explicitly authorize. | Authorized servers only | Never |
The order is about cost and safety, not about which method matters most. Records, observation and targeted questions run as one loop.
From one VM to a living inventory.
- 1
Deploy one collector VM
In your environment, air-gap capable.
- 2
Issue read-only access
An SNMP user, an LDAP reader, a read-only hypervisor role, API tokens for your tools.
- 3
First inventory
Every asset with its type, location, confidence and the sources that saw it.
- 4
Continuous collection
The inventory stays current, cycle after cycle.
On premises
Runs inside your perimeter, no outbound dependencies.
Cloud
Only the collector runs on your site. Analytics and the console are hosted in the ARKYPEL cloud.
Air-gapped
Operates without internet egress. Updates flow in through a controlled channel.
What your security team will ask.
Something not covered here? Write to us and we will answer in detail.
Do we need to install anything on our endpoints?
No. ARKYPEL works without agents: one collector VM in your environment reads the systems you already have.
Can any of the accounts you ask for change our systems?
No. Every account we ask for is read-only: an SNMP read-only user, an LDAP reader, a read-only hypervisor role, read-only API tokens. Your team issues and revokes them.
Does any data leave our network?
That depends on the deployment you choose. On premises and air-gapped, no: the collector, analytics and the console all run on your site, and air-gapped sites receive updates through an offline, controlled transfer. In the cloud deployment, the collector sends the inventory it builds to analytics hosted in the ARKYPEL cloud. In every case, it only ever reads your systems.
What happens in our OT and industrial zones?
They are observed, never probed. ARKYPEL reads records and listens passively where you allow it. It never sends an active packet to an industrial device, and it never asks a question there.
Do we need to change the network or install taps?
Not to get started. Records and passive signals cover most of the estate. Traffic capture is optional and targeted: a SPAN or TAP on the segments you choose, typically industrial segments or zones with unknowns.
How do we check what ARKYPEL concluded?
Every asset carries its evidence: the sources that saw it, its location (switch, port, VLAN) and a confidence score. When a device cannot be typed, ARKYPEL says so and gives the reason.