What's the difference between Einstein and DESelect Engage?

within journey builder in sfmc, 2 einstein components are available 1\ einstein sto einstein sto provides send time optimization, which allows sending a message to a contact when einstein thinks the contact is most likely to open a message, within a timeframe that you define it's possible to continue using einstein sto in combination with deselect engage; first, you put a deselect engage component in the journey to decide if a contact should receive a campaign send (also referred to as just "send/s"), next you have einstein sto figure out the exact timing of the send 2\ einstein frequency split einstein frequency split is a simple saturation control solution, which considers contacts over or undersaturated based on previous engagement data of a contact 90 days of history and the use of the sfmc subscription center are required for this to work black box ai is used to make the saturation control decisions, so the logic is a black box, hence no feedback is provided on why a contact is considered oversaturated engage provides a detailed prediction and history of which contacts will be excluded from which sends and why saturation control rules einstein does not allow defining your own saturation control rules in engage rules can be defined up to the level of contact categories, campaign types, and channels send prioritization einstein does not offer send prioritization; it only takes the past into account and has no capability of looking ahead at other sends that are planned in the future engage offers a campaign calendar where you can plan future sends and assign them priorities engage looks ahead in the future at planned sends to reserve timeslots for the most important sends accuracy einstein considers a contact over or undersaturated for a whole day, as data view data is processed only once per day so while a contact may be undersaturated at the start of the day, as you send messages during the day, the contact may actually become oversaturated but einstein will only detect this the next day engage does not consider over or undersaturation on a contact level, but on a send per contact level hence, a contact may be excluded from send 1 and 2 but included on send 3, even if all these 3 sends are sent out on the same day supported channels einstein supports email and mobilepush engage supports email, mobilepush, and sms as native sfmc channels, but can also process custom channels, even if those sends are happening outside of sfmc hosting einstein is hosted on aws, which may be a concern, especially for retail customers engage runs on google cloud