Deployment Options & Fiori Cloud

Why does the cloud connector sit on the on-premise side of the landscape rather than in the cloud, and what does that placement let you avoid?

Central hub vs embedded Fiori deployment: in each, where does SAP Gateway run — and which single component's location is the whole distinction?

You want to try cloud development tools against a real on-premise system but you don't have admin rights on the host. Can you proceed, and what is the actual line between the developer and productive cloud connector?

A 2016-era design doc tells you to deliver Fiori via 'SAP Fiori, cloud edition' with zero on-premise installation. Why should you not adopt that today, and what was the original promise?

After installing the cloud connector, how do you reach its admin UI, what are the initial credentials, and what must you do at first login?

Performance-wise, what does an embedded deployment buy you over a central hub, and what is the precise mechanism behind that gain?

Beyond pure on-premise, Fiori launchpad can run cloud or hybrid. What hidden cost does the hybrid model carry that the other two don't?

In the classic Fiori cloud-edition architecture, several services (launchpad, apps, UI Theme Designer, Web IDE) ran in the cloud. How did they ever reach on-premise data — and what would break without that piece?

Trust with your cloud account is already set up. To actually expose an on-premise system through the cloud connector, which mapping do you configure and which four things must you define per system?

An architect has several back-end systems to surface through one launchpad. Why does central hub become the right call here even though it costs an extra Gateway server?

SAP Cloud Platform (later SAP BTP) — was it SaaS or PaaS, and why does mislabeling it change what you'd reach for it to do?

Classic guidance said central hub. For S/4HANA today the recommendation flipped to embedded — what changed to turn the old drawback (version coupling) into the new advantage?

Why was embedded deployment considered risky for a high-load landscape with several Business Suite systems, beyond just 'it shares the server'?