Questions worth answering properly.

The Founding Beta is a small, selected cohort of teams who get early access to Snapn while the platform is in active development. Beta partners are not just early users: they work directly with the team building Snapn, influence the roadmap, and help shape how the product evolves.

The cohort is deliberately kept small so each partner gets real attention, not a support queue. Applications are reviewed weekly and partners are chosen based on how closely their use case aligns with what we are building.

Pricing is not published during the beta. When Snapn launches publicly, a pricing structure will be announced. Beta partners lock in their rate at whatever point they join the program, and that rate stays with them after public launch, regardless of what public pricing becomes.

This is not a temporary discount that expires. It is a permanent rate tied to your founding-partner status.

Teams where undocumented process is a real risk, not just an inconvenience. The strongest applications come from organizations in regulated industries where documentation has compliance, audit, or key-person-risk implications.

Applications are reviewed weekly. If your use case is a good fit, someone from the team will reach out directly, not via an automated sequence, to learn more about your workflows and discuss next steps. If the timing is not right we will let you know that too.

Snapn is in private beta. Pricing will be announced at public launch. Publishing a number now, before the product is fully formed and before we understand the market, would lock us and our partners into something premature.

Beta partners lock in their rate when they join. That rate persists through public launch. The tier structure (Starter, Growth, Enterprise) and what each tier includes is stable and accurately described on the pricing page.

Growth is for teams that need unlimited documentation, governance workflows, and analytics. It is hosted on Snapn’s infrastructure in a shared environment.

Enterprise unlocks three things Growth does not have: regional data residency with contractual boundary guarantees, on-premise and private cloud deployment, and Process Blueprints with automatic gap detection. If your security team needs to know where your data lives, or if you operate in a regulated environment that cannot use third-party SaaS, Enterprise is the tier you need.

Yes. During the founding beta, the Starter tier is available at no cost. It includes 25 guides per month, the Chrome and Edge extension, PDF export, link sharing, sensitive data masking, and basic analytics. No credit card is required to apply.

After public launch, Starter will retain a free tier, though the exact limits may be adjusted. Beta participants on Starter lock in their tier and rate before those decisions are finalized.

Yes. Beta partners can move up to a higher tier at any point. The founding pricing benefit extends to the tier you are on when public pricing is announced, not just the tier you joined at. Downgrading is also possible, though any data or features associated with a higher tier would become inaccessible at the lower tier.

If you cancel your Snapn account, you have a 30-day window to export your guides, blueprint data, and any associated assets before they are permanently removed from our systems. Exports are available in PDF, structured JSON, and as a full data archive. After the 30-day window closes, data is deleted in accordance with the regional deletion policies defined in your Data Processing Agreement.

For Enterprise customers with on-premise or VPC deployments, your data never leaves your environment in the first place, so there is nothing to delete on our side. Offboarding for those deployments is coordinated directly with the team.

The following are current and confirmed true:

• SOC 2 Type I achieved. Type II audit is in progress.
• ISO 27001 certified.
• HIPAA-ready architecture available on Enterprise tier.
• GDPR Data Processing Agreement available for customers requiring it, including EU and international organizations subject to GDPR.
• PIPEDA compliance for Canadian data.
• ADGM compliant for UAE and Abu Dhabi operations.

The security packet is a document bundle prepared for enterprise security teams evaluating Snapn. It includes the architecture diagram, penetration test summary, DPA, deployment options overview, and certification documentation.

You can request it by applying to the beta and checking the security packet checkbox on the form, or by contacting the team directly. It is sent to your security team’s email address, not publicly available for download.

Masking happens at the point of capture, before any data is saved or transmitted. Snapn automatically detects fields commonly associated with passwords, PII, financial data, and other sensitive information and redacts them in the captured screenshot. The redacted version is what gets saved, structured, and shared.

Masking rules are configurable for Enterprise customers, allowing your security team to define additional fields or patterns to be automatically redacted across all capture activity in your organization.

No. Your content, captured workflows, guides, and process blueprints are never used to train AI models. Enterprise customers can additionally bring their own private AI model (pluggable AI), meaning AI-assisted guide generation runs entirely on their own infrastructure with no data leaving their environment.

Three options, all available on the Enterprise tier:

• Full SaaS: hosted by Snapn on infrastructure in your chosen region. No setup on your part.
• Customer-managed VPC: deployed inside your own cloud account (AWS, Azure, or GCP). You control the infrastructure; Snapn manages the application layer.
• Fully on-premise: deployed inside your own data center. No dependency on any external service. For organizations that cannot use cloud infrastructure at all.

The application is identical across all three modes. Choosing a mode is a deployment decision, not a product decision.

Four regions are available: United States European Union Canada UAE

Regional data residency is contractually guaranteed: your data never crosses your regional boundary. This is stated in the Data Processing Agreement and enforced at the infrastructure level, not just as a policy commitment.

Yes. The security packet includes the architecture diagram, penetration test summary, and deployment options documentation. It is designed specifically for enterprise security reviews. Apply to the beta and request the security packet from the application form.

The Chrome and Edge extension can be installed by individual users without admin rights. For enterprise-wide deployment, it can be pushed via your existing MDM or browser management tool (Chrome Enterprise, Intune, Jamf, etc.) using standard extension deployment policies. No special permissions or API access to the tools being captured are required.

A guide is a step-by-step walkthrough of a single task. A Process Blueprint is a visual BPMN-style canvas that maps an entire end-to-end process, with individual guides attached to each node.

The key difference is gap detection: a Blueprint automatically flags every step in the process map that does not have a guide attached. This is the thing no other documentation tool does: it shows you not just what is documented, but what is not. That is what makes it useful for compliance and audit preparation rather than just documentation management.

Any web-based application. The browser extension works across SAP, Salesforce, Workday, ServiceNow, Oracle, Microsoft 365, Google Workspace, and any other tool that runs in a browser. No integration setup, no API access, and no admin permissions to the source application are required.

Desktop applications that are not browser-based are not currently supported.

Yes. The REST API is available on Growth and Enterprise tiers. It supports fetching guides and metadata, triggering captures programmatically, managing team members, and receiving webhook events when guides are created, updated, or approved. Token-based authentication with full documentation is provided.

Yes. Every guide can be embedded with a single line of HTML in any web page, intranet, help center, or LMS. Tested integrations include Confluence, Notion, SharePoint, Zendesk, Intercom, and any iframe-capable platform. Guides can also be shared via link (public or private) or exported as PDF for offline use.

The Snapn browser extension is available for Chrome and Microsoft Edge. Both are supported on macOS and Windows. Enterprise deployments can push the extension organization-wide via Chrome Enterprise policies, Intune, Jamf, or any standard MDM that supports browser extension management.

Firefox and Safari extensions are on the roadmap. If your organization requires a specific browser not currently supported, note this in your beta application and it will be factored into the roadmap prioritization.

Most documentation tools help you capture individual steps and share a single guide. Snapn does that too, but it adds two structural capabilities that point tools do not have.

The first is Process Blueprints with automatic gap detection: a BPMN-style canvas where you map your entire end-to-end process, attach governed SOPs to each node, and get an automatic flag on every step that has no documentation behind it. This is the capability that makes Snapn useful for compliance and audit readiness, not just documentation management.

The second is enterprise deployment flexibility: full SaaS, customer-managed VPC, or fully on-premise, with contractual regional data residency in the US, EU, Canada, and UAE. Most documentation tools are SaaS-only, which means they are not available to regulated organizations that cannot send data outside their environment or their region.

Go to the application form on the home page. The form takes about two minutes and asks six questions: the first process you would map, your team size, your industry, your primary use case, your data residency requirements, and your contact details. Applications are reviewed weekly.

For SaaS deployments, most teams are capturing their first guide within 30 minutes of the extension being installed. There is no integration setup required to start capturing. Governance workflows, team libraries, and Process Blueprints are configured progressively as the team’s needs grow.

For VPC and on-premise deployments, setup time depends on your infrastructure. Enterprise partners work directly with the team for deployment support. The security packet includes a deployment guide.

Apply to the beta and mention your question in the application. The team reads every application and will answer directly. During the founding beta there is no support queue: you communicate with the people building the product.