Skip to content

Support

How can we help?

Setup help, contact routes and how to report a vulnerability. LyraShield is in open beta, so response times are best-effort rather than a contractual SLA.

Email supportRequest a demo time

Include your client name and a timestamp for setup help, or your timezone and suitable times for a demo. Never include tokens or customer data.

Where to look first

Most setup questions are answered by a guide that already exists. Check these before opening a support thread:

  • Integration troubleshooting — the config-key differences that break MCP setup (VS Code uses servers, Zed uses context_servers, Gemini CLI uses httpUrl, OpenCode uses {env:VAR} interpolation).
  • REST API and API keys — creating lsk_ keys, scopes and where to store them.
  • Agent authorization — why a mutating action returns connect_required and what grants it.
  • Methodology — what an evidence state means, so a result is not read as a stronger claim than it is.

Setup help

Start with the integration guides. Marketplace clients use OAuth discovery and workspace consent; CLI and CI clients can use an API key stored in ~/.lyrashield/credentials.json.

Contact

General support: support@lyrashieldai.com. Include the client name, connection type and a timestamp—never include tokens, prompts or customer data.

Security reports

Use the security-reporting instructions to send vulnerability reports to security@lyrashieldai.com. Use encrypted attachments only when requested and do not test systems without authorization.

Start free trialIntegration guides