Answers that respect who’s asking.

askneutron limits every answer to what the person asking can open, and nothing changes in your tools until a person says yes.

Talk to our teamRead the privacy policy
Access checks between people and sources A shield with a check mark covers layered document surfaces. It represents access controls for company knowledge.

Every answer follows access

Only what each person can open A shield with a check mark covers layered document surfaces. It represents access controls for company knowledge.

Only what each person can open

Before a passage is used in an answer, askneutron checks that the person asking may open its source. Anything not allowed is left out.

Access syncs from your tools A file symbol sits on a stack of document surfaces. The layers represent stored source versions.

Access syncs from your tools

Permissions come from your settings and from the tools you connect. If a connection stops syncing, its access lapses within a day, so content is hidden rather than exposed.

Every decision has a reason A message with a warning symbol sits on a raised surface. It represents questions and answers that need review.

Every decision has a reason

Each allow or deny records why, such as a group match, a restriction in the source tool, or an expired permission sync.

Changes wait for a yes

Review before anything runs An editable document, an eye, and an approval badge sit on three connected surfaces. They represent a proposed change, user review, and completion.

Review before anything runs

In chat, askneutron shows the exact change in an approval card. Nothing changes until a person confirms it.

The same rule in your AI tools The askneutron mark sits on a raised central surface. Short connections join it to app, document, API, and database symbols, showing company systems connected in one place.

The same rule in your AI tools

Through MCP, Codex and Claude can only prepare an action. The person opens askneutron to review and confirm it.

Runs with that person’s access A database symbol rises from a table of records. It represents current data read through a permitted connection.

Runs with that person’s access

A confirmed action runs as the person who confirmed it, with the access they already have in that tool.

Sign-in and identity.

Your team signs in the way your company already works.

  • Enterprise single sign-on

    Enterprise plans sign in through SAML or OpenID Connect. Your company proves it owns its email domain with a DNS record before SSO applies to it.

  • Google and Microsoft work accounts

    People can sign in with Google Workspace or a Microsoft work or school account. Personal accounts are refused.

  • Breached-password checks

    New passwords are checked against known data breaches. Only the first five characters of the password’s hash leave our service.

  • Short-lived email codes

    Email verification codes expire after five minutes, allow three attempts, and are stored hashed.

Protecting stored data.

How we encrypt, keep and isolate the data you store with us.

  • Encrypted secrets

    Connection credentials, API keys and SSO settings are encrypted at rest with AES-256-GCM. API keys can be rotated.

  • Retention you control

    Admins choose how long earlier document versions, deleted uploads and audit metadata are kept, within the options their plan includes.

  • Isolated analysis

    When Neutron runs Python to analyze data, it runs in a sandbox with no network access, separate for each organization.

  • Short-lived debugging data

    Chat debugging traces keep tool inputs and outputs encrypted for 7 days, and never record them when an answer used restricted content.

  • Allowed domains for the widget

    The embedded widget loads only on the domains you list, inside a sandboxed iframe on askneutron’s own origin.

  • Hosting

    askneutron runs on Cloudflare’s network. The database and file storage are hosted with Supabase. Our privacy policy lists every provider that processes data for us.

On the roadmap.

We hold no security certifications today. These are planned, not yet available.

  • Admin audit logPlanned

    A record of who changed SSO, API keys, allowed domains, people and roles, with export.

  • SCIM provisioningPlanned

    Add, update and remove people and groups from Okta or Microsoft Entra ID.

  • Enforced SSOPlanned

    Require single sign-on for everyone at your domain, with one break-glass owner.

  • Two-step verification for adminsPlanned

    A second factor for the people who manage your organization.

  • SOC 2Planned

    An independent audit of our security controls.

Found a security issue? Email support@workneutron.com.

Ask your company anything.

Get started free Talk to sales