Security

Security overview

How Ruligent protects your data, and honest notes on where we are as an early-stage product. Questions? Ask us directly — we answer security questionnaires.

Tenant isolation

Every database query is scoped to your organization ID, enforced in the data-access layer. API keys resolve to exactly one org; dashboard sessions resolve to exactly one user and org. Cross-tenant access is covered by automated tests.

Credential storage

API keys are stored as SHA-256 hashes and shown exactly once at creation. Passwords are hashed with scrypt and per-user salts. Webhook signing secrets are shown once and stored for signing only.

Transport & webhooks

All hosted traffic is TLS. Outbound webhooks are signed with HMAC-SHA256 and a timestamp so you can verify authenticity and reject replays; verification helpers ship in both SDKs and the core library.

Payments

Billing runs on Stripe Checkout. Card data never touches Ruligent servers. Incoming Stripe webhooks are signature-verified with a timestamp tolerance window before any plan change is applied.

Data minimization

The guard API stores a bounded summary of tool-call payloads for the audit trail — not raw payload bodies. Audit events expire per your plan's retention window and are purged automatically.

Rate limiting & abuse

Per-org guard-rate limits and per-caller API limits are enforced at the gateway. Error responses avoid leaking internals; storage failures return sanitized diagnostics.

Fail-closed design

The kill switch outranks every rule. On plans without approvals, approval-required outcomes fall back to block. The MCP gateway denies tool calls when the guard API is unreachable.

Private deployment

Private deployment options are available for organizations with data-residency or infrastructure-control requirements. Contact Ruligent to evaluate architecture, support, and operational responsibilities.

Honest maturity notes

We believe security pages should say what is true, not what sounds good:

Certifications: Ruligent does not yet hold SOC 2 or ISO 27001 certification. If your procurement requires attestations today, contact us to evaluate a private deployment and an internal security review; no certification is implied.
Disclosure: Report vulnerabilities via Security Policy. We commit to acknowledging reports promptly and fixing verified issues with priority.
Scope: Ruligent governs agent actions that pass through the gate. It cannot control actions your agents take without consulting it — instrument coverage matters, and our safety-check tool reports risky tools it has seen that have no gating policy.
Your responsibility: Ruligent provides controls, logs, and governance tooling. It does not guarantee your agents are safe, correct, or compliant with laws applicable to your use.

Have a security questionnaire?

Send it over — answering them honestly is part of the product.