Frequently Asked Questions

A typical pilot runs two to four weeks from scoped data to a tangible output, a lifecycle report, a refresh plan, or a business-case model. Longer pilots happen when the data is fragmented across many sources, not because the platform is slow.

Most customers go from pilot to broader rollout over one to two quarters, adding integrations and feeds in priority order. There's no big-bang implementation, it's iterative, with each integration scoped on the workflow it unlocks.

Netos leads on connecting our supported feeds. Your team owns access, credentials, and approvals. Where a partner is in the conversation, they typically own the customer-facing delivery with Netos doing the platform side.

Surface it in scoping, we'd rather descope cleanly than miss a deadline. The pilot is built to expose what you don't know about your own data, so complexity is information, not failure.

Yes. Netos runs as a managed SaaS, in a dedicated tenant in your cloud (AWS, Azure, GCP), or fully on-prem. The deployment model is part of the commercial conversation and depends on data residency and security requirements.

Yes. Netos is containerized and supported on customer-managed Kubernetes or single-VM deployments for air-gapped or regulated environments. Updates ship as signed releases.

The default managed service is hosted in the UK and US. Other regions are available on request, typically driven by data residency or latency requirements.

Yes. Self-hosted and dedicated-tenant deployments keep all customer data inside the customer-controlled environment. The managed SaaS model uses tenant isolation and the controls published in the Netos Trust Center.

Yes, SOC 2 controls are verified by independent audit, with current evidence published in the Netos Trust Center at trustcenter.netos.io.

Netos processes minimal personal data, typically names and email addresses of users of the platform. Customer data (inventory, contracts, finance) is held in the chosen region, and Data Processing Agreements are part of the standard contract.

Yes. The Trust Center serves most procurement and security reviews directly. For anything not covered there, our security team responds to bespoke questionnaires as part of the procurement cycle.

Access is role-based and audited. The managed SaaS deployment grants named support engineers time-bound access for incident response only; self-hosted deployments grant zero standing Netos access.

Yes. Netos is built on NetBox and is additive to existing NetBox deployments. We ingest from your NetBox, enrich the inventory, and feed enriched data back where useful.

Start from spreadsheets. The platform is explicitly designed to ingest fragmented data, CSVs, vendor portal exports, finance system extracts, and reconcile them into a trusted source of truth.

The full catalog lives at /integrations/. Common ones include Cisco, Arista, Juniper, Aruba, NetBox, ServiceNow, SolarWinds, IP Fabric, and the major ITAMs. Custom feeds can be added in pilots when the volume justifies it.

Yes, where it makes sense, enrichment back into NetBox, ticketing into ServiceNow, exports into finance systems. The default is read-only with explicit write-back enabled on agreement.

Pricing tracks deployment model, scope, and estate size, not a published list price. We size the use case during scoping and walk through pricing once the success criteria are agreed.

Pricing is platform-based, not seat-based. Estate size matters (devices, sites, contracts under management), but adding internal viewers does not.

Most pilots are paid against a defined outcome. The pilot fee is a fraction of the first-year platform cost and converts into the rollout commercial if you continue. We do run unpaid proofs of concept in selective cases.

First-year commercials are typically annual, with multi-year discounts available. The contract is shaped to match how you'll use the platform, modules, deployment, integrations, rather than a fixed bundle.

No. The platform stands on its own, Netos works without any agents. Finance, Data, and Engineer Agents are an option you add when your team is ready, not a requirement.

Finance Agent turns BoMs, renewals, and invoices into cost models and business cases. Data Agent turns spreadsheets, APIs, and exports into a clean reconciled inventory. Engineer Agent turns inventory and lifecycle data into refresh plans and audit packs.

Yes, dashboards, report templates, terminology, and roles are configurable. Partners often white-label outputs for their customers. Custom data models and integrations are scoped case by case.

Public roadmap themes are published in the Articles section. Customer-influenced roadmap items come from named opportunities, if a workflow matters to you, surface it during scoping.

All customers get a named contact, a shared channel, and tracked tickets. SLA tiers cover incident response and time-to-fix, with enterprise tiers adding named platform engineers and quarterly business reviews.

Yes. Onboarding includes role-based training for engineers, finance, and leadership users. Self-serve docs live at docs.netos.io, and the Netos Support area covers day-to-day questions.

Once an integration is live, Netos owns the pipeline and you own the source. If a source format changes or credentials rotate, we flag it; if your team adds a new source, we scope the addition.

The platform, dashboards, and integrations don't depend on individuals. New joiners are onboarded through the same training path, and support keeps continuity across handovers.