Why is the Kitt Cache Crawler not a Plugin or Extension?
It seems to be convenient for the user to be able to administer all functions relating to the CMS within the CMS. However, the Kitt Cache Crawler neither needs the CMS nor is Kitt interested in the respective CMS. However, Kitt is not a universal crawler, but is individually adapted to the respective CMS and the plugin/extension used. Kitt communicates directly with the web server. Any contact with the respective CMS would therefore be a hindrance and would significantly affect the performance of Kitt and thus the crawling performance.
Another not unimportant reason is the issue of security. No matter how well a plugin or extension is programmed, if the CMS has vulnerabilities, then a plugin/extension is also affected. Kitt, on the other hand, is self-sufficient and cannot be connected to external access, especially since the Kitt installation directory is not tied to a specific directory. In addition, Kitt does not store any sensitive data. This protection is supplemented by a sufficiently secure login procedure, which only allows a limited and adjustable login attempt in the rare case of a brute force attack.
Ultimately, the standalone architecture ensures maximum crawl speed with low system load, which would not be possible to the same extent as a plugin or extension.