Skip to content

Security

Built so your data stays yours

Isolation between organizations, least-privilege access, encrypted secrets and a record of what happened. Here is how each one works.

Tenant isolation

Every organization is a boundary

Every tenant table is protected by Postgres row-level security, and the application scopes each query to the organization again. Two independent layers have to agree before a row is returned.

  • Postgres row-level security on tenant tables
  • Repository-layer scoping to the organization in every query
  • The organization comes from the session or API key, never from a request body or from the AI model
  • API calls act inside exactly one organization, resolved from your membership
Read about organizations

Access control

The right people see the right things

Permissions are explicit, and sensitive actions can wait for a second person.

  • Role-based access

    Fourteen role templates cover business, vendor and 3PL staff, and you can create custom roles with exactly the permissions you want.

  • Warehouse restrictions

    Limit a member to specific warehouses so people only see the sites they work in.

  • Approval policies

    Require approval for purchase orders, adjustments and transfers, so one person cannot do everything alone.

  • Single sign-on

    SAML and OIDC single sign-on for your identity provider, available on the Enterprise plan.

  • Passwordless sign-in

    Sign in with Google, or with a one-time code sent by email or phone. There is no password to leak.

  • Scoped API keys

    Each key belongs to one organization, lists the scopes it may use and can expire. The secret is shown once, when you create it.

Data protection

Secrets sealed, traffic encrypted

Credentials you give us for sales channels and carriers are encrypted at rest, and the product is served over HTTPS.

  • Connection credentials are encrypted with AES-256-GCM, bound to the connection and organization, with versioned keys
  • TLS in transit, with HTTP redirected to HTTPS and strict transport security headers
  • Errors never include stack traces or database constraint names
  • Files are served through short-lived signed URLs from private storage
Read the security notes in the docs

Accountability

A record of what happened

So you can answer who, what and when.

  • Audit log

    Changes across the organization are recorded, and Growth and Enterprise plans can export the audit log.

  • Immutable stock ledger

    Stock movements are append-only. Corrections are new entries, so the history is intact.

  • Signed webhooks

    Outbound webhooks are signed with an HMAC and a timestamp so your endpoint can reject forged or replayed requests. Inbound webhooks are verified before they are stored.

AI guardrails

AI inside the same walls

The copilot is not a back door. It can do what the signed-in user can do, and consequential actions wait for a human.

  • Permissions are checked on every tool call
  • No tool accepts an organization id, so the model cannot choose one
  • Consequential actions need an explicit approval that is validated again when it is given
  • External text is marked as untrusted data, and the model is told not to follow instructions inside it
  • Monthly budgets, rate limits and policy limits bound cost and impact
Read how the copilot is bounded

3PL boundaries

Operators work on stock, not on your books

When a 3PL runs your warehouse, the database decides what it can read.

  • Narrow visibility

    An operator sees a client's SKU only when it is in a warehouse the operator actively runs for that client.

  • No commercial data

    Operators never see client prices, costs or valuation, and only an operational list of client settings.

  • Scoped grants

    Access is granted per warehouse with specific scopes, and can be narrowed to a zone or location.

Responsible disclosure

Found something? Tell us.

If you believe you have found a vulnerability, please email the address below with enough detail to reproduce it. Give us a reasonable chance to fix it before you share it publicly.

[email protected]

Write to [email protected]; we route security reports to the right people.

Security questions

Questions for your security team?

Talk to us and we will answer them in writing.