←
Kongo Docs
Salesforce vs HubSpot sandbox architecture
Salesforce dev pattern vs HubSpot sandbox equivalent, with add-on sandbox scenario
Three panels. Salesforce shows multiple dev sandboxes promoting to a shared UAT and then production, with full metadata deploy including edits. HubSpot default shows one standard sandbox with only new assets auto deploying to production and manual reapply of edits, reports, dashboards, integrations, and settings. HubSpot with add-on sandboxes shows multiple sandboxes but no sandbox-to-sandbox deploy path, so every sandbox is a separate spoke into production and the manual reapply gap still applies.
Salesforce: current Esri pattern
Multiple dev sandboxes promote to a shared UAT, then to production. Full metadata deploy, edits included.
Dev 1
Dev 2
Dev 3
UAT sandbox
Merge and integration environment
Deploy including edits
Production
HubSpot: default (one sandbox)
One sandbox. Only new assets auto deploy to production. Everything else reapplied by hand.
Standard sandbox
One per Enterprise account
Auto deploy
(new assets only)
Manual reapply in prod
• Edits to existing configuration
• Reports and dashboards
• Integrations and settings
Production
HubSpot: with paid add-on sandboxes
More sandboxes can be purchased, but they cannot deploy to each other. Every sandbox is a separate spoke into prod, and the deploy limitations still apply.
Sandbox 1
Dev use
Sandbox 2
UAT use
Sandbox 3
Other use
No sandbox-to-sandbox deploy path
Auto deploy, new assets only
Production
Manual reapply of edits, reports, dashboards, integrations, and settings still applies to every sandbox