Plans & pricing

Your account has three things: a storage allowance, an investigation-unit budget for its period, and a set of capabilities. This page explains what each one does and how to get one changed. Your current numbers are on your billing page in the console.

Every upload is analyzed

Upload a bugreport, logcat, dmesg, pcap, trace, or bundle and analysis starts on its own. You don’t trigger it.

The one exception is the specialized log types below.

Capabilities

Most capabilities turn on a specialized log type. Two turn on features that apply to every log type. There are seven:

  • Telecom: modem and protocol analysis (Qualcomm baseband captures, and QXDM/QCAT, MediaTek and Shannon text exports). See Preparing telecom logs.
  • Automotive: CAN and VHAL analysis, including CAN traces decoded against your DBC. See Preparing automotive logs.
  • Kernel crash dump analysis: kernel crash-dump forensics, both Linux core dumps (vmcore) from x86-64 and ARM64 machines and Qualcomm device ramdumps. See Kernel dumps & References.
  • Robotics log analysis: analysis of robot recordings, in all three ROS recording formats. See Robot recordings.
  • API access: programmatic use of the public API, and connecting the Claude connector. See Getting API access.
  • Source-grounded analysis: findings cite the source line that emitted them, you can ask about that source during an investigation, and you can request a candidate fix against it. This one applies to any log type rather than turning one on, and every account has it. See Source grounding.
  • Citations from your own source: upload your organization’s own Android platform or Linux kernel source so findings cite the code your devices run. See Upload your own source.

If you upload a telecom, automotive, kernel-dump or robot-recording file and your account doesn’t have the matching capability, the file uploads but analysis stops with “This log requires <name>.” Standard logs (bugreports, logcat, dmesg, syslog, pcap, traces) are always analyzed. Source-grounded analysis behaves differently from the log-type capabilities: every account has it, and on an account where it has been turned off nothing is refused and no analysis stops. Findings simply arrive without source citations, and the fix and source-question features are not offered. See Why was I limited?.

Capabilities are provisioned for your account. If you’re on a team, your administrator can tell you which ones you have; otherwise email sales@logcat.ai.

Allowances

  • Storage: how much you can upload per period. It refills on your reset date. Deleting a file removes it from your workspace, but it does not return those bytes to your allowance for the current period. An archive counts by the data it holds, not by its upload size, since that’s what gets read and kept: a 400 MB compressed capture that expands to 4 GB draws 4 GB.
  • Investigation units: your budget for the AI work run on your files. Different operations draw down different amounts. See Investigation units & quotas for how the budget works.

Both are shown live on your billing page.

Getting a plan

Plans are provisioned by sales, not through a self-serve card checkout. Tell us what you need (capabilities, allowances, seats) and we’ll set your account up.

Once you’re on a paid plan, the billing portal on your billing page handles the rest: manage your card, download invoices, and cancel or reactivate. Cancel anytime; you keep access to the end of the current period and can reactivate before it lapses.

If you run out of storage or units mid-period, email sales@logcat.ai and we’ll raise your allowance.

Next