Names are a starting point
External and internal describe broad implementation approaches, but a storefront label does not tell you every technical detail. Avoid deciding purely on the name. Requirements, supported features, setup steps and current compatibility are more useful information for a purchase.
Two products using the same label can still have different interfaces and dependencies. Conversely, products with different labels may share familiar controls.
Do not equate architecture with a guarantee
An architecture label does not establish that a product is undetectable, harmless or allowed by a game. Account enforcement and software risks still exist. Claims about drivers, memory access or protection need evidence specific to that product; they should not be inferred from a single word in its title.
Choose using the available documentation
On United Cheats, compare the listing, menu preview and setup guide for the exact Rust product. Check the current status and ask about requirements that are not documented. If you are considering developing software yourself, remember that a commercial listing is not a technical tutorial: documentation, a test environment and permission to inspect the relevant software are separate considerations.
Your next step
Use the live product listing for current plans and requirements, then open the matching setup guide.