Simple plans for every language, monthly or yearly — Boosthis

Choose monthly or yearly below, where a year costs 10 months, and the price you see is the final amount charged — inclusive of any applicable taxes, with no hidden fees. Enterprise is priced by arrangement. 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. Major cards are accepted. You choose your plan when your free trial ends, or during it if you would rather subscribe straight away.

Try Boosthis free for 3 days. It is the whole Team plan, every feature switched on: up to 6 projects, up to 7 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 3 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. If your readings do not reach us on some days of your trial or plan — unless it was something you did yourself, such as switching off a key or removing a project — we give those days back automatically, up to a limit: free days after a trial, or a later payment date on a plan. If you are still waiting on a reply from support when it ends, it carries on, within the same limit, until 3 days after we reply. 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.

Choose your plan

What each runtime actually gets

Every plan includes every kit we serve: twelve languages — JavaScript / TypeScript, Python, Java, Go, PHP, C# / .NET, Ruby, Dart (Flutter), Swift, Kotlin (Android), Rust and Elixir — in phone apps, browser pages, back-end servers, Bun and edge functions, which is sixteen things you can install. What is identical everywhere is the scoring model and its budgets, the strict PII guard, and the AI tool surface. How much a runtime can measure is not identical and cannot be: the fullest kits take 96 readings and the newest take 25, because a browser has no garbage collector to inspect, Rust has no runtime to ask, and an edge isolate is gone between requests. Find your runtime here before you choose a plan.

¹ Database work — Web (browser), React Native, Flutter, Swift (Apple) and Android (Kotlin). A kit here measures the app where it runs — on the device or in the page — and there is no server request there and no database to wait on. The database belongs to the backend the app calls, and the kit installed on that backend is what measures the work against it: the waiting, the order the queries are issued in, the rows they bring back and the pressure on the connection pool. This is a boundary, not a gap waiting to be filled.

² Whole route list — Edge functions. The platform decides which addresses reach the function, and it keeps that mapping outside the code: the kit wraps the one function the platform invokes, and there is no framework inside the isolate holding a list of routes to ask for. Every label the kit reports is therefore read from the address of a request that actually arrived. The exception is a worker that runs a router library inside the isolate: that worker does hold a list of its own, and reading it is a capability we have not built rather than one the platform prevents.

The table asks 5 questions of each of the 15 runtimes, and answers every one of them: the reading is there, it cannot exist in that runtime at all, or it is not built yet. Today: tracing on 15 of 15; full telemetry on 14 of 15; database work on 10 of 15 (it cannot exist at all on React Native, Web (browser), Flutter, Swift (Apple) and Android (Kotlin)); AI calls on 15 of 15; whole route list on 14 of 15 (it cannot exist at all on Edge functions). Tracing needs the kit to emit spans, and a waterfall needs it to link each span to the one it sits inside (15 of the 15 that emit them do); full-telemetry mode needs the kit to honour the directive. AI-call visibility is every runtime today, and the spend estimate that goes with it is Web (browser), Node.js / Express, Python and Edge functions today — a plan that includes them cannot add them to a runtime that has no way to watch. React Native, Web (browser), Node.js / Express, Python, Java, Go, PHP, C# / .NET, Ruby, Flutter, Swift (Apple), Android (Kotlin), Rust and Elixir can ask the app’s own framework for its whole route list, so the map shows routes traffic has never reached, marked as not seen. On every other runtime the map shows the pages traffic has reached, which is not the same as all the pages the app has. On Edge functions that is the only map there can be: there is no route list inside to ask for, so the cell says not applicable rather than not yet. The price is the same whichever runtime you use, so pick the plan for the readings your runtime can actually take.

Plans renew automatically — monthly plans each month, yearly plans each year — until cancelled. Cancel anytime: you keep your plan until the end of the period you have paid for, and a lapsed plan never deletes your data. Fees are prepaid for the period you chose and non-refundable except where the law requires — full details in the Refund & Cancellation Policy.