Grike
Grike

Secure by default, visible by design.

What Grike does to protect your organization today. Each point links to the docs that describe it in detail.

  • Four organization roles: Owner, Co-owner, Developer, and Viewer.
  • Organizations can require authenticator MFA for every member.
  • Passkeys, active-session review, and per-session revocation on every account.
  • Organization API tokens carry explicit scopes, a target, and a lifetime of 30 days by default.
  • Scopes that reveal or change secrets, or query databases, are marked sensitive.
  • CLI logins are approved in the browser and listed separately, so each can be revoked.
  • Variable values stay hidden until someone with the reveal scope asks for them.
  • The CLI asks for confirmation before revealing, and never caches revealed values.
  • Variables belong to one Environment and are never copied into another.

Isolation

Read the docs
  • Each Environment is its own boundary. Staging never shares resources with production.
  • Networks are private by default. Members reach each other and nothing else until you connect the network to the internet.
  • Agents reach the control plane over mutual TLS.
  • Organization audit logs record changes, searchable and exportable as CSV.
  • Every deploy keeps its source, build, and release, so you can roll back.
  • Access to audit logs is limited to owners and co-owners.

Report an issue

If you find a vulnerability, email the security team with steps to reproduce. We reply to every report and ask that you give us time to fix it before sharing it publicly.