Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gateways.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Gateways vs Heroku

Heroku popularized git-push deploys, dynos, and add-ons on Salesforce infrastructure—great for teams that want opinionated PaaS with minimal raw cloud exposure. Gateways assumes you (or your org) operate AWS, Azure, or GCP directly and need visibility and control: environments, connections between services, and APIs—not a single shared PaaS layer.
TopicGatewaysHeroku
AbstractionReal cloud services you configureDynos, buildpacks, add-on marketplace
PortabilityNative to each cloud’s APIsHeroku platform
FitRegulated or multi-cloud shops, existing landing zonesRapid app iteration on PaaS
If Heroku’s model still fits, it remains a strong developer PaaS. If you have moved (or must use) hyperscaler accounts, Gateways helps teams see and run that estate without losing a product-grade UX. Compare hub · Cloud connections