

Protect your sensitive data from unauthorized access or disclosure with enterprise-grade security. Reprise combines multiple layers into a comprehensive information security program that is SOC 2® Type 2 certified.

With Reprise's ISO/IEC 27001:2022 certification, your product demos are protected by stringent security practices, meaning we never put your sensitive customer data at risk.

Reprise provides highly customizable Role-based Access Control (RBAC) configurations for admins, making it easy to create roles that align with your employees' positions. Manage and control the privileges of every feature in Reprise so you have the security and convenience of every employee having access to ONLY those features that they need to do their jobs.

Reprise uses a content delivery network (CDN) to distribute published content, ensuring a consistent end user experience globally. When publishing a demo, you can be confident that experience will be available for ALL your prospects and customers, at any scale!
Reprise holds SOC 2 Type II and ISO/IEC 27001:2022 certifications, and the platform is built to meet GDPR and CCPA requirements.
Your Reprise account team can share current audit reports and complete security questionnaires. The sub-processor list is public.
No. Reprise does not connect to your production databases, your internal network or your source code. A demo is built from what a builder captures in the browser.
Data Injection changes what your app shows during a demo, not the data behind it. Turn it off and the app shows its real data again.
Reprise stores what your team creates in the platform: captured screens for Product Tours, captured application content for Application Clones, datasets for Data Injection, demo configuration such as guides and notes, and usage analytics.
The strongest control is what you capture. Capture from a demo or test account, and any real data that lands in a capture can be edited out before the demo is shared.
Access is set in two layers. System roles (Admin, Builder, Viewer or a custom role) decide what a user can do in Reprise. Sharing decides who can view, edit, publish or own each demo and folder.
Groups apply either layer in bulk, and folder permissions carry to every demo inside. Demo-level access never goes beyond a user's account permissions.
Yes. Reprise supports SAML SSO through your own identity provider, including Okta, and SCIM provisioning to create, update and deactivate accounts from that provider.
When someone leaves, deactivating them in your identity provider removes their Reprise access without a manual step.
Yes. State-changing actions are recorded in a customer-visible audit log, so you can see what a user did and when.
That includes actions taken by AI assistants through the Reprise MCP, which always run as a named user with that user's permissions.
A published demo is reached through its link, so the link is the first control. For tighter access, gate the demo behind a form and track who opened it.
You also decide what is clickable and what is off limits inside a demo, and you can limit which domains a demo can be embedded on.
Yes. Published demos are served from a dedicated content delivery network, so the experience stays consistent for every viewer, whether you run five demos or five hundred.
Product Tours and Application Clones run separately from your live application, so releases and outages don't break them, and they can run offline at events with no internet.