pricing.html — prepared website copy, 6 November 2026

Packages & Ongoing Support | OTCogniShield Skip to content Passive · Local processingMenuPlatformArchitectureCompliancePricingDiscuss a Factory Pilot ↗ Pause backgroundSMB APPLIANCE / CLEAR COMMERCIAL SCOPE Start with the plant. Choose the support. A local appliance for passive visibility and practical evidence, with a bounded annual Core licence and deployment priced for the work your site needs. CORE / ONE AGREED SITE Local visibility. Practical evidence. £3,500 / year Plus £1,500 one-off appliance cost. One appliance and an agreed passive monitoring scope. Core local monitoring, risk and evidence workflows. Standard report templates and controlled offline update entitlement. Up to 6 hours of remote platform support per subscription year. Customer-managed operation. Support by email during agreed UK business hours; no 24/7 monitoring or emergency response commitment. Discuss Core → SUPPORTED / PROPOSED PILOT OFFER More time with an OT practitioner. £6,995 / year Plus £1,500 one-off appliance cost. Core platform and offline update entitlement. Up to 12 hours of remote platform support per subscription year, replacing Core’s 6 hours. Four scheduled remote engineering reviews, up to 1 hour each, additional to the 12 support hours. One annual operator refresher, up to 2 hours, additional to the 12 support hours and four reviews. Reviews cover agreed findings, evidence gaps and next actions. This is scheduled assistance, not a managed SOC, certification or incident-response retainer. Discuss Supported → DEPLOYMENT / QUOTED SEPARATELY Plan it. Validate it. Hand it over. Scoped quotation Pre-installation planning and capture-point requirements. Appliance preparation and agreed passive-feed checks. Operator walkthrough, documentation and acceptance checks. Remote or on-site delivery agreed before work begins. Installation, site visits, travel, network changes, bespoke reports, integrations and custom development are outside subscription allowances unless specifically included in writing. Scope deployment →A defined service, with a clear boundary. Indicative pilot pricing for a single agreed site and appliance. Core is £5,000 in year one; Supported is £8,495 in year one, before separately quoted deployment, travel and any applicable VAT. The selected annual package (Core or Supported) is the recurring component; Supported includes Core rather than adding a second Core charge. Hardware is a one-off purchase. Core is not offered here as a perpetual licence. Monitoring capacity, collection points, retention, hardware specification, support arrangements, update delivery and renewal terms are confirmed in your written proposal. No unlimited asset count, support or engineering work is included. Support time covers diagnosis and agreed assistance; additional work requires an approved quotation. Remote support uses agreed communications and authorised evidence exports; the appliance can remain offline. Included hours are annual allowances, not guaranteed resolution times, and do not roll over. The £6,995 Supported package is a proposed offer being evaluated through paid pilots. Availability, final scope and pricing are confirmed before order. No automatic uplift from Core applies. Pricing may be revised for future offers after pilot costs are measured; accepted agreements govern existing customers. The platform remains in pre-launch validation. Evidence preparation supports review; it does not establish regulatory compliance or award certification. Incident response, 24/7 monitoring, network control and safety-system changes require separate arrangements. Need several sites or specialist help? Each site’s capacity and collection scope are reviewed separately. Multi-site coordination, consulting and additional engineering services are quoted against agreed deliverables. Discuss your requirements →PROPOSED COMMERCIAL MODEL / PENDING HCR REVIEW Annual Core. Separate module rights. These are proposed terms for new offers. Final licence rights, expiry arrangements and service commitments must be confirmed in the written agreement before order. Existing agreements retain their own terms. Licence and service boundaries for one agreed site and applianceComponent During the agreed term On non-renewal Core annual licence Entitlement to new monitoring and contracted Core workflows, within the agreed scope. Entitlement to new monitoring ends. Existing evidence remains readable and exportable under the proposed terms. Updates and support Controlled offline update entitlement and the purchased support allowance. Update entitlement and support end. No continuing security-update or response commitment is implied. Planned Manufacturing & Robotics module A separately quoted perpetual licence for the purchased module version and contracted capabilities, once validated and released. Non-renewal of optional module maintenance does not itself revoke purchased module rights. Required Core or other dependencies, and their separate terms, must be stated before order. Appliance hardware One-off hardware purchase; specification and warranty agreed separately. The hardware purchase is separate from software and service renewal. Owning the appliance does not grant a perpetual Core licence. Expiry implementation and offline operationThis page describes the proposed commercial model, not verified licence-enforcement behaviour. Evidence access and export after expiry, time handling, renewal and recovery must pass acceptance before these arrangements are supplied to a customer. No online activation or continuous licence callback is promised or introduced by this website update. Offline renewal delivery, any notice or grace period, retention and compatibility conditions must be specified and validated. No grace-period length is established here. Ending an entitlement to new monitoring does not authorise interference with machinery or deletion of retained evidence. Storage retention, backup and lawful data handling remain subject to the agreed deployment arrangements. Core and Supported pricing → · Engineering readiness → 



pilots.html — prepared website copy, 6 November 2026

Factory Design Partner Programme | OTCogniShield Skip to content Passive · Local processingMenuPlatformArchitectureCompliancePricingDiscuss a Factory Pilot ↗ FACTORY DESIGN PARTNER PROGRAMME Help shape practical OT visibility for smaller factories. Explore a controlled evaluation with agreed monitoring boundaries, engineering responsibilities and clear acceptance criteria. Start with one production area and a named plant lead. Review what the platform can observe, where the gaps are and whether the evidence helps your team make decisions. Discuss your factory ↗Download readiness checklist ↓Pre-launch programme. Participation is subject to suitability, readiness and a written scope. An enquiry grants no network access. A CONTROLLED STARTOne site.An agreed scope. Initial cohortUp to three UK manufacturing sitesStarting methodApproved recorded capture, or a SPAN/TAP feed after readiness and site approvalCommercial boundaryAgreed initial-cohort pilot deliverables at no charge. Customer-side or third-party costs identified before acceptance.After the pilotA separate decision. No automatic paid subscription.Read the programme terms and FAQs →AGREE THE MEASURES BEFORE CONNECTION Define what a useful result looks like. Targets, observation windows and exclusions are agreed for your site. These are proposed evaluation checks, not claims of completed validation. Proposed pilot acceptance checksReview area Evidence to inspect Joint review Asset visibility Observed devices compared with an agreed reference list; identity gaps and devices outside the feed recorded. Plant lead and evaluator Protocol coverage Agreed sample traffic produces expected protocol records; unsupported or encrypted fields remain explicit. Controls engineer and evaluator Traffic to workspace Trace a known capture through processing to the UI. Distinguish packet observation time from import time. Engineering reviewer Collection and recovery Check freshness, capture-loss indicators where available, restart behaviour and the agreed stop procedure. Site owner and evaluator Useful evidence Review exported records for scope, dates, owners, findings and limitations. Named assessment owner Live capture, installed isolation, detection coverage and performance require their own acceptance evidence. Monitoring supports investigation and review; it does not block attacks or certify compliance. YOUR PLANT / AGREED DATA BOUNDARIES Know what is collected.Know who can access it. Define the data handling plan before captures or site information are exchanged. Initial enquiries need only a high-level introduction. Review deployment responsibilities →Collection and access Agree the source, authorised personnel, management interface and observation window. Record what is outside scope. Storage and updates Agree local storage, retention, backup, update transfer and any separately authorised export or support access. Exit and publication Agree access closure, hardware return, evidence handover and retention or deletion. Case studies need separate written permission. ONE PAGE / NO EMAIL REQUIRED Prepare the first conversation. Use the deployment-readiness sheet with your engineering lead. Mark unknowns as questions for scoping; completing it does not authorise installation. Download the checklist ↓The practical outcomes we will evaluateWHAT WE ARE TESTING Three simple, practical outcomes. The pilot is not about proving whether industrial cyber security matters. It is about proving whether OTCogniShield makes it easier to understand and manage. 01 — IS DEPLOYMENT GENUINELY STRAIGHTFORWARD? Can a pre-configured appliance be introduced into a live industrial environment without turning installation into a major IT project? 02 — DOES IT BUILD A USEFUL PICTURE OF THE FACTORY NETWORK? Can your engineering team use observed assets, communication paths and network context to understand the agreed part of the environment more clearly? 03 — DOES IT TURN TECHNICAL EVIDENCE INTO PRACTICAL ACTION? Can observed network activity and operational context be translated into clear, prioritised decisions your team can actually use? IF IT DOESN’T MAKE THE WORK CLEARER, FASTER AND EASIER TO ACT ON, THE PILOT HAS TAUGHT US SOMETHING IMPORTANT. What your team receivesWHAT YOUR TEAM RECEIVES Real engineering value — not just a product test. The agreed OTCogniShield pilot is delivered at no charge. Scope, operational safeguards, responsibilities, hardware arrangements and success criteria are agreed in writing before anything is connected. SCOPING & SAFEGUARD AGREEMENT A clear written definition of the factory area in scope, agreed collection method, responsibilities and operational safeguards. PASSIVE PLATFORM DEPLOYMENT Installation of the local appliance against an approved SPAN/TAP feed, or analysis of agreed offline packet-capture files where appropriate. No endpoint agents. No active discovery scans across production equipment. BASELINE ASSET & RELATIONSHIP VIEW A developing inventory of the industrial devices and communication relationships visible through the agreed monitoring point. Your team helps confirm identities, functions and operational context. IEC 62443-3-2 ALIGNED RISK ASSESSMENT A structured review linking relevant threat scenarios to operational consequences, existing controls and prioritised actions. ASSURANCE READINESS SUMMARY Identification of evidence gaps relevant to customer security questionnaires, Cyber Essentials / Cyber Essentials Plus preparation, NIS2-related supply-chain requirements or other assurance discussions where applicable. This supports preparation. It is not certification, a formal Cyber Essentials Plus assessment or a legal compliance determination. FOUNDER-LED REVIEW Direct access to an OT/ICS cyber-security practitioner with more than 13 + years of specialist experience, including work with organisations such as ADNOC, Maersk and GKN. Findings are reviewed with your plant lead, engineering team or relevant management stakeholders. What we ask from your teamWHAT WE ASK FROM YOU A straightforward, practical partnership. You do not need an in-house cyber-security department. You do need people who understand how the plant operates and are willing to help us test the platform properly. NAMED PLANT CONTACT An engineering, operations or technical lead who understands the facility and can help validate asset identities and operational context. APPROVED NETWORK FEED An agreed SPAN port, network TAP, other authorised traffic source or suitable offline packet capture. OPERATIONAL CONTEXT Enough information to help distinguish expected production activity from something that genuinely deserves investigation. CANDID FEEDBACK Tell us what worked. Tell us what did not. Tell us what made the job easier — and what still felt difficult. FINAL JOINT REVIEW A structured review against the success criteria agreed at the beginning of the pilot. Your company name, logo, comments, site information or case study are never published or shared without separate written permission. Installation safeguards and stop procedureBUILT AROUND PRODUCTION Nothing connects until the safeguards are agreed. OTCogniShield is designed around passive observation rather than actively probing production equipment. But any physical installation inside an operating industrial site still has to respect the plant. Before deployment, we agree: 01 — MONITORING SCOPE Which factory area or network segment is included. 02 — COLLECTION POINT The agreed SPAN, TAP or other authorised source. 03 — AUTHORISED PERSONNEL Who can approve and support the deployment. 04 — INSTALLATION METHOD How the appliance is connected and physically accommodated. 05 — ACCEPTANCE CHECKS How we confirm the deployment is behaving as expected. 06 — STOP PROCEDURE What happens immediately if the site wants the pilot paused or disconnected. No responsible industrial security practitioner should promise zero operational risk when introducing equipment into a live factory environment. WE REDUCE AND MANAGE THAT RISK BY PLANNING THE DEPLOYMENT AROUND PRODUCTION. Visibility and coverage limitsHONEST COVERAGE BOUNDARIES Passive visibility shows what the agreed network feed presents. Passive monitoring can only analyse the traffic available through the agreed collection point. During the pilot, coverage depends on: Which network areas are presented to the appliance Which devices communicate during the observation period Which industrial protocols can be interpreted How much useful information is available from encrypted traffic Whether relevant equipment is isolated or sits outside the capture An incomplete view is not presented as complete. WHERE THE EVIDENCE STOPS, OTCogniShield SHOWS YOU. The evaluation processTHE PILOT WORKFLOW A clear process from first conversation to final review. 01 — DISCUSS Tell us about your factory, priorities and what you want to understand. 02 — SCOPE Agree the monitoring boundary, safeguards, responsibilities and success criteria. 03 — CONNECT Deploy the pre-configured appliance to the approved source or begin from agreed capture files. 04 — OBSERVE Allow normal factory traffic to build the baseline. 05 — VERIFY Review the observed assets and relationships with the people who understand the plant. 06 — ASSESS Turn relevant findings into practical risk decisions and prioritised actions. 07 — REPORT Review the findings, evidence, limitations and recommendations together. NO SURPRISES. NO OPEN-ENDED CONSULTING BILL. NO AUTOMATIC PAID SUBSCRIPTION. What happens at the endAT THE END OF THE PILOT Keep the value. Decide what happens next on your terms. At the end of the pilot, your team receives the agreed deliverables, including the asset and relationship baseline, risk-assessment outputs, assurance-readiness findings and final recommendations. Then you decide. IF YOU WANT TO CONTINUE We provide a separate commercial proposal covering the appropriate OTCogniShield licence, platform updates, support and any further consulting. IF YOU DO NOT The pilot ends. There are no automatic renewals and no obligation to buy. Hardware removal or return, access closure and agreed data retention or deletion are handled according to the pilot plan. THE PILOT SHOULD STAND ON ITS OWN AS USEFUL, COMPLETED WORK FOR YOUR FACTORY. Is your factory a good fit?IS YOUR FACTORY A GOOD FIT? We are looking for real UK manufacturing environments — not perfect labs. The initial cohort is aimed at manufacturers that: Operate active OT, IoT or IIoT equipment Can provide an authorised passive view of an agreed network area Have a plant contact who understands production operations Want a clearer view of factory-network security and risk Are willing to provide practical, honest feedback You do not need perfect documentation. You do not need a mature cyber-security programme. And you do not need to send confidential network information with your initial application. Programme costs and frequently asked questionsFREQUENTLY ASKED QUESTIONS Know what to expect. IS THE PILOT GENUINELY FREE OF CHARGE?Yes. There is no charge for the agreed OTCogniShield pilot deliverables or founder-led consulting time. Any customer-side infrastructure, access or third-party costs are identified before the pilot begins. There is no automatic conversion to a paid subscription. HOW LONG DOES A PILOT TAKE?The timetable is agreed around the factory, monitoring scope and engineering availability. A typical observation period may run for around two to four weeks, followed by review and reporting, but the agreed pilot plan determines the actual duration. DO WE NEED TO SEND SENSITIVE NETWORK INFORMATION WITH OUR APPLICATION?No. A high-level introduction is enough to start the conversation. Do not send passwords, detailed network diagrams, packet captures or other sensitive plant information with your initial enquiry. CAN YOU GUARANTEE ZERO OPERATIONAL DISRUPTION?No responsible industrial security specialist should make that promise. The platform is designed around passive observation, but physical deployment still requires careful planning and site change control. Operational safeguards and an immediate stop procedure are agreed before connection. DO WE HAVE TO BUY THE PLATFORM AFTERWARDS?No. There is no obligation to purchase a commercial licence or ongoing service. Any future engagement is a separate decision and a separate agreement. APPLY FOR THE FACTORY DESIGN PARTNER PROGRAMME Tell us about your factory. COHORT LIMITED TO UP TO THREE UK MANUFACTURING SITES. A short introduction is enough to assess suitability. Tell us: Company and site location What you manufacture The broad type of OT / industrial environment you operate What you would most like to understand or improve That might include: Factory-network visibility Customer security requirements Insurance renewal Upcoming assurance activity General OT risk understanding You do not need to provide detailed technical information at this stage. Submitting an application does not grant network access and does not commit your business to any subscription. APPLY FOR THE FACTORY DESIGN PARTNER PROGRAMMETALK TO OTCogniShieldYour nameCompanyWork emailPhone (optional)Factory town or regionApproximate OT / IoT / IIoT asset countSelect a rangeNot yet knownFewer than 5050–200201–500More than 500What would you like to achieve?This prepares an email in your email app. Nothing is submitted or stored on this website. Send the draft to complete your application; avoid confidential plant information. Prepare pilot application Your prepared applicationCopy applicationSend it to info@otcognishield.com if your email app did not open. Help us prove that serious OT security can be practical. You give OTCogniShield a real industrial environment in which to validate the proposition. We give your team useful visibility, expert interpretation and a clearer picture of the security decisions that matter to your plant. NO-COST PILOT. REAL FACTORY. USEFUL RESULTS. APPLY FOR THE FACTORY DESIGN PARTNER PROGRAMMETALK TO OTCogniShieldVALIDATION STATUS / CONTROLLED FACTORY PILOTS Evidence first. Results when they are ready. The examples on this website are synthetic. Verified factory performance results will be published only after a scoped pilot, evidence review and permission to share the findings. AVAILABLE TO INSPECTDemonstration material Supplied interface captures and a synthetic evidence pack explain the review workflow. They do not establish production performance. Inspect the examples →TO BE AGREED PER PILOTEngineering acceptance Agree the reference asset list, observation window, capture coverage, packet loss checks and operational safeguards before evaluating a site. Review deployment responsibilities →AWAITING VERIFIED RESULTSField findings Future results should identify scope, method, duration, limitations and approval to publish. Anonymous reporting still requires a verified source. Discuss a design-partner pilot →What a verified pilot case study will containScope: site or anonymised context, authorised collection points, device reference list and observation period. Method: baseline assumptions, capture coverage, comparison method and acceptance criteria agreed before testing. Findings: measured results with supporting records, unresolved identity or coverage gaps and practical review actions. Limits: traffic not observed, encrypted or silent devices, exclusions and conditions affecting interpretation. Approval: a named review owner and customer permission before any identifiable or anonymised results are published. No customer name, endorsement, success metric or production claim is implied by the current synthetic demonstrations. ENGINEERING CHECKPOINT / 4 NOVEMBER 2026 Verified maintenance. Further acceptance ahead. A targeted SASL dependency update has been deployed and checked in the current engineering environment. This is a bounded maintenance result, separate from factory-pilot acceptance. VERIFIED IN THE ENGINEERING ENVIRONMENTTargeted dependency maintenance The tested collector image and shared worker/scheduler image were deployed. All nine platform services were healthy after verification; the six other services stayed unchanged. Protected Kerberos library hashes and retained dependency checks passed. Isolated ingestion, database, job and retention checks passed before deployment. RELEASE ACCEPTANCE REMAINS OPENWhat still needs evidence Dedicated-appliance and physical SPAN/TAP capture acceptance. Supported abnormal-command paths tested from packet to alert. Remaining security findings and release decisions. Licensing review and scoped factory-pilot validation. Technical scope of this checkpointOn collector, worker and scheduler, libsasl2-2 and libsasl2-modules-db were verified at 2.1.28+dfsg-10+deb12u1. The running image identities matched the tested candidates. The collector and worker candidates were scanned before deployment, and isolated integration checks compared the running and candidate images. The deployment verification also checked retained source fingerprints, runtime configuration, mounts and network membership. Environment ordering, empty DNS-list representations and mount-list ordering were compared without discarding their values or security properties. No LDAP/SASL server-negotiation test or factory performance claim follows from this checkpoint. Remaining findings require their own evidence and decisions. Overall release status: Gate 14 HOLD. These results do not establish a completed security assessment, certification, live capture performance or factory readiness. Explore the architecture and capture paths → 



licensing.html — prepared website copy, 6 November 2026

Licence & Renewal Scope | OTCogniShieldSkip to contentPassive · Local processingMenuPlatformArchitectureCompliancePricingDiscuss a Factory Pilot ↗COMMERCIAL SCOPE Licence and renewal scope. A proposed annual Core model, with separate hardware, service and planned module terms. PROPOSED COMMERCIAL MODEL / PENDING HCR REVIEW Annual Core. Separate module rights. These are proposed terms for new offers. Final licence rights, expiry arrangements and service commitments must be confirmed in the written agreement before order. Existing agreements retain their own terms. Licence and service boundaries for one agreed site and applianceComponent During the agreed term On non-renewal Core annual licence Entitlement to new monitoring and contracted Core workflows, within the agreed scope. Entitlement to new monitoring ends. Existing evidence remains readable and exportable under the proposed terms. Updates and support Controlled offline update entitlement and the purchased support allowance. Update entitlement and support end. No continuing security-update or response commitment is implied. Planned Manufacturing & Robotics module A separately quoted perpetual licence for the purchased module version and contracted capabilities, once validated and released. Non-renewal of optional module maintenance does not itself revoke purchased module rights. Required Core or other dependencies, and their separate terms, must be stated before order. Appliance hardware One-off hardware purchase; specification and warranty agreed separately. The hardware purchase is separate from software and service renewal. Owning the appliance does not grant a perpetual Core licence. Expiry implementation and offline operationThis page describes the proposed commercial model, not verified licence-enforcement behaviour. Evidence access and export after expiry, time handling, renewal and recovery must pass acceptance before these arrangements are supplied to a customer. No online activation or continuous licence callback is promised or introduced by this website update. Offline renewal delivery, any notice or grace period, retention and compatibility conditions must be specified and validated. No grace-period length is established here. Ending an entitlement to new monitoring does not authorise interference with machinery or deletion of retained evidence. Storage retention, backup and lawful data handling remain subject to the agreed deployment arrangements. Core and Supported pricing → · Engineering readiness → OTC-DEMO-EVIDENCE-001 | v1.2Synthetic Executive Evidence Pack PreviewClose ×PDF viewerPage images · mobile friendlyPage 1 of 3 · synthetic examplePage 2 of 3 · synthetic examplePage 3 of 3 · synthetic exampleSANS ICS review themes · IEC 62443-3-2 evidence preparation. Synthetic website example; not a live export, compliance certificate or safety assessment. Download sample PDF · 3 pages ↓Open PDF separately ↗

