Everything Debugt does on your machine is in every plan. What differs is how many services run at once, how much of each request is recorded, how many overrides a library holds, and how many shared links are open at once — and, with Team, sharing a project with your team.
$0
No account, no license, no network.
$15 a month
$12 a month · $144 billed yearly
For one developer, on 3 machines.
Pro is in a closed beta.
By invitation
For a team working on the same services. Pricing is set after the beta.
Prices do not include sales tax or VAT, which is added at checkout where it applies.
| Free | Pro | Team Beta | |
|---|---|---|---|
| In every plan | |||
| Hop tracing Every call between your services, and every message on a queue. | Yes | Yes | Yes |
| Request History Every send, with its hops, payloads and recordings, kept on your machine — as many as you choose to keep. | Yes | Yes | Yes |
| Canvases, redirects, overrides, the request runner | Yes | Yes | Yes |
| Who it is for | |||
| An account | None | An email address | An email address, invited by your team |
| Machines | Any | 3 at once, for one developer | 3 at once per member |
| Limits | |||
| Services running at once | Up to 5 | No limit | No limit |
| Override libraries Named overrides kept with a project, for any service to attach. A service's own overrides have no limit on any plan. | Up to 5 per project | No limit | No limit |
| Execution recording A step is one call, line or return in a service's own code. | Up to 5,000 steps a request | Up to 200,000 steps a request | Up to 200,000 steps a request |
| Shared sends One send shared by link, encrypted on your machine. A link frees its place when it expires or you revoke it: there is no limit on how many you share over time. | 3 links open at once, each up to 3 days | 50 links open at once, each up to 7 days | 100 links open at once, each up to 14 days |
| Team | |||
| Sharing with your team Saved requests, canvases, environment profiles, overrides and redaction rules, kept in step on every member's machine — encrypted there, so Debugt's servers cannot read them. | — | — | Yes |
No. Install the extension and use it. Nothing is activated and nothing is sent anywhere.
One call, line or return in a service's own code while it handles a request, counted for each service. 5,000 is enough for an ordinary handler; a request with a real loop in it runs past that, and its recording says where it was cut short.
As many as you like over time. What is limited is how many links are open at the same moment: 3 on Free, on each machine, each lasting up to 3 days; 50 on Pro, across your machines, for up to 7 days; 100 on Team, for each member, for up to 14 days. A link frees its place when it expires, or the moment you revoke it — then share the next one. Sharing a send.
By email, a moment after paying. Paste it into Debugt under Settings → License. Keep the email: the key is stored only as a hash, so it cannot be read back — a lost key is replaced with a new one.
3 at once — a laptop, a desktop, a spare. A license is for one developer. To move it, choose “Remove from this machine” on the one you are leaving.
Nothing, for two weeks. The license is checked on your machine, and renewed once a day when there is a connection. After fourteen days without one, Debugt goes back to the Free limits until it can check again.
Pro runs to the end of what you paid for, and then Debugt goes back to the Free limits. It never stops a running service and never hides anything already on your machine.
Yes, in full, within 14 days of any payment — the first or a renewal — with no reason needed. Ask through Paddle's receipt or by email. The refund policy.
Write to us. Teams are set up by Debugt during the beta; the team's owner then invites the rest from the team page, and each member signs in to Debugt in Settings → License. Pricing for Team is set after the beta. How Teams work.
Paddle, as the reseller: the charge on your statement and the invoice are theirs, with the sales tax or VAT of where you are. Debugt never sees your card.
Debugt