No-Code SaaS Automation Platform  ·  View 06 of 21  ·  Structure

Layered Architecture

Six layers, with the providers drawn as the bottom one to keep the dependency direction honest.

Editable source SVG draw.io All views
Author surfaces Automation editor reference binding Run history Repair inbox Connector gallery Control plane Definition registry immutable versions Connector catalogue Tenancy and quotas Audit log Ingest Push endpoints Poll fleet Scheduler Trigger event log Execution Run admission fair share Step runners Step ledger Egress and trust Quota governor Connector runtime sandboxed Credential custody Providers Third-party SaaS APIs not ours publish lease attempt effect governed call Layered Architecture Application we own Security / platform Interface / broker Queue / topic Data store External / third party synchronous v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Providers are a layer, not an annotation. Drawing them inside the stack makes it visible that the bottom of this architecture is owned by other companies.
  • Egress and trust share a layer because the credential exchange and the quota decision happen at the same boundary — that co-location is deliberate and is what keeps credentials out of the runners.
  • The control plane sits above ingest and execution rather than beside them: nothing in the hot path may block on it.

Assumptions

  • The author surfaces can be unavailable (99.9%) while ingest continues at 99.99% — authors tolerate a broken editor far better than a lost trigger.

Deliberately omitted

  • Edge labels have been cut to the four that carry the flow; the layer boundaries say the rest, and the detail is in views 07 and 13.
◀  Journey — The Automation That Quietly Stopped All views Container View  ▶
Solution Architecture v1.0 · Amazon Web Services · Integration Platform Architecture · 2026-10 · 21 views06-layered-architecture