Yes, and it does the job differently. Traditional document generation produces a snapshot: a file that was correct at the moment it was created, and starts going out of date immediately.
Nextdoc Stream renders the document as a live view of your Salesforce data. When a colleague or an AI agent changes a record, the document reflects it. You see what your customer will see before it goes out.
If you only want faster generation, that works too. Point it at your existing process and take the speed without the live window, either on demand or automatically from a Flow.
Documents typically take 2 to 3 seconds for the initial render, and around 2 seconds to reflect a change. This holds for documents up to hundreds of pages.
Speed is also affected by latency. Nextdoc rendering locations are configurable. This allows you to choose a location geographically close to your Salesforce org. This minimises network latency.
None of your data is stored in a permanent database. We follow the privacy recommendations of our partners (e.g. Salesforce) when building our integrations.
There is a caching layer which writes to temporary storage on AWS. This is cleared automatically every 24 hours.
Rendering runs in regional pods. Choosing a pod close to your Salesforce org reduces latency, and it also keeps the data within that region, which is what most data residency requirements ask for.
When creating templates, administrators can upload sample data to Nextdoc for testing. This data is stored but you control what you include in samples and it's typically test data from a sandbox or development org.
We do store Salesforce user ids for analytics and billing. To minimise PII data, we hash these values before storage so we cannot identify them.
We do store Salesforce org ids in clear text for feature access controls. They are not considered PII data and must be stored in clear text to allow customer support to activate features.
Rendering is hosted by AWS in multiple regions. In the unlikely event that your primary region (you choose in Salesforce setup) has an outage, you can switch the endpoint to another region and Stream will immediately render from there.
In other words, Stream rendering is run on a globally replicated high availability cloud service.
In 5+ years running this service, we have not had a rendering outage yet.
The template editor is run on a different system which does occasionally have interruptions for upgrades. This does not affect your end users, only your template administrators.
We passed the Salesforce security review based on following industry best practices for cloud service design.
We have automated checks for as many common vulnerabilities as possible e.g. CVEs. Any time a check fails, we fix the problem as quickly as possible.
We follow industry best practices for network communication, internal process, and authentication.
Documents are rendered using fully customizable template, typically managed by your Salesforce administrator.
These templates are created, updated and deployed from the Nextdoc cloud, also hosted on AWS. It provides a streaming template editor which provides the same UX for the administrator as the users see in Salesforce.
Data mapping is done in the editor using the samples.
Stream is installed as a managed package from the AppExchange.
It is not yet a public listing because we are still in an early access stage to maintain onboarding quality. Once we open for general access, the package will be visible on the AppExchange.
