Questions companies ask before they trust Nura.

Nura is an AI company memory layer for teams. It connects to approved workplace sources and helps people recover decisions, context and operating knowledge with the source, reasoning, timing and decision owner attached.

Enterprise search is designed for broad information discovery across connected systems. Nura is designed around a narrower workflow: recovering a decision, preserving its provenance, surfacing conflicting records and showing whether the decision is still current.

No. Nura works alongside the tools where teams create and store information. It processes approved sources to help people understand the decision, context and current status behind that information.

Nura evaluates available signals such as recency, source type, decision owner and conflicting records. It shows the supporting sources and reasoning so the user can verify the answer. Nura can still be wrong, so materially important decisions should be checked against the original source.

Yes. Nura can return incomplete, outdated, incorrect or misattributed information. Sources and provenance are intended to make verification easier, not to remove the need for human review of materially important decisions.

Nura is built for teams whose important knowledge lives across discussions, approvals, exceptions, documents, tickets, and operational workflows.

Nura's early-access connector set includes Slack, Gmail, Google Drive, Notion and GitHub. Jira, Linear, Confluence, Zoom and HubSpot are planned.

Nura synchronizes approved source data for company-memory processing. The original content remains in its source system.

Yes. Administrators control which approved connectors and supported source scopes are connected and can revoke them later.

Nura is designed around administrator-controlled connectors, encrypted connector credentials, tenant isolation and permission-aware retrieval. Nura is currently in early access; the Security page distinguishes current controls from planned certifications and documentation.

Nura is designed to return only information the requesting user is authorized to access.

Nura does not use Customer Data to train models shared across Nura customers. Customer Data is processed to provide Nura to the relevant workspace, subject to the Privacy Policy, Terms and any applicable customer agreement.

Nura is currently free during public early access. The website shows planned post-launch tiers, which may change before paid subscriptions begin. Nura will confirm the final price and billing terms before charging any workspace.

Public early access is currently free and does not require a credit card. Nura may introduce a one-time trial when paid subscriptions launch; final eligibility and duration will be published before billing begins.

During early access, workspace limits are communicated during onboarding. When paid plans launch, Nura will show usage against the active plan and provide clear options to reduce usage or move to a plan that supports the workspace.

There is no paid public subscription to cancel during early access. Once billing launches, cancellation and access-through-period terms will be presented before purchase and reflected in the Refund Policy.

Yes. Nura can provide approved, source-backed company context to compatible AI agents through its MCP layer. Agent access is designed to follow the same workspace and permission boundaries as human access.

MCP is a protocol that allows compatible AI systems to retrieve context or invoke supported tools through a standardized interface.

No. Agent access is designed to follow the same workspace, tenant and permission boundaries as authenticated human access.

Yes. Nura answers are designed to remain traceable to approved source material, including relevant timing and ownership information. If the available evidence is incomplete or conflicting, Nura shows that uncertainty rather than presenting an unsupported conclusion as certain.

Nura is designed to isolate each organization's workspace data and company memory from other customer workspaces. Current architecture details are available from the Nura team.

Administrators can revoke a connector and request deletion of synchronized data associated with that source, subject to Nura's documented retention and deletion process.