Nothing breaks. Everything you already have keeps working — you just can’t add more until you upgrade or free up space. We show your usage clearly in settings.

You choose which ones stay active, and we ask you before the change goes through. The rest are paused three days later: a paused project keeps all of its data, it just becomes read-only and stops receiving events. You can resume any of them whenever you have a free slot — pausing a different project frees one — and upgrading again brings them all back automatically.

Anytime. Upgrades are prorated and take effect immediately. Downgrades take effect at the end of your current billing period, so you keep what you paid for. If the new plan holds fewer projects than you have active, we ask which ones you want to keep before the change goes through.

Payments are handled by Paddle, our merchant of record. They take care of invoices, receipts, and VAT/sales tax for your region.

Yes. Your plan stays active until the end of the period you already paid for, then you roll onto the free Hobby plan. Your data stays put — nothing is ever deleted. If you have more projects than the free plan holds, we ask which one you want to keep active when you cancel, and the others are paused: still there, still yours, read-only until you resume or resubscribe.

Always over HTTPS. For sensitive payloads you can also turn on encryption per project. The SDK seals each report with an X25519 public key before it leaves the client, so the body stays opaque in the browser network tab, at proxies, and in logs. Only your BugBoard server can decrypt it. Available on every plan, including Hobby.

They are two separate limits and they behave differently. The per-minute burst limit is per project. Go over it and the API answers 429 with a Retry-After header — wait the few seconds it asks for and send again. Nothing is lost. The event allowance is per account: every project you own draws on the same pool, and it resets at midnight UTC. Once it is spent, further reports are accepted and quietly discarded — the API still answers 200, because a monitoring tool should never turn a billing limit into an error inside the app it is watching. Those reports are gone rather than queued, so there is nothing to retry. One project also cannot take the whole pool. As soon as you have more than one active project, no single project may draw more than 80% of the allowance, so a misbehaving integration on one cannot silence the others.

It cannot cost you more than one day. That is what the allowance window is for: an accidental loop or a retry storm spends the day it happens on and stops there. The allowance resets at midnight UTC and you are reporting again, with no support ticket and nothing for us to reset by hand. You also hear about it while it is still happening. As your account passes 75%, 90% and 100% of its allowance, we email everyone on the project who can act on it — the owner, admins and members — and each email lists the task cards drawing the most events, so a runaway integration is usually obvious from the first line. Each of those warnings is sent at most once per day, so a loop cannot flood your inbox either.

BugBoard was built by a developer, for developers. I know what it’s like to open a billing dashboard at the end of the month and wonder where it all went. Hosting, email, storage, CI/CD, domains. It adds up fast before we've even made a dollar. That is why BugBoard is built lean on purpose. No VC funding to burn, no enterprise sales team to pay for, no unnecessary overhead. Just a focused tool that does one thing really well and charges you fairly for it. We'd rather have 1,000 happy developers who stick around forever than squeeze every dollar out of 100 who eventually churn. That's the whole philosophy.