Gutenburg is designed as a Salesforce-native document-generation application. According to the product architecture, document-generation data remains inside the customer’s Salesforce environment rather than being sent to an external document-rendering service.
No external document-processing service
Gutenburg does not require a separate third-party rendering service to receive Salesforce data and produce the PDF.
The document-generation workflow occurs within the customer’s Salesforce environment.
Salesforce-native controls
Because Gutenburg operates inside Salesforce, the workflow uses familiar Salesforce components and controls, including:
- Salesforce users
- Gutenburg managed-package licensing
- Gutenburg permission sets
- Salesforce records
- Standard Salesforce Files when File creation is enabled
Data-flow implications
Keeping document-generation processing inside Salesforce reduces the need to transmit document data to a separate rendering vendor as part of the core generation process.
For organizations evaluating data residency, vendor risk, or security architecture, this can simplify the document-generation data flow that must be reviewed.
Compliance responsibility
A Salesforce-native architecture can support an organization’s security and data-residency requirements, but legal and regulatory compliance depends on the organization’s complete configuration, policies, data, and applicable obligations. Evaluate Gutenburg as part of that broader compliance program rather than treating architecture alone as a universal compliance guarantee.