Small (under 200k) documents are typically rendered in less than a second.
Larger documents can take up to 2 seconds.
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. We follow the privacy recommendations of our partners (e.g. Salesforce) when building our integrations.
Data is sent from Salesforce to AWS (our cloud host) and is returned as a document. None of the data is stored on disk.
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 2+ 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.
All network communications uses TLS1.2 or higher.
We use 2FA where possible to avoid the most common attacks seen today i.e. social engineering.
We use well known encryption and authentication systems e.g. AWS Cognito.
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 from Salesforce to the template can be done in Salesforce or in the template editor.
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.