Compare

Native vs. external Salesforce document generation

The generation architecture determines how many systems handle Salesforce data while a document is created.

The central question

Does document generation happen inside the Salesforce platform boundary, or is Salesforce data sent to another service for processing?

Why architecture matters

Document generation often handles customer, financial, healthcare, employee, or operational data. An external processing path is not inherently insecure, but it adds another service, data flow, security review, residency consideration, and failure domain to evaluate.

Native processing

Generation occurs within Salesforce and uses the platform's users, permissions, records, and storage model.

External processing

A connected service receives some combination of data, templates, or generated output and returns or stores the result.

Questions to ask

Where does data travel? Who processes it? Where are temporary files stored? Which subprocessors exist? Which controls apply?

Gutenburg architecture

Gutenburg's product architecture is fully Salesforce-native, with document processing designed to remain inside the customer's Salesforce environment.

Accessibility is a separate dimension

Native architecture and accessible PDF output answer different requirements. Evaluate both the data-processing model and whether the PDF engine creates the semantic structure required by your accessibility program.

Related Gutenburg resources

See it in Salesforce

Turn the document workflow into part of the Salesforce workflow.

Explore the interactive tour or open a conversation about the documents, automation, accessibility, and security requirements that matter to your organization.