Netaphor works with manufacturers, integrators, and service providers who are accountable for print estates measured in thousands to hundreds of thousands of devices — across many sites, many manufacturers, and often many countries. SiteAudit is the layer that makes an estate that size legible enough to manage.
A few hundred devices can be managed by someone who knows them. At a few thousand, that stops being true, and at a few hundred thousand the question is no longer "what is happening on this printer" but "which of these thousands of facts should anyone act on this week." Estates at that size share a set of problems that smaller ones do not.
Large organizations do not run one vendor. Procurement cycles, acquisitions, and regional purchasing leave a genuinely mixed fleet, and each manufacturer's own tool reports on its own devices and stops. SiteAudit discovers and monitors across makes and models, which is usually the deciding capability rather than a feature-list item — it is what allows a single operating model to cover the entire estate, including the parts a competitor supplied.
A national agency or a multinational has far more locations than it has people to visit them. Discovery works from the network rather than from a site visit, so a branch office, a depot, or a regional bureau reports the same way the head office does. A Data Collection Agent covers up to 25,000 devices, and satellite agents extend the same deployment across additional sites and countries.
At this size, fleet data that lives only in a print tool has limited value. The ServiceNow Connector publishes inventory and incidents into the CMDB, so devices become managed assets alongside everything else the organization tracks, and service events land in the workflow the service desk already runs. How the ServiceNow Connector works
Utilization and volume data across the whole estate is what makes right-sizing possible: which devices are barely used, which are overloaded, where color is being paid for and not needed. On a fleet of thousands, decisions of this kind are consequential — but they are only defensible when the underlying measurement covers every device rather than a sample.
Government bodies, regulated industries, and defence-adjacent organizations frequently cannot place fleet data in a vendor's cloud, and that requirement is usually non-negotiable rather than a preference. SiteAudit runs either way. OnSite keeps the database, the mail server, and every record on the customer's own infrastructure, inside their own network boundary and under their own retention and backup policy. Hosted removes that operational burden where it is not required. The capability set is the same in both; the difference is custody.
Discovery uses SNMP, including SNMP v3 with authentication and encryption. The ports and protocols involved are documented openly rather than described in general terms — see security and ports and the network traffic guide, both of which exist so a security review can be completed without a call.
Alliance partners connect SiteAudit with broader print and service ecosystems, so identity, condition, and customer details can remain intact as they reach the systems customers already use.
If you serve large corporations, the OEM and enterprise section is the relevant one. This section is for the dealer whose book of business is hundreds or thousands of accounts averaging a few dozen devices, with plenty holding one or two. Those accounts are only profitable when finding out what is happening at them costs nothing — a site visit to read a meter can cost more than the account earns in a month.
SiteAudit is built for that shape of business. A single server routinely carries hundreds of customer environments, and has been run in production well past 4,000. SiteAudit Hosted gives a partner access to multiple customer databases, with reporting across one or more customers at a time.
On Hosted, a new customer needs one thing: a Data Collection Agent. The installer runs in one to two minutes, the service starts on its own, and discovery begins immediately — under five minutes end to end, with no database or mail server for the customer to provide.
Supply, meter, reporting, and service tasks begin from current device data rather than a phone call or a visit. Across a few thousand small accounts, that is the difference between a service model that scales and one that hires.
A single customer's failing model is an anecdote. The same model failing across dozens of accounts is a purchasing decision, a service-contract change, or a conversation with the manufacturer. Hosted reporting spans one or more customer databases at a time, so the pattern is visible without exporting anything.
Hosted. The customer needs a Data Collection Agent and an outbound HTTPS connection (port 443) to the SiteAudit Hosted server. If that connection is available, the installer takes one to two minutes, the service starts automatically, and it begins discovering and monitoring print devices straight away — caching locally and uploading to the hosted database, where the data is kept for current and historical analysis. Under five minutes, and the customer provides no database, no mail server, and no subnet documentation.
OnSite. Worth being straight about: this one varies. The customer supplies their own database and mail server, and someone has to know the IP subnets and SNMP details to enter for scanning. How long it takes depends almost entirely on how prepared the environment is. Once the application is installed, discovery and configuration still need to be entered. For a customer who wants their data on their own infrastructure this is the right path — but it is not the five-minute one, and no partner should plan as though it is.
The practical consequence for a dealer: Hosted is what makes a one-printer account economically possible, because onboarding effort stops tracking account size.
Partners use SiteAudit commercially in more than one way, and most combine several. Which of these matters most depends on whether you are growing the book or protecting the margin on the accounts you already hold.
SiteAudit licensing is sold on to the customer, earning margin on the product itself.
The fleet data is what the managed service is measured and billed against, rather than a separate line item.
Proactive supply replenishment, SLA reporting, and consolidation work are sellable once device condition and volume are already known.
Fewer visits and manual meter reads on existing accounts improves margin without adding a single new customer.
This is enterprise software, and enterprises run it at 80,000 devices and beyond. But the discovery engine, the reporting, the supply and meter data, the incident history, and the security posture reporting are the same whether the account is a global manufacturer or a dental practice with one printer. There is no reduced edition for small customers and no capability held back for a higher partner tier — what a partner can demonstrate is what a partner can deliver. Licensing determines what is deployed; it does not determine which features exist.
Discovery works from the network, not from a map. A device in Lyon, São Paulo, or Osaka becomes the same kind of record as one in the head office, and it arrives in the same central data store. That covers the customer headquartered in one country with branch offices across Europe, the Americas, or Asia — and it covers the branch office with three printers that would never justify a visit from anyone.
The same applies to a partner's own footprint. Partners running SiteAudit have offices across many states and several countries, and each of those offices is serving its own local accounts. In SiteAudit Hosted, access is granted per user across customer databases: a branch team can be given the accounts it actually services, while a national or regional team works across the whole set. Nobody has to consolidate spreadsheets from the field to answer a question about the business.
Capacity is rarely the limit. A Data Collection Agent covers up to 25,000 devices of any make and model, and two satellite agents can extend the same deployment — so a customer with forty small sites is a question of coverage, not of scale. SiteAudit Hosted normally requires no local installation or service configuration at all, which is what makes a two-person branch office practical to bring in. Installers ship in English, French, German, Japanese, Polish, and Spanish, and the application displays in the operating system's language.
SiteAudit supports organizations from local operations to distributed enterprises. Partners can apply the operating model across sectors with high concentrations of office and digital printing:
Begin with a use case, validate it with real data, and carry what works into training, a supported customer pilot, and a broader launch.
Choose the market, customer type, and first operating question worth testing.
Use real technical and operational conditions to see which connections matter.
Prepare sales and technical teams to explain, deploy, and support the approach validated in the evaluation.
Complete an initial deployment with Netaphor guidance and agreed pilot criteria.
Carry the validated use case into a wider offer with continued product and support access.
Use sales collateral, marketing resources, pricing guidance, and demo environments to explain the use case clearly.
Access product knowledge, case management, and software downloads through dedicated partner resources.
Build and refresh sales and technical capability through guided training options.
Connect SiteAudit with billing, CRM, ERP, supplies, and help-desk workflows through governed APIs.
This section is for manufacturers and product teams whose clients are large organizations — and for the partners who put SiteAudit behind their own brand. Netaphor's primary business is selling through partners of this kind, and its modular architecture supports branded experiences, governed data integration, flexible deployment, and mixed-manufacturer environments.
The mixed-manufacturer point is usually the deciding one. A large client rarely runs a single vendor's devices, so a manufacturer-native tool sees a portion of the estate and stops. SiteAudit discovers and monitors across makes and models, which means one operating model covers the whole fleet — including the parts a competitor sold. Customers run this at 80,000 devices and beyond, with a Data Collection Agent covering up to 25,000 devices and satellite agents extending the same deployment across sites and countries.
Partners arrive here from three directions: manufacturer-native tools that cannot see a mixed estate, a competing fleet platform that fell short on coverage or scale, and manual meter collection that stopped scaling as the client count grew. If you are evaluating against something specific, tell us what it is — a comparison against your actual environment is more useful than a feature grid.
Authorized partners can move from a customer deployment to the Netaphor License Application, locate the customer record, and complete SiteAudit licensing.
Bring a market, customer type, workflow, or integration idea. We can explore where SiteAudit fits and what a useful first pilot would need.