diff --git a/cloud/apps/web/src/app/page.tsx b/cloud/apps/web/src/app/page.tsx index 43db79a..6eadb3a 100644 --- a/cloud/apps/web/src/app/page.tsx +++ b/cloud/apps/web/src/app/page.tsx @@ -238,13 +238,25 @@ export default async function Home() {
- No. Driving a browser is the easy part — Playwright and Selenium have done it for - years, and a dozen no-code tools wrap them. The browser is simply how Ghost - reaches a system, and it is the least preferred way. Where a real API - exists that is the better path, and the same controls sit on top of it unchanged. - Ghost leads with the browser because the systems this work actually lives in — - supplier portals, ERPs, insurer sites, internal admin panels — mostly have no API, - or have one nobody has integrated. + Driving a browser is the easy part — Playwright and Selenium have done it for + years, and a dozen no-code tools wrap them. The browser is how Ghost reaches a + system, not what Ghost is. +
+
+ Being exact about it:
+ today every step runs through a browser. Calling a system’s API
+ directly is the better path where one exists, and the pieces for it are designed
+ in — an apiCall step type, the
+ connector model, and the rules that decide an API action is sensitive all exist
+ already. The executor behind them is not written yet, so Ghost does not call
+ external APIs on your behalf. The step is deliberately not offered in the editor
+ until it does, because a step that silently does nothing while the run reports
+ success is worse than no step at all.
+
+ Which matters less than it sounds, because the systems this work actually lives + in — supplier portals, ERPs, insurer sites, internal admin panels — mostly have no + API, or have one nobody has integrated. The browser is what reaches them all.
What Ghost is, is the layer between something wanting to act and the