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 fourteen runtimes 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:

⚛ React Native Per-screen TTFF, TTI, FID — in the app, with a built-in dashboard tab

🌐 Web (browser) Real user Web Vitals (LCP, FID, CLS, TTFB) per page — no server needed

🟢 Node.js Per-route latency on any Express server — one middleware line

🐍 Python Per-route latency on Flask or FastAPI — one decorator or middleware

☕ Java Per-route latency with JDK stdlib only — no dependencies

🐹 Go Per-route latency via standard http.Handler wrapping — pure stdlib

🐘 PHP Per-route latency — Laravel middleware or plain front-controller

🎯 C# / .NET Per-route latency via ASP.NET Core middleware — no NuGet packages

💎 Ruby Per-route latency — Rails Railtie or plain Rack middleware

🦋 Flutter Per-screen frame timings — straight from the engine, two lines in main()

🍎 Swift Per-screen timings on native Apple apps — one line at launch, plus MetricKit

🤖 Android Per-screen timings on native Android apps — one line at launch, straight from frame timing and the ART runtime

Rs Rust Per-route latency — one tower/actix layer, and a core that pulls in nothing but std

Ex Elixir Per-route latency plus scheduler and run-queue detail — one plug, OTP only

How do I install it?

Every runtime follows the same pattern:

Sign in and create a project key. Your key is issued from your dashboard after you choose a plan.
Download the kit for your runtime. The kit is a small archive you download from your key's Setup page — no public package registry.
Drop in one line per screen or route. The Setup page shows the exact command for your runtime, with your key already filled in.
Check your dashboard. Once your app is running, measurements appear in your project's performance page.

Exact install commands are on the Setup page. Each project key has its own Setup page at your dashboard → your project → Setup. The commands are specific to your runtime and have your project key already substituted, so you can copy-paste them directly.

If you use an AI assistant (Replit, Claude, Cursor, ChatGPT, Copilot, Windsurf, or others), your Setup page also provides a short prompt you can paste into your AI — it will read the install guide and do the wiring for you.

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. The kit has no access to them.

Full details are in the Privacy Policy.

Billing and cancellation

Boosthis is a paid product, priced in Saudi Riyal (SAR). You choose your plan when you create your account, before your first project key is issued. You can pay monthly or yearly — a yearly plan is charged for ten months instead of twelve. The price you see is the final amount charged — inclusive of any applicable taxes, with no hidden fees.

Free trial. If you start on the free trial, we charge SAR 1 to check the card works and refund it straight away. Nothing else is charged for the first seven days — the plan price is taken when the trial ends, unless you cancel before then.

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.

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. After that, measurements stop uploading but your data is not deleted — it is still there if you re-subscribe.

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.

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.

Need help right now?

Email us and we'll get back to you as soon as we can.

Email support