Help centre

What does Boosthis measure?

Boosthis measures how fast your own project responds for real users — timing how long each screen takes to show its first content, how quickly it becomes interactive, and how smoothly it responds to input. It also watches for known performance problems (the kind that consistently slow apps down) and surfaces the ones it finds, each with a specific fix.

All measurement runs entirely inside your running process. Nothing is sampled from source code, user input, or network traffic. Route labels and screen names are normalized before they ever leave the process, and a strict word-and-pattern guard strips anything that looks like personal data — email addresses, UUIDs, JWTs, IP addresses — before any data is sent anywhere.

Detection stays local by default. Telemetry (sending measurements to your Boosthis dashboard) is an explicit opt-in per project, not the default.

Boosthis works across twelve languages, in phone apps, browser pages, back-end servers, Bun and edge functions — sixteen separate things you can install — and rates every one of them against the same shared performance budgets, so you can compare a React Native screen and a Python API route on the same scale:

The budgets, the privacy guard and the AI tool surface are identical everywhere. How much each runtime can measure is not — a browser has no garbage collector to inspect, an edge isolate is gone between requests — so the newer kits take fewer readings than the oldest ones. The pricing page lists what each runtime gets, before you pay.

How do I install it?

The usual way: let your AI set it up. Connect your AI to Boosthis says which assistants work with it.

The first three steps happen in your browser: an AI cannot create your account or your key for you.

1. Create an account, confirm your email address with the code we send, and choose a plan or start the trial.
2. Create a project key in the dashboard. It is shown once, so copy it straight away.
3. Open that key's Setup page and pick the AI tool you use.
4. Paste the message it gives you into the AI that works on your project's code, not a separate chat that cannot see it. From there your AI follows Boosthis's private setup guide.
5. Connect your AI to Boosthis. If your tool offers to sign in to Boosthis, that is enough: choose the project and approve. Otherwise an AI that can edit your project's files usually adds the connection itself, and one that can't hands you the line to add in your tool's settings. The Setup page shows that line too. Some tools need a reload before they see a new connection.
6. Let your AI install the kits (one for each language the project runs in, all on the same key), then run the project. Once each kit checks in, readings start to appear in your dashboard as the project is used, and your AI can read them through the connection.

Two common detours:

• If you lose the key before copying it, the dashboard can issue a new one for the same project, and anything already set up keeps working.
• If your AI tool cannot add a connection at all, the kits can still be installed and the dashboard still shows the readings. Only asking your AI about them needs the connection.

Or install it yourself. Every runtime follows the same pattern:

1. Sign in and create a project key. Your key is issued from your dashboard once your free trial or a plan is running.
2. Download the kit for your runtime. The kit is a small archive — press the download button on your key's Setup page, or copy the one-line terminal command next to it. It is never on a public package registry.
3. Unpack it in your project and paste the snippet. The Setup page names the folder the archive leaves behind, how to point your project at it, and the one snippet to paste — with your key already filled in.
4. Check your dashboard. Once your app is running, measurements appear in your project's performance page.

What data leaves my app?

Nothing leaves your process by default. Local measurement and issue detection are always on; telemetry (sending data to your Boosthis dashboard) is an explicit opt-in per project.

When you do turn on telemetry for a project, the kit sends:

• Performance samples — timing numbers for each screen or route. No source code, no request bodies, no response bodies.
• Issue signals — a short label identifying a known performance pattern (e.g. "slow first render"), not the data that triggered it.
• Screen or route names — normalized and filtered. Any label that looks like an email address, UUID, JWT, IP address, or phone number is replaced with a placeholder before it ever leaves the process.

Your source code, user input, HTTP request or response bodies, cookies, and session data are never collected. Reading something inside your process and collecting it are two different things. The one exception is the AI-call meter: to tell repeated prompts apart it reads up to the first 4,096 characters of an outbound request body to an AI provider, inside your own process, and reduces it immediately to a single number — no body text is stored, uploaded or recoverable. Nine other bounded reads work the same way — the token counts a provider states in its reply, which kind of refusal a provider's error reply is, a stack trace or a secret about to reach one of your users, an error-shaped JSON answer returned with a 200, the method name in a tool-call request your app serves, the flags on the cookies your app sets, a fixed list of named headers, the query of the kit's own upload URLs and one on/off switch in the page's own address, for the dashboard bubble — each reduced on the spot to a number, a flag or a label from a fixed list, and each set out with its own limit in the Privacy Policy. One bounded read is not a reduction at all — the HTML page the dashboard bubble is written into — held only long enough for the one script tag to be written in, then handed back with nothing taken from it. One read is neither narrowed to a label from a fixed list nor limited in length — the query on requests to the kit's own read endpoints — used as the caller wrote it to pick which of the kit's own rows come back, then dropped with the reply. One bounded read does not stay inside your process — a trace id another instrumented service already put on the request — adopted only when it is exactly the shape the kits mint, then carried onward and uploaded with that request's timings so one action across your services reads as one. One read is neither bounded nor reduced to a number, and you ask for it yourself: the code you post to the kit's own rule matcher. Apart from a trace id another instrumented service already put on the request, none of what is read here is stored, uploaded or recoverable from what is uploaded, and the guard on the upload path refuses outright any payload carrying a request or response body, a header, a cookie or a query value — and that id is uploaded as a field of its own, never as the header it arrived in.

Full details are in the Privacy Policy.

Describing Boosthis in your own privacy policy. Our kit runs inside your app, so your users may reasonably expect your policy to mention it. What Boosthis collects inside your app is written for whoever reviews that policy: exactly what the kit sends, what it never sends, what changes if you switch something on, where it is processed and how long it is kept — with a short paragraph you can paste into your own policy.

Evaluating the kit before you wire it in. Before you install a Boosthis kit answers the rest of it in one page, without an account: what the kit reads inside your process, what your users see, what it puts on your own domain, which destinations a strict Content-Security-Policy has to allow, what a leaked project key can and cannot do, what checking the download against its checksum list does and does not prove, and what the first network call is and when it fires.

Billing and cancellation

Plans run from about $15 to $110 a month (SAR 56 to SAR 413 charged), or about $149 to $1101 a year (SAR 560 to SAR 4130 charged) — a yearly plan is charged for ten months instead of twelve. Charged in Saudi Riyal (SAR): the SAR figure shown is the exact amount taken from your card. The dollar figure is an approximate conversion at the fixed rate of SAR 3.75 to $1, and your own bank converts at its own rate, which may include a fee. You choose your plan when your free trial ends, or during it if you would rather subscribe straight away. You can pay monthly or yearly. The price you see is the final amount charged — inclusive of any applicable taxes, with no hidden fees.

Try Boosthis free for 7 days. It is the whole Team plan, every feature switched on: up to 6 projects, up to 10 people and 12,000 AI credits. No card and no payment details: confirm your email with the 6-digit code we send you, and the trial starts as soon as you enter it. On day 7 the trial ends and nothing is charged — subscribe whenever you like to carry on. Your projects, keys and everything already measured stay exactly as they are, whether you subscribe or not. Subscribe during the trial and you keep the free days you have left: you pay the ordinary price once, and the month you have paid for starts the day the trial would have ended. You get an email when the trial starts, one a few days in, and one when it ends. End the trial whenever you like — one click, and nothing is ever charged for it. One free trial per account and per confirmed email address.

Renewing. Plans renew automatically at the end of each period — every month on a monthly plan, every year on a yearly one. You'll receive a reminder email a few days before each renewal.

AI usage. Every plan includes a monthly allowance of AI usage for asking Boosthis questions, measured in AI credits. A short question draws a little from it; a long follow-up over a big snapshot draws more. Your billing page always shows how much is left, and roughly how many typical questions that is. You are never charged for going over — there is no automatic overage bill. If the allowance runs out, AI questions pause until the allowance resets at the start of the next month, and everything else — measuring, alerts, dashboards and rules — keeps working exactly as normal. Two things at that line work in your favour, and both are deliberate: a question that is already being answered is always finished rather than cut off part-way, so a month can end a little over the number; and if your plan included a fixed number of questions before the allowance was measured in credits, those questions still work once the credits are gone, so nobody is worse off than the plan they bought. Neither is charged for.

Your billing page. The top of the billing page says which plan you are on, what happens next and when, and what it costs — with two buttons beside it: one to change plan, one to stop. Billing is owner-only: in a shared workspace, only the workspace owner sees the plan, the card and the receipts.

Cancelling. Cancel anytime from your dashboard billing page. You keep your plan and your project keys until the end of the period you have already paid for, and until that date you can resume with one button. After that, measurements stop uploading but your data is not deleted — it is still there if you re-subscribe. Cancelling takes no payment, so it works even in the rare case where card payments are unavailable; only starting, changing or resuming a plan needs the payment provider.

Changing plan. Pick another plan from the same page — your current one is marked as current. Moving up takes effect immediately and you pay only the prorated difference for the rest of the period; moving down takes effect at your next renewal, so you keep what you paid for until then.

If a plan stops. A plan that lapses after a declined renewal can be restarted, or ended for good from the billing page — ending takes no payment and deletes nothing. Ending a plan is not the same as closing your account, which is a separate, deliberate choice.

Refunds. Fees are prepaid for the period and non-refundable except where the law requires. Full details are in the Refund & Cancellation Policy.

See the plans page for current pricing.

Getting support

There are two ways to reach the Boosthis team:

• In-dashboard support. If you're signed in, use the Support page in your dashboard. Your message is saved immediately and emailed to the team — even if email is temporarily down, the message is not lost.
• Email directly. Send a message to support@boosthis.com at any time, signed in or not. Replies go back to the address you wrote from.

What happens to your message. Once your request is closed, we keep the message for 365 days and then delete it automatically. While a request is still open we keep it until it is closed, because we cannot answer you otherwise. Support mail is never joined to telemetry. What you can ask us to do with it, including having it deleted, is in your rights over your data — and you do not need a Boosthis account to ask.

For service health — outages, degraded performance, or maintenance — the status page is linked in the footer of your dashboard once you are signed in. If you cannot sign in, email support and we will tell you what is happening.