Skip to content
RatifAIGate

Data boundary

We host the dashboard. Your agents’ data stays with you.

RatifAIGate has two halves: a hosted control plane for rules, approvals and results, and a data plane you run next to your agents. Every plan works this way.

Your environment

Data plane

  • Agents & tool execution
  • Gateway & policy checks
  • Credential vault
  • Raw prompts & context
  • Payloads & tool arguments

Raw content never leaves your environment.

RatifAIGate cloud

Control plane

  • Policies & configuration
  • Decisions & reason codes
  • Redacted traces
  • Audit summaries
  • Metrics & dashboards

Only allowlisted fields arrive; free text is dropped, not masked.

“Your environment” means wherever you run the data plane; for a single developer, a local helper on their own machine. Our own organization runs this way today. We don’t yet have external customer deployments to point to.

Built-in safeguards

Four things we never leave to the agent.

Credentials, identity, the record and what leaves your network are handled by the gateway, not by the agent and not by a prompt.

  • Agents never hold your credentials

    The gateway keeps each credential in a vault and the agent only receives the result of the call. An agent can’t leak a key it never had.

    • Credentials stay in the data-plane vault.
    • Sign-in tokens go from your browser straight to the data plane.
    • New connectors need a second owner’s approval.Preview: implemented, not yet proven in production
  • Identity is worked out by the server

    RatifAIGate resolves who is acting from the credential presented. An identity an agent claims for itself is never trusted.

    • A claim that disagrees with the credential is rejected.
    • Every action is attributed to a real principal.
    • Workspaces are isolated, and tests check nothing leaks.
  • A record that shows if it was changed

    Every governed action is written to a hash-chained ledger. Each entry carries the hash of the one before it, so an edit breaks the chain.

    • Events are never edited or deleted.
    • A correction is a new event pointing at the old one.
    • Tamper-evident, not tamper-proof: a change shows.
  • Rebuilt from an allowlist before it leaves

    Before an event leaves your data plane, its summary is rebuilt from a short allowlist: the decision, reason codes, risk tier and status.

    • Free text, prompts and tool arguments are dropped, not masked.
    • Anything not on the allowlist is removed.
    • Tests plant a fake secret and check it does not cross.

These apply to actions that go through the gateway. Anything that never passes through RatifAIGate is outside what it can see or protect.

When something breaksPreview: implemented, not yet proven in production

Reads can carry on. Anything that changes the world waits.

When a check can’t run, RatifAIGate refuses actions that write instead of waving them through.

  • The policy service is unavailableLow-risk reads continue on cached policy. Writes and high-risk actions are refused.
  • The approval service is unavailableActions that need an approval stay paused until it is back.
  • The gateway is downEvents are held on disk and replayed afterwards. In our chaos test, none were lost, even with the local sidecar killed.

The fail-closed rules are built and unit tested; a live outage demonstration is still pending. The no-loss event buffering is demonstrated.

Deployment

Where you can run it today.

Every option keeps the same boundary: the data plane runs with you, and only allowlisted summaries reach our cloud.

  • Live

    Local developer

    Install the command-line tool from public npm and run a local sidecar next to your coding agents. Windows, macOS and Linux.

  • Live

    Hybrid

    A hosted control plane plus a data plane you run. Our own organization has run on it since August 2026; no external customers yet.

  • Roadmap

    Fully private

    The control plane inside your own network, or fully air-gapped. Designed, but not built or offered today, and dates are not promised.

Compliance posture

A mapping, not an attestation.

Auditors ask for evidence. RatifAIGate produces records that map to well-known frameworks, and we are clear about what that does and doesn’t mean.

What we offer

Preview: implemented, not yet proven in production

A crosswalk from the records RatifAIGate already produces to 27 controls across these frameworks, to help you assemble audit evidence. It is a mapping; it does not by itself make an organization meet any framework.

  • EU AI Act
  • NIST AI RMF
  • ISO/IEC 42001
  • OWASP LLM Top 10
  • MITRE ATLAS

What we don’t have

We have not completed a SOC 2 audit or an ISO 27001 assessment, and we hold no third-party attestation today. We will say so on this page when that changes.

If your procurement process requires an attestation, ask us before you commit and we will tell you where we stand.

Responsible disclosure

Found a vulnerability? Tell us.

If you think you have found a security problem in this website or in RatifAIGate, email us. A person reads every report.

Report it by email

support@neurynae.com

We don’t run a bug bounty, so we can’t pay rewards. We won’t pursue researchers who act in good faith and follow these guidelines.

Please include

  • What you found and where: the page, endpoint or component.
  • The steps to reproduce it, and what you expected.
  • The impact as you see it.
  • How to reach you.

What we ask of you

  • Test only against accounts and data you own.
  • Don’t access, change or keep anyone else’s data.
  • Don’t degrade the service for other people.
  • Give us reasonable time to fix a problem before you publish it.

See what your agents are doing — before you decide what they may do.

Tell us about your setup. A person on our team reads every request, and every workspace starts in observe-only mode.

Developer plan is free · Team from $10,000 a year