You buy credits, and nothing else. It is a one off purchase: there is no subscription, nothing renews by itself, and we do not keep your card.

Credits do not expire. Whatever you do not spend stays on your account.

Prices are listed without VAT. The rate of your own country is added by the payment provider at checkout.

Installing pitlane costs nothing, and so does looking: scanning a resource, running the checks and booting your server all happen on your own machine and cost no credits.

Work that runs an AI model costs credits: a repair, an extension, a build, and a question you ask it. The app shows the price before it starts, and you are charged for what the call really used.

It reads the resources on your server, reports what is broken and why, and can repair, extend or write a resource when you ask it to.

A model writes that code, so a working result is what we aim at and cannot be a guarantee. You keep the last word on what goes live: a repair lands where you can read it first, and pit undo puts it back.

It does not restart your server unless you ask. It writes in your resources folder only on a deploy or a register you asked for. It records whether your server.cfg has a FiveM license key, never the key itself.

We can block a license that is used to run our model proxy for something other than this product. That is the only reason we would.

Stop whenever you like; there is nothing to cancel. Your account and any credits on it stay as they are.

Mail [email protected] and we will sort it out.

pitlane runs on your own Windows machine. Scanning, the checks, the boot simulation and the reports all happen there, and none of it sends a line of your source code anywhere.

There is one path where code does leave, and you start it yourself. When you ask for a repair, an extension or a build, the files that job touches go through our backend to Anthropic, who run the model. That transcript is kept only while the job runs: it is dropped when the job ends, and in any case within an hour.

Your email address, your password as a hash, the name you filled in, and a hash of your license key for each machine you use it on, with the last four characters and a label so you can tell them apart. The key itself is shown to you once and is never stored.

Your credit balance, your orders (how many credits, the amount, the status), and one usage row per model call: when it ran, which task, which model, how many tokens and what it cost.

Card details do not come to us. Checkout runs at Stripe, who need your email address and a billing country to work out the VAT.

Crash reports. The type of error, our own call chain, the command, the version and your OS. Paths, user names, player identifiers (steam:, license:, discord:, fivem:) and IP addresses are replaced before anything goes out. Switch it off and nothing is sent.

Bug reports you write. Your text, the version, your OS, the framework and inventory you run, what you were doing, and the last error lines from your server console, cleaned the same way. No source code and no file contents. The app prints the whole report before it sends it.

Error telemetry. Anonymised signatures of console errors, with file names, identifiers and numbers taken out. It says which class of bug is common, not who ran into it. pit telemetry off ends it.

The bridge registry. The name of a resource we do not know yet and the exports and events it publicly offers. No code, no file contents, no paths, no config values, no player data. pit telemetry show prints the lines before they go.

What happened to a fix. Which rule fired, whether you applied or dismissed it, and whether the same signature came back. No diff, no file contents, no file names, no resource names: that table has no column for them.

Anthropic, for the model work described above, and Stripe, for payments. Nobody else. Nothing is sold on, and this page carries no trackers, no analytics and nothing loaded from another site.

Zedox Development is answerable for what is written here.

Mail [email protected] and we will sort it out.

Your credits land on your balance as soon as the payment comes through, and you can spend them on the very next call. By buying you ask for that immediate delivery, and from that moment the purchase is final.

Credits do not expire, so a balance you have not spent yet is not lost.

A payment that went through while no credits arrived, and a charge that happened twice. Those are our side of it and we correct them.

Your orders are listed on your account page with their status, so a payment that stayed open is visible to you as well.

Mail [email protected] and we will sort it out.