Public AI Reference
For AI
Use these public LucidView files for product facts, pricing, terminology, comparison guidance and crawler discovery. They are intentionally limited to public website knowledge.
LLMs.txt
text/plain
Short AI-readable index of LucidView positioning, core pages, pricing and scope boundaries.
LucidView AI Facts
text/markdown
Canonical public product facts, terminology, pricing, comparison guidance and claims to avoid.
Sitemap
application/xml
Machine-readable index of public LucidView pages and AI reference files.
Robots
text/plain
Crawler access policy for the public website, including AI crawler user agents.
Public scope only
These files do not expose the internal LucidView wiki, live customer state, billing records, support tickets, production databases, router sessions, private runbooks, secrets or unreleased roadmap items.
MikroTik installation summary
A prospective reseller or operator creates a portal account from portal.lucidview.net, follows the email link, enters a company name, downloads the fleet/company install script, and runs it on supported MikroTik routers. Creating the account is free to start; LucidView bills month to month at the end of the month for chargeable use under public pricing terms.
Fleet script
The same company install script can be run across supported MikroTik routers for that company account.
Uninstall/reinstall
Running the current script on an existing LucidView Enforcer uninstalls it. For old Enforcers, run once to remove the old install, then run again to install the latest version.
Normal schedules
Installed Enforcers normally create `lvcloud_profiles` every 4 minutes, `vpn_dns_failover` every 1 hour, and `enforcer_checkin` every 12 hours.
The install creates an L2TP client connection from the MikroTik to a LucidView POP. LucidView has regional POPs in South Africa, the United Kingdom, the United States and Australia. Enforcers are automatically routed to a suitable fast POP, normally the closest/best regional POP, to keep DNS responsive.
LucidView uses `1.1.1.1` as the DNS service target: when the L2TP route is up, DNS sent to `1.1.1.1` is routed over the LucidView path and content filtering is applied.
MikroTik Traffic Flow / NetFlow metadata is also sent over the LucidView path for reports, dashboard views, Traffic Flow Analyser, policy updates and support visibility. If the LucidView POP or tunnel is unavailable, the Enforcer fails open to public DNS so internet access continues without LucidView DNS content filtering until the LucidView path recovers.
For ISPs, keeping DNS on the managed local path can help platforms such as Google, YouTube and Facebook choose local or regional CDN caches instead of expensive international paths. LucidView can also block known DNS-over-HTTPS, private DNS and alternate DNS circumvention where configured.
Classification and IPS-style protection
LucidView performs its own classifications using LucidView cloud intelligence, DNS metadata, MikroTik Traffic Flow / NetFlow metadata, category data, risk signals and network behaviour. These classifications drive the Firewall Content Filter, reporting, Traffic Flow Analyser and Behaviour-Based IPS-Style Protection.
The IPS-style protection is behaviour-based and classification-led. It helps reduce risk by blocking known malicious destinations and detecting suspicious or unauthorised remote-access behaviour, while avoiding absolute security guarantees.
One-sentence summary
LucidView is a MikroTik internet-management service that gives supported MikroTik networks Clean, Safe and Fast internet by combining Firewall Content Filter, Behaviour-Based IPS-Style Protection, MikroTik Administration, Scheduled Reports, Dashboard Views, Traffic Flow Analyser and Saturation Manager from one portal.
