Axis/Vault
Should be created as a central register for hardware, licenses and life cycles.
- Test assets and locations
- Design assignment and values
- Show license periods
Entire product in development · not yet ready for market
Early development preview · no finished or available software
AxisOne
AxisOne is created as a platform that will bring together inventory, monitoring, software lifecycle and vulnerability work in a multi-client capable system. The views shown are solely an early foretaste of ongoing development and do not represent a finished, market-ready or already available product.
4 module prototypesearly views of Vault, Pulse, Edge and Flare
Common conceptOrganizations, roles and access in the design
Not finished yetProduct development, testing and validation are ongoing
Assets and Licenses
Early prototype Dark modeDesign prototype in light and dark
A taste of two work environments.
The images show what a later product surface could look like in light and dark representation. Both variants are part of the ongoing development and testing status, not the view of a finished application.
Early module prototypes
Four directions of development. A planned system.
Vault, Pulse, Edge and Flare show examples of how organizations, roles and information should later interact. Functions, scope and surfaces can change significantly as the project progresses.
Axis/Pulse
In the future, availability, signals and alarm routes should be classified together.
- Try SNMP and connectors
- Develop metrics and thresholds
- Design alarm routes
Axis/Edge
Intended to bring together software inventory, endpoints and update requirements.
- Model devices and versions
- Test lifecycle and end-of-life
- Develop patch and CVE coverage
Axis/Flare
Should connect vulnerability information with the inventory maintained later.
- Check NVD and OSV data
- Try prioritization
- Develop alert workflows
Foretaste of development
Scroll through early module views.
Each step first opens a filled product image with three assigned explanation points. The short operating video can then be switched on consciously. All data is fictitious; The views are neither final nor proof of market readiness or availability.
AxisOne · early development prototype · Vault
Assets and Licenses
In this way, every asset could maintain its inventory, location and life cycle.
The prototype tests a planned registry for hardware, procurement value, location, status and license context.
- 124 populated demo assets
- 258,260 euros documented inventory
- 3Status, location and delivery times
Monitoring and alerting
In this way, measured values could become a prioritized operating state.
The prototype tests how devices, availability, local connectors and open alarms could later be classified together.
- 118 monitored demo devices
- 2Locations and connector status
- 3Thresholds, maintenance and escalation
Endpoints and patch planning
In this way, existing software could become a controllable update.
The early view tests the planned connection of endpoints, products, versions, lifecycle and open patches.
- 116 populated demo endpoints
- 2Software and version inventory
- 3Patch requirements and CVE reference
CVE Intelligence and Security
In this way, weak points in your own inventory context could become visible.
The prototype explores how NVD and OSV data, severities and affected software could later be merged.
- 1129 CVE entries in the demo state
- 2CVSS based prioritization
- 3Alerts with work status
Entire project under development
The path to a sovereign security platform.
AxisOne as a complete product is not yet finished. The following points describe the desired development result. The module views shown previously are also early prototypes within this project and are not already available series modules.
An IT/OT data model
Assets, machines, controls, software and their relationships should be brought together in a consistent model. Axis/Atlas forms the planned CMDB foundation for this.
Local, sovereign AI
The plan is to have our own multi-model operation on AXISPORT hardware with structured, testable results instead of an uncontrolled cloud black box.
Controlled assistance
Future assistants should combine knowledge, security assessments and approved actions. Human approval, least privilege and audit trail remain binding.
Planned Audiences
For operational IT responsibility in medium-sized companies.
In the future, AxisOne will provide support where inventories, statuses, software and security information need to be processed with limited resources. The suitability will be validated during further development and testing.
Internal IT teams
AxisOne is intended to enable a common working environment for devices, locations, software, monitoring and security.
IT service providers and MSPs
Multi-tenant organizations, roles and modules are planned for clearly separated work contexts.
Distributed companies
In the future, locations and endpoints will be visible via connectors and states will be classified together.
Connected work routes
Why the platform is more than four tools.
The benefits arise at the transitions. Information is not exported and later collected again, but remains in the same client and rights context.
01
From device to responsible asset
The prototype tests how connector or master data could later be supplemented with location, assignment, value, status and license context.
02
From signal to processable disturbance
Pulse is testing how accessibility, metrics, thresholds, maintenance windows and alarm paths could work together in the future.
03
From software to security decisions
Edge and Flare will later connect version levels, devices and CVEs to create comprehensible security recommendations.
Mobile development prototype
This is what AxisOne could look like later on the road.
When scrolling, Vault, Pulse, Edge and Flare switch directly in the iPhone. The stage demonstrates the desired responsive operation, but does not represent a finished or already available mobile application.
01Axis/Vault
In this way, every asset could maintain its inventory, location and life cycle.
The prototype tests a planned registry for hardware, procurement value, location, status and license context.
02Axis/Pulses
In this way, measured values could become a prioritized operating state.
The prototype tests how devices, availability, local connectors and open alarms could later be classified together.
03Axis/Edge
In this way, existing software could become a controllable update.
The early view tests the planned connection of endpoints, products, versions, lifecycle and open patches.
04Axis/Flare
In this way, weak points in your own inventory context could become visible.
The prototype explores how NVD and OSV data, severities and affected software could later be merged.
iPhone · Development prototypeIn this way, every asset could maintain its inventory, location and life cycle.
Early responsive prototype in iPhone format
Planned connectivity
Designed for existing data paths.
Connectors, protocols, APIs and notification channels are part of the planned integration concept. Which connections will be included in the finished product will be technically tested and implemented as development progresses.
Monitoring connection being tested
Local inventory as a development goal
Planned structured handovers
Scheduled event delivery
Scheduled notification route
Possible future alarm path
Possible future reports
Data sources in the development prototype
Security concept under development
Think about identity and client separation from the start.
The development prototype tests Auth0, organizational contexts, roles and protected routes. The final security architecture, hardening and testing are part of further product development.
Client separation
The separation of organizational data is tested in the prototype and further secured.
Roles and modules
Authorization models and module access are validated during development.
Central access
Auth0 currently serves as the technical basis for the development prototype.
Frequently asked questions
AxisOne specifically classified.
Is AxisOne already a finished series product?
No. The entire product is under development. Vault, Pulse, Edge and Flare are also only early prototypes and not finished or available series modules.
What do the pictures and videos show?
They provide a non-binding foretaste of the product idea, possible modules and operating concept. Functions, scope, design and technical implementation can change significantly during further development.
Is AxisOne ready to launch or purchase?
No. AxisOne is currently not offered as finished software. All that is possible is a guided insight into the early development prototype.
Can AxisOne replace existing tools?
No, no reliable transfer promise can currently be derived from this. This must only be validated during further development and testing.
AxisOne
Discuss preview Classify the level of development together
We show the early, not market-ready prototype with fictitious data and openly explain the product goal it is pursuing.