Skip to content
Fallow home

Contact

Email hello@fallow.tools with a question about Fallow or Fallow Cloud. A bug or a security problem has its own route, below.

  1. Questions, sales and billing

    Email hello@fallow.tools for a question about Fallow Cloud, your trial, an Enterprise plan or an invoice. Give the name of your organization on fallow.cloud and the repository the question is about, so I can look at the right data. The documentation answers most setup questions about the scan, the beacon, CI and the MCP server.

    You can start the 30-day trial yourself on fallow.cloud, without a credit card. If your security, legal or purchasing team needs more than a card payment, ask about Enterprise: help with your security review and its questionnaires, and payment by invoice with contract terms on request. An organization owner manages the subscription, the seats and the invoices on fallow.cloud under Settings, Billing, Manage subscription.

  2. Bugs and feature requests

    For the free, open-source scan (npx fallow, the VS Code extension and the GitHub Action), open an issue on GitHub. Give the Fallow version, the command that you ran and its output. Other users then find the issue and can add to it.

    For Fallow Cloud (the dashboard at fallow.cloud, the beacon or a coverage upload), email hello@fallow.tools. That code is not public, so a GitHub issue cannot help there. Give your organization and the repository.

  3. Security reports

    Never put a security problem in a public issue. For the free scan, use private vulnerability reporting on GitHub. For Fallow Cloud, email security@fallow.tools.

    For a security review, the network activity page lists every request that Fallow and Fallow Cloud make, and the subprocessor list names each vendor.