Editor: Created page with "= NP Tracker Projects = {{#seo: |title=NP Tracker Projects - Vehicle Intelligence, Security Operations and Community Safety Technology |titlemode=append |keywords=NP Tracker, vehicle intelligence South Africa, number plate lookup, suspicious vehicle lookup, ANPR South Africa, LPR, community safety technology, security intelligence, NPS-CLOUD, ANPR-Cloud, secureMIND, AdmitIT, ProveIT, PatrolIT, NPS API, vehicle hotlists, control room software, South Africa, SADC |descrip..."

2026-09-23T06:00:29Z

Created page with "= NP Tracker Projects = {{#seo: |title=NP Tracker Projects - Vehicle Intelligence, Security Operations and Community Safety Technology |titlemode=append |keywords=NP Tracker, vehicle intelligence South Africa, number plate lookup, suspicious vehicle lookup, ANPR South Africa, LPR, community safety technology, security intelligence, NPS-CLOUD, ANPR-Cloud, secureMIND, AdmitIT, ProveIT, PatrolIT, NPS API, vehicle hotlists, control room software, South Africa, SADC |descrip..."

New page

= NP Tracker Projects =

{{#seo:
|title=NP Tracker Projects - Vehicle Intelligence, Security Operations and Community Safety Technology
|titlemode=append
|keywords=NP Tracker, vehicle intelligence South Africa, number plate lookup, suspicious vehicle lookup, ANPR South Africa, LPR, community safety technology, security intelligence, NPS-CLOUD, ANPR-Cloud, secureMIND, AdmitIT, ProveIT, PatrolIT, NPS API, vehicle hotlists, control room software, South Africa, SADC
|description=Discover the NP Tracker and NPS project ecosystem: vehicle lookout intelligence, ANPR monitoring, OSINT analysis, visitor management, evidence capture, patrol operations, bots and APIs for security teams and community-safety organisations across South Africa and the SADC region.
}}

<div class="nps-hero">
<div class="nps-eyebrow">VEHICLE INTELLIGENCE • SECURITY OPERATIONS • SOUTH AFRICA & SADC</div>

== Right information. Right people. Right time. ==

'''NP Tracker turns scattered vehicle-related reports into focused, searchable intelligence.'''

When a registration number matters, authorised users can check it through supported bots, applications and integrations, review the available context and make a better-informed operational decision.

NP Tracker sits at the centre of a wider [[NPS|Number Plate Systems (NPS)]] technology ecosystem spanning vehicle intelligence, ANPR/LPR monitoring, visitor management, open-source intelligence, evidence capture, patrol operations, communications and secure API integration.

'''[https://www.nptracker.co.za/guides.html Start checking plates]'''   •   '''[https://www.nptracker.co.za/how-it-works.html See how NP Tracker works]'''   •   '''[https://www.nptracker.co.za/contact.html Discuss your requirements]'''
</div>

'''Responsible-use notice:''' Community-generated lookout reports are unverified intelligence. A result does not prove criminal conduct. Users must assess the source, date, location and context, follow applicable law and organisational procedure, and involve the appropriate security service or authorities where required.

__TOC__

== The Operational Challenge ==

Security-relevant information is often fragmented.

A vehicle may be mentioned in a public report, a participating community channel, an incident message or an operational submission. By the time that same registration is seen again, the original report may be buried in an old conversation, difficult to search or unknown to the person who needs it.

That creates three practical problems:

* '''Useful information is hard to retrieve''' when it is trapped in scattered messages and platforms.
* '''Time is lost''' while operators manually search groups, ask other teams or reconstruct old reports.
* '''Context is easily missed''' when a registration is checked without access to an earlier relevant lookout.

NP Tracker is designed to close that information gap. It processes supported vehicle-related information, identifies registration numbers, structures the relevant context and makes it retrievable through a plate-specific lookup.

== What NP Tracker Delivers ==

{| class="wikitable" style="width:100%;"
! Operational need
! NP Tracker response
! Practical value
|-
| Find earlier vehicle-related reports
| Search using a known registration number
| Retrieve relevant lookout context without manually searching multiple message histories
|-
| Support faster assessment
| Return structured information through familiar interfaces
| Help operators review what is known while an event is still developing
|-
| Connect field users and control rooms
| Provide access through supported bots, applications and integrations
| Fit vehicle intelligence into existing operational workflows
|-
| Protect against indiscriminate browsing
| Return results per plate lookup instead of publishing a browsable list of registrations
| Require the user to begin with a known registration
|-
| Extend existing security systems
| Offer API and platform-integration routes
| Add vehicle-lookout context to approved third-party and NPS workflows
|}

== How NP Tracker Works ==

The core idea is simple: collect relevant reports, recognise vehicle registrations, structure the useful context and make it retrievable when a user checks a known plate.

{{#mermaid:
flowchart LR
REPORT["Vehicle-related report"] --> DETECT["Registration identified"]
DETECT --> STRUCTURE["Context structured"]
STRUCTURE --> STORE["Secure lookup record"]
OBSERVE["Vehicle observed"] --> QUERY["Known plate submitted"]
QUERY --> STORE
STORE --> RESULT["Matching context returned"]
RESULT --> ASSESS["Human assessment"]
ASSESS --> ACTION["Appropriate action"]
}}

=== 1. Collect ===

Vehicle-related information may be received from public-domain sources, participating channels and supported submissions. The availability and scope of sources depend on the project and the authorised workflow.

=== 2. Detect ===

Supported South African and SADC registration formats are identified in relevant reports. A detected plate provides the index that allows the information to be found later.

=== 3. Structure ===

Useful report context is organised for lookup. This may include the reported registration, description, date, location, source context or a link to the underlying report where available.

=== 4. Retrieve ===

A user submits a known registration through a supported bot, application or integration. NP Tracker searches for matching lookout information and returns the available context for that plate.

=== 5. Assess ===

The user considers the age, source, location, wording and relevance of the returned information. The system supports judgement; it does not replace it.

=== 6. Respond ===

Any response remains governed by the user's authority, organisational procedures and applicable law. A lookup can inform escalation, observation, verification or reporting, but it should never be treated as an automatic instruction to confront a person.

== Built for the People Who Need Context Quickly ==

=== Security Control Rooms ===

Give operators a fast way to check a vehicle already reported by a guard, camera, resident or field team. NP Tracker can supplement live operational information with earlier lookout context.

=== Armed Response and Patrol Teams ===

Support field personnel who need to evaluate a known registration from a mobile device while following their organisation's escalation and response procedures.

=== Estates, Business Parks and Campuses ===

Add vehicle intelligence to entrance, perimeter and monitoring workflows, alongside private hotlists, visitor records or ANPR detections where those systems are configured.

=== Community Safety Organisations ===

Help neighbourhood watches, Community Policing Forums and participating safety networks retrieve earlier vehicle-related reports without maintaining isolated personal “black books”.

=== Investigators and Risk Teams ===

Use plate-linked reports as one source of contextual intelligence during a wider, properly authorised assessment or investigation.

=== Software and Integration Partners ===

Connect approved systems to documented NPS API services so vehicle lookups, report sharing or detection workflows can form part of a larger operational platform.

== One Ecosystem, Multiple Operational Problems ==

NP Tracker is part of the wider NPS portfolio. Each product solves a different operational problem, and organisations can select the components that match their needs.

{{#mermaid:
flowchart TD
NPS["Number Plate Systems (NPS)"] --> NPT["NP Tracker<br/>Vehicle lookout intelligence"]
NPS --> ANPR["ANPR-Cloud<br/>Camera detections & hotlists"]
NPS --> CLOUD["NPS-CLOUD<br/>Vehicle & operational management"]
NPS --> MIND["secureMIND<br/>OSINT & security intelligence"]
NPS --> ADMIT["AdmitIT<br/>Visitor & entrance workflows"]
NPS --> PROVE["ProveIT<br/>Verifiable image evidence"]
NPS --> PATROL["PatrolIT<br/>Patrol teams & incidents"]
}}

{| class="wikitable" style="width:100%;"
! Platform
! Primary role
! Typical operational question
! Learn more
|-
| '''NP Tracker'''
| Registration-based vehicle lookout intelligence
| “Has this known registration appeared in a relevant lookout report?”
| [https://www.nptracker.co.za/ NP Tracker]
|-
| '''ANPR-Cloud'''
| Cloud monitoring, searching and alerting for ANPR/LPR camera detections
| “Where and when was this vehicle detected, and does it match a configured hotlist?”
| [https://www.anprcloud.co.za/ ANPRCloud.co.za]
|-
| '''[[NPS-CLOUD]]'''
| Browser-based vehicle and operational management
| “How do we manage private hotlists, alerts, scanner records and reports?”
| [https://www.npscloud.co.za/ NPS-CLOUD]
|-
| '''[[TheNeedle|secureMIND]]'''
| OSINT collection, analyst investigation, intelligence correlation and KPI reporting
| “What patterns, threats or emerging risks can analysts identify across authorised sources?”
| [https://www.securemind.co.za/ secureMIND]
|-
| '''AdmitIT'''
| Visitor registration, identification, vehicle capture and entrance control
| “Who is visiting, which vehicle are they using, where are they going and what was the access decision?”
| [https://admitit.co.za/ AdmitIT]
|-
| '''ProveIT'''
| Contextual and verifiable image-evidence capture
| “What was photographed, where and when, and what supporting capture context is available?”
| [https://www.proveit.co.za/ ProveIT]
|-
| '''PatrolIT'''
| Patrol shifts, live team visibility, communications and incident reporting
| “Where are our patrol teams, what incidents were reported and what happened during the shift?”
| [https://www.patrolit.co.za/ PatrolIT]
|-
| '''freeMIRROR / SocialPrints'''
| Community communication, group automation and supported information distribution
| “How can participating groups coordinate communication and relevant alerts?”
| [https://www.freemirror.co.za/ freeMIRROR]
|}

== Vehicle Intelligence in Context ==

NP Tracker and ANPR-Cloud address different but complementary questions.

* '''ANPR-Cloud''' records an observed camera detection: the plate, time, camera, site, images and associated metadata available in that deployment.
* '''NP Tracker''' returns available lookout context associated with a registration from supported reports and submissions.
* '''Private hotlists''' represent registrations an organisation has chosen to monitor within its own authorised environment.
* '''Human assessment''' determines what the combined information means and what action is appropriate.

{{#mermaid:
flowchart TD
CAM["ANPR / LPR camera"] --> DETECTION["Vehicle detection"]
DETECTION --> ANPR["ANPR-Cloud record"]
ANPR --> HOTLIST["Private hotlist check"]
ANPR --> NPT["Supported NP Tracker lookup"]

REPORTS["Vehicle-related reports"] --> PROCESS["NP Tracker processing"]
PROCESS --> NPT

HOTLIST --> OPERATOR["Authorised operator"]
NPT --> OPERATOR
OPERATOR --> REVIEW["Review context & verify"]
REVIEW --> RESPONSE["Follow operational procedure"]
}}

An ANPR detection proves that the configured camera system recorded a detection. It does not, by itself, prove that an offence occurred. Likewise, a community lookout may provide valuable context without establishing guilt. Keeping those distinctions clear is central to responsible use.

== Access NP Tracker in the Way That Fits the Task ==

=== Telegram ===

Supported Telegram bots provide a convenient way to submit a registration and request a lookup from a mobile device or desktop client.

* [[@NPTrackerBOT]]
* [[OwnLookupBOT|Own managed lookup bots]]
* [[Third party/custom bots]]
* [https://www.nptracker.co.za/guides.html Telegram lookup guides]

=== WhatsApp ===

Supported WhatsApp services can provide a familiar interface for users who need to check a registration without opening a separate database application.

* [[NP Tracker on Whatsapp]]
* [https://www.nptracker.co.za/guides.html WhatsApp lookup guides]

=== Web and NPS Platforms ===

Authorised users may access NP Tracker functionality through supported NPS-CLOUD, ANPR-Cloud or other configured web workflows.

=== APIs and Custom Integrations ===

NPS provides documented services for approved developers and operational partners. These can support vehicle lookups, incident sharing, ANPR feed ingestion, barcode decoding and other specialised workflows.

Documented or historically listed services include:

* [[NPS-API]] — vehicle-registration lookup services
* [[NPS-SHARE]] — cross-platform incident sharing
* [[NPS-ANPR]] — ANPR/LPR feed ingestion
* [[NPS-VCR]] — vehicle-check reporting
* [[NPS-LIC]] — motor-vehicle licence-disc decoding
* [[NPS-DL]] and [[NPS-DLNAM]] — driver's-licence decoding services
* [[NPS-ID]] — supported identity-document decoding

'''[https://api.nptracker.co.za/docs/ Open the NP Tracker API documentation]'''

API availability, authentication, usage limits and commercial conditions can differ between services. Confirm current requirements in the API documentation or with NPS before designing an integration.

== Why Organisations Choose a Lookup-Based Approach ==

=== Faster Retrieval ===

A known registration becomes the starting point for a focused search. Operators do not need to remember which group, message thread or source contained the earlier report.

=== More Useful Context ===

A simple “match” is rarely enough. NP Tracker is designed to return the available report context so the user can consider what was reported, when, where and from which source.

=== Familiar User Interfaces ===

Messaging bots reduce friction for mobile users, while web platforms and APIs support control-room and system-integration requirements.

=== Controlled Discovery ===

NP Tracker is not presented as an open, browsable register of number plates. A user begins with a known registration and requests the result for that plate.

=== Scalable Integration ===

The same vehicle-intelligence capability can support an individual lookup, a managed bot, a control-room workflow or an approved API integration.

=== A Wider Operational Toolkit ===

Organisations can combine vehicle intelligence with ANPR detection, visitor management, patrol operations, evidence capture or OSINT analysis without treating every product as the same system.

== Example Operational Scenarios ==

=== Suspicious Vehicle Reported Near an Estate ===

# A resident or guard reports a registration through an approved channel.
# An authorised operator checks the known plate using NP Tracker.
# The operator reviews any matching report context, including its date and source.
# The team compares the information with current observations and private records.
# Any response follows the estate's escalation procedure and applicable law.

=== ANPR Detection Matches a Vehicle of Interest ===

# A connected camera records a vehicle detection.
# ANPR-Cloud checks the registration against configured hotlists.
# Where supported, the operator requests NP Tracker lookout context.
# The operator reviews the camera record and the separate intelligence result.
# The control room verifies the circumstances and follows its authorised response plan.

=== Patrol Team Documents an Incident ===

# A patrol member records an incident in PatrolIT.
# Photographs or supporting evidence may be captured through the appropriate workflow, including ProveIT where configured.
# A registration mentioned in the incident can be checked through an authorised NP Tracker interface.
# Supervisors review the patrol record, supporting context and required follow-up.

=== Visitor Arrives at a Controlled Entrance ===

# AdmitIT captures the authorised visitor, identity, vehicle and destination information required by the site.
# The site's configured access process determines whether any vehicle check is required.
# The access decision and entry or exit event are recorded in the relevant system.
# Staff follow the site's privacy, retention and escalation procedures.

== Responsible Intelligence, Not Automated Accusation ==

NP Tracker is designed to support human decision-making. It is not a substitute for official law-enforcement systems, an investigation, legal process or independent verification.

Every user should understand the difference between an observation, a report, a lookup match and proof.

{| class="wikitable" style="width:100%;"
! Information type
! What it can indicate
! What it does not automatically prove
|-
| Camera detection
| A configured camera recorded a plate or vehicle at a particular time and place
| That the driver or vehicle was involved in criminal conduct
|-
| Community lookout
| Someone previously reported the plate in a stated context
| That the report is complete, current or correct
|-
| Private hotlist match
| The organisation previously chose to flag that registration
| The present reason for the match or the correct response
|-
| NP Tracker result
| Matching lookout context is available for the submitted registration
| Guilt, identity of the current driver or authority to confront
|-
| Analyst correlation
| Multiple information points may share a relevant pattern
| Causation or a final investigative conclusion
|}

=== Responsible-Use Principles ===

* Check the '''date''' of the report. Old information may no longer describe current circumstances.
* Consider the '''source''' and whether it can be independently verified.
* Review the '''location''' and whether the reported context is relevant to the current observation.
* Distinguish a '''camera detection''' from a '''lookout report''' and a '''private hotlist entry'''.
* Never assume that a registration identifies the person currently driving the vehicle.
* Do not confront an individual solely because a lookup or hotlist returns a result.
* Use information only for an authorised and legitimate operational purpose.
* Restrict system access to appropriately authorised users.
* Apply applicable privacy, data-protection, information-security and retention requirements.
* Record decisions and escalations according to organisational procedure.
* Contact the appropriate security service or authorities where circumstances require it.

== Implementation Path ==

=== Step 1: Define the Operational Need ===

Identify where vehicle intelligence will be used: field lookups, a control room, entrance management, ANPR monitoring, an existing application or a multi-organisation information-sharing workflow.

=== Step 2: Select the Right Interface ===

Choose a supported bot for straightforward lookups, an NPS platform for managed operations, or an API for an approved custom integration.

=== Step 3: Establish Governance ===

Define authorised users, legitimate purposes, escalation rules, audit expectations, data handling and access-review responsibilities before operational rollout.

=== Step 4: Configure and Test ===

Test registration formats, lookup behaviour, alerts, permissions and failure handling in a controlled environment. Confirm that users understand the difference between a match and a verified incident.

=== Step 5: Train Users ===

Provide short, role-specific training for guards, operators, supervisors and administrators. Training should cover both system use and responsible interpretation.

=== Step 6: Review and Improve ===

Evaluate how the workflow performs in practice. Update hotlists, access, alerting, retention rules, response procedures and integrations as operational needs change.

== Frequently Asked Questions ==

=== Is NP Tracker a police database? ===

No. NP Tracker provides vehicle-related lookout intelligence from supported reports and participating sources. It does not replace official police databases, criminal records, legal processes or independent verification.

=== Does a lookup result prove that a vehicle is involved in crime? ===

No. A result shows that matching lookout context is available for the registration submitted. Users must examine the details and assess their relevance and reliability.

=== Can anyone browse every registration in the system? ===

NP Tracker is presented as a lookup-based service rather than an openly browsable list. A user must already know most or all of the registration being checked.

=== What information should I review in a result? ===

Review the original wording where available, the report date, source, location, circumstances and whether the information has been independently confirmed or superseded.

=== Can NP Tracker work with ANPR cameras? ===

NP Tracker lookups can form part of supported ANPR/LPR workflows. ANPR-Cloud is the dedicated NPS platform for receiving, storing, searching and monitoring supported camera detections.

=== Can my organisation maintain its own vehicle hotlist? ===

Private hotlist functionality is available within supported NPS-CLOUD and ANPR-Cloud workflows. Confirm the current product, plan and configuration requirements with NPS.

=== Is there an API? ===

Yes. NPS publishes API documentation covering vehicle and integration services. Access, authentication, limits and commercial terms depend on the specific service.

=== Can we use our own branded or managed bot? ===

Managed, third-party and custom bot options are documented within the NP Tracker project ecosystem. Contact NPS to confirm the option appropriate to your organisation.

=== Does NP Tracker cover only South Africa? ===

NP Tracker is positioned for South Africa and the wider SADC region. Registration-format support and data availability can vary by country and source.

=== What should we do when a result is returned? ===

Review the context, verify what can be verified and follow your organisation's authorised procedure. Where an immediate threat or suspected crime is involved, contact the appropriate security service or authorities.

== Get Started ==

=== I Need to Check a Registration ===

Use the current NP Tracker lookup guides to select a supported Telegram, WhatsApp or other available interface.

'''[https://www.nptracker.co.za/guides.html Open the lookup guides]'''

=== I Need Vehicle Monitoring or ANPR ===

Explore ANPR-Cloud and NPS-CLOUD for supported camera detections, searches, hotlists, alerts and vehicle-management workflows.

'''[https://www.anprcloud.co.za/ Explore ANPR-Cloud]'''   •   '''[https://www.npscloud.co.za/ Explore NPS-CLOUD]'''

=== I Need a Business or Enterprise Solution ===

Discuss the operating environment, user roles, sites, cameras, data sources, alerting, reporting, service levels and integration requirements with NPS.

'''[https://www.nptracker.co.za/contact.html Contact NP Tracker / NPS]'''

=== I Am Building an Integration ===

Review the current API documentation before relying on historical project pages or example endpoints.

'''[https://api.nptracker.co.za/docs/ View the API documentation]'''

=== I Want to Contribute a Public Vehicle Report ===

Use the current reporting route and provide a public source link where possible. Reports remain subject to review and responsible-use requirements.

'''[https://www.nptracker.co.za/report.html Report a vehicle]'''

== Product and Documentation Links ==

=== NP Tracker ===

* [https://www.nptracker.co.za/ NP Tracker Website]
* [https://www.nptracker.co.za/how-it-works.html How NP Tracker Works]
* [https://www.nptracker.co.za/guides.html Lookup Guides]
* [https://www.nptracker.co.za/faq.html Safety and Privacy FAQ]
* [https://www.nptracker.co.za/contact.html Contact]

=== Vehicle and Operational Platforms ===

* [https://www.anprcloud.co.za/ ANPR-Cloud]
* [https://wiki.anprcloud.co.za/ ANPR-Cloud Documentation]
* [https://www.npscloud.co.za/ NPS-CLOUD]
* [https://admitit.co.za/ AdmitIT]
* [https://www.proveit.co.za/ ProveIT]
* [https://www.patrolit.co.za/ PatrolIT]

=== Intelligence, Community and Developer Resources ===

* [https://www.securemind.co.za/ secureMIND]
* [[TheNeedle|secureMIND Wiki Page]]
* [[StreetTalkerWA|StreetTalker]]
* [https://www.freemirror.co.za/ freeMIRROR]
* [https://api.nptracker.co.za/docs/ NP Tracker API Documentation]
* [https://www.nptracker.co.za/solutions.html NPS Solutions Portfolio]

== See Also ==

* [[NPS|Number Plate Systems (NPS)]]
* [[@NPTrackerBOT]]
* [[NP Tracker on Whatsapp]]
* [[NPS-CLOUD]]
* [[NPS-ANPR]]
* [[NPS-API]]
* [[NPS-SHARE]]
* [[NPS-VCR]]
* [[TheNeedle|secureMIND]]
* [[StreetTalkerWA]]
* [[TOPC-MCD]]
* [[FreeMIRROR user manual]]

== Final Message ==

'''Every useful security decision starts with relevant context.'''

NP Tracker helps turn dispersed vehicle-related information into focused intelligence that can be retrieved when a known registration needs to be checked. Combined with the wider NPS ecosystem, it gives security teams, communities, estates, control rooms and technology partners a practical route from observation to context, from context to assessment and from assessment to an appropriate response.

'''[https://www.nptracker.co.za/guides.html Start with the lookup guides]'''   •   '''[https://www.nptracker.co.za/solutions.html Explore all solutions]'''   •   '''[https://www.nptracker.co.za/contact.html Contact NPS]'''

[[Category:NP Tracker]]
[[Category:NPS Projects]]
[[Category:Vehicle Intelligence]]
[[Category:ANPR]]
[[Category:Security Intelligence]]
[[Category:Community Safety]]
[[Category:Visitor Management]]
[[Category:Patrol Management]]
[[Category:OSINT]]
[[Category:Software]]
[[Category:Documentation]]

← Older revision		Revision as of 06:15, 23 September 2026
Line 516:		Line 516:

	'''[https://www.nptracker.co.za/guides.html Start with the lookup guides]'''   •   '''[https://www.nptracker.co.za/solutions.html Explore all solutions]'''   •   '''[https://www.nptracker.co.za/contact.html Contact NPS]'''		'''[https://www.nptracker.co.za/guides.html Start with the lookup guides]'''   •   '''[https://www.nptracker.co.za/solutions.html Explore all solutions]'''   •   '''[https://www.nptracker.co.za/contact.html Contact NPS]'''

	~~[[Category:NP Tracker]]~~
	~~[[Category:NPS Projects]]~~
	~~[[Category:Vehicle Intelligence]]~~
	~~[[Category:ANPR]]~~
	~~[[Category:Security Intelligence]]~~
	~~[[Category:Community Safety]]~~
	~~[[Category:Visitor Management]]~~
	~~[[Category:Patrol Management]]~~
	~~[[Category:OSINT]]~~
	~~[[Category:Software]]~~
	~~[[Category:Documentation]]~~

NP Tracker projects - Revision history

Editor: /* Final Message */

Editor: /* Intelligence, Community and Developer Resources */

Editor: /* See Also */

← Older revision		Revision as of 06:15, 23 September 2026
Line 490:		Line 490:
	* [https://www.securemind.co.za/ secureMIND]		* [https://www.securemind.co.za/ secureMIND]
	* [[TheNeedle\|secureMIND Wiki Page]]		* [[TheNeedle\|secureMIND Wiki Page]]
	* [~~[StreetTalkerWA\|~~StreetTalker]]		* [https://www.streettalker.co.za StreetTalker]
	* [https://www.freemirror.co.za/ freeMIRROR]		* [https://www.freemirror.co.za/ freeMIRROR]
	* [https://api.nptracker.co.za/docs/ NP Tracker API Documentation]		* [https://api.nptracker.co.za/docs/ NP Tracker API Documentation]

← Older revision		Revision as of 06:14, 23 September 2026
Line 506:		Line 506:
	* [[NPS-VCR]]		* [[NPS-VCR]]
	* [[TheNeedle\|secureMIND]]		* [[TheNeedle\|secureMIND]]
	* [[StreetTalkerWA]]
	* [[TOPC-MCD]]		* [[TOPC-MCD]]
	* [[FreeMIRROR user manual]]		* [[FreeMIRROR user manual]]