Frequently asked questions

The binary. CrashCart is a catalog of prebuilt, self-contained executables — you pick a provider, model and Linux architecture, download one file, copy it to a server, and run it. The subscription is what keeps your download current as models and builds move on.

Yes. CrashCart is BYOK — bring your own key. You set CRASHCART_API_KEY in the environment at runtime and the binary uses it for that session. We never see it, it is never baked into the binary, and it never leaves the machine you run it on.

No. You pay your model provider directly for tokens, on your own account, at their rates. CrashCart charges for access to the binaries — the two bills are separate, and you keep full control of the provider relationship and spend.

The provider and model are compiled in, which is what lets the binary be a single dependency-free file with nothing to configure in a crisis. Switching models means downloading a different binary rather than editing config. That is also why plans are tiered by how many models you can download rather than by usage.

Two ways to buy. A one-time download gets you one model for one architecture, at the build available when you buy it. A subscription instead gives you ongoing access: unlimited re-downloads of the latest build while it is active, and more models as you move up the tiers. Current prices are on the pricing page in the portal.

Freshness. A one-time purchase is a snapshot: that model, that architecture, that build. It keeps working, but a newer build, the other architecture, or a different model each mean buying again. A subscription keeps you on the current build and covers both Linux architectures.

One model from a limited set, Linux x64, chat mode. It is meant for trying the thing on a real box before deciding — no session saving or prompt presets, and free builds carry a shorter freshness window.

Chat mode talks; Active Mode acts. It lets the binary use tools to run commands on the machine it is troubleshooting rather than only telling you what to type. It is compiled into higher-tier builds only, so a chat-mode binary cannot act even if asked to.

Linux x64 and ARM64 today. It is a static binary with no runtime, no installer and no dependencies — copy it over, chmod +x, run. Windows and macOS builds are planned; nothing about the model needs a native machine to build them.

The catalog rebuilds on a schedule, so new models and refreshed builds appear without you doing anything. Subscribers download the current build whenever they like. One-time buyers keep what they bought — a newer build is a new purchase.

The binary talks to your model provider with your key, and to nothing else. Prompts and output go where you would expect — to the provider you chose. The portal only records download metadata so it knows what you are entitled to.

Yes — that is what the MSP tier is for: unlimited seats, per-client prompt files, client-tagged download reporting, a white-label binary name, and a bulk download API. Use the contact form for MSP or enterprise questions.