The next security layer
starts at the foundation.
The investment thesis for NØNOS: a smaller trusted computing base, explicit workload authority and a long-term platform opportunity across connected industries.
More autonomous software.
More consequential permissions.
The opportunity is to constrain execution at the operating-system layer while making the chain of authority inspectable.
01 / Structural demand
Connected devices and autonomous tools expand the number of processes that can act on sensitive data and infrastructure. Their authority becomes a security and governance question.
02 / Technical differentiation
Rust foundations, signed capsule admission, isolated user address spaces and capability checks form a coherent security architecture. The opportunity depends on implementation quality and practical integration.
03 / Commercial discipline
A narrow, validated workflow can establish value before a broader platform rollout. Technical readiness, repeatable deployment and willingness to pay are the critical conversion points.
A large landscape.
A specific entry point.
The research catalogue covers 200 workloads across ten industries. Those opportunities are not additive: many describe alternative uses of the same device.
Start with a compatible device cohort, a buyer with a defined problem and a product that meets its operational requirements. Apply adoption and net pricing only after eligibility is established.
Explore market intelligenceDefined deployment concepts
Customer challenges, capsule designs, buyer groups, market context, global device scenarios and implementation boundaries.
TAM · Relevant category context
Broad industry spending provides scale, not automatically a NONOS revenue pool.
SAM · Qualified devices
Hardware, applications, geography, procurement and assurance narrow the eligible population.
SOM · Obtainable adoption
Sales capacity, competition, qualification time and customer evidence determine attainable share.
Turn technical control into customer value.
Platform support
Paid enterprise support, release maintenance and deployment guidance around open-source foundations.
Fleet management
A proposed recurring management service for policy distribution, device enrolment, verification and operational evidence.
OEM integration
Engineering partnerships and commercial licensing where applicable for a specific device or embedded platform.
Assurance services
Integration testing, threat modelling, deployment qualification and independent-review coordination.
Earn the right to scale.
Bounded x86_64 workflows
Select non-production privileged, signing or research tasks. Define the workflow, hardware and threat model.
Design-partner pilots
Demonstrate application fit, recovery and measurable containment. Gather evidence of customer value and buying intent.
Managed deployment
Qualify policy distribution, updates, identity integration, offline handling and support on a named hardware matrix.
OEM & sector integration
Extend hardware and application coverage. Pursue specialised sectors after meeting their procurement and assurance gates.
Make the assumptions visible.
Build your own adoption scenario.
Estimates only · USDStart with a global device population
Select a preset, then adjust the slidersCustom scenario. Select a global population above or choose your own eligible-device count below.
Sources and how these estimates work
Windows: Microsoft, June 2025. Other presets: Omdia, January 2026 (2025 shipments) multiplied by an assumed six-year active lifetime. Annual shipments are not installed devices. This simplified model assumes a stable replacement flow and omits historical shipment variation and actual retirements.
These populations overlap and must not be added together. They include hardware that may not support NONOS. Compatibility, migration and procurement must be assessed before treating a population as eligible.
1M eligible devices × 1.0% adoption × $60 / year
10K licensed devices
Before churn, discounts, channel fees, support costs, tax or implementation expense.
Device eligibility, adoption and pricing are assumptions. Population presets provide published or explicitly modelled context. These are not announced NONOS prices, signed customers, a revenue forecast, valuation or token-price model. Eligibility and willingness to pay must be demonstrated.
Readiness is earned at each gate.
| Milestone | Evidence required | Current position |
|---|---|---|
| Core security foundations | Source-pinned admission, memory separation and capability checks | Public source available; independent runtime assurance remains a qualification requirement |
| Practical OS operation | Persistence, installation, multicore, drivers, updates and recovery | Material public beta limitations |
| Enterprise control plane | Enrolment, signed policy, rollback protection, revocation and fleet receipts | Proposed architecture |
| Commercial repeatability | Successful paid deployments, unit economics, support and renewal evidence | Paid deployment and renewal evidence not publicly established |
A clear view of the work ahead.
Technology & integration
Operating-system development is complex. Hardware coverage, drivers, persistent storage, updates, power management, application availability and security assurance can constrain adoption. Source availability is not a security audit.
Commercial execution
Pilot interest may not convert to paid deployment. Procurement cycles, migration cost, incumbent platforms, support obligations and customer willingness to pay all affect attainable revenue.
Regulated & safety-critical markets
Market size does not imply eligibility. Medical, defence, industrial and transport deployments require specialised validation, independent safety controls and relevant approvals. Certification status must be confirmed for each intended deployment.
Blockchain & operational design
Signer compromise, ledger availability, finality, stale state, privacy, offline recovery and long-term governance must be engineered. A chain commitment does not prove device compliance.
Token & company economics
NOX is a separately traded cryptoasset. Token ownership is not presented as company equity, a dividend right or a claim on operating revenue. Liquidity, smart-contract risk and volatility are separate from the software business thesis.
Build a stronger
computing foundation.
Discuss technical diligence, a design-partner evaluation or strategic investment through the official NØNOS channels.
Company financials, cap-table information, funding terms, named customer evidence and commercial agreements are not published in this overview. Request those materials directly before an investment decision.
Let’s talk