Who runs Boosthis, and what its AI connection does

Open without an account, a key or a sign-in — for anyone, person or assistant, checking that Boosthis is a real service before trusting a connection to it. The same facts are published in machine-readable form, linked from this page's head.

Who operates Boosthis

Boosthis is a trade name of Veqtara Tech Company, a company registered in the Kingdom of Saudi Arabia under commercial registration number 7054832287. The same company name and number appear on the Terms of Service and on every receipt it issues.

Written questions reach a human at support@boosthis.com.

What Boosthis does

Boosthis measures how a developer's own project behaves while it runs — how long its pages and requests take, which queries are slow, what is failing — and shows those measurements back to the developer, along with the problems it finds in them.

What the AI connection is for

The AI connection lets an assistant a developer already works with read those measurements for that developer's own project, over the standard tool-connection protocol (MCP). It is one connection, offered on the same terms to every assistant that speaks the protocol; none is treated differently.

A connection carrying no project key is answered, and told it is unconfigured. That is the normal reply to a connection nobody has supplied a key for — the service is not down and nothing has been revoked. Every read simply stays shut until a developer puts their own project key on the connection.

What a connected assistant reads

Measurements a developer's own Boosthis kit has already sent from their project: timings, counts, errors, and the findings derived from them.
The files that list a project's declared packages and their versions, when a developer asks for a check on what their project depends on. Those files are read as text and nothing in them is run.
Source code is not read. Boosthis does not fetch a project's source, does not store it and cannot show it to an assistant. The one way any of it can arrive is a developer submitting their own assistant's closing lines to be checked, described below.
Personal data is filtered out before anything is stored: everything the kits send passes a privacy guard first, described in the Privacy Policy.
Only the project the presented key belongs to. One customer's key never reads another customer's measurements.

What the connection never does

It never acts on a developer's project unasked. Nothing is installed, edited, deployed or run because a connection exists; anything that touches a project is done by the developer, or by their assistant at their request.
It is read-only on the Boosthis side too. An assistant can look at a project's measurements; it cannot change an account, cancel a plan, buy anything or delete data through the connection.
It reads nothing without a project key the developer issued themselves, and that key can be revoked from the dashboard at any time.
Connecting an assistant to Boosthis does not put Boosthis inside the conversation. Nothing is taken from a session as it happens: not the prompts, not the replies, not the files being worked on, and connecting starts no such collection. What Boosthis receives is what is deliberately submitted to it, one short line at a time: a sentence to be checked against that project's own measurements, a summary of a change just made, the name of one thing about to be built, or a promise to remember. Each of those is capped at a line or a sentence and screened for personal data and credentials before it is read against anything or answered, and every one of them is the assistant choosing to send it — except where a developer has installed the hook described next, or has switched on the Boosthis editor extension's reading of their own messages, which sends work-item names the developer has seen and no assistant was involved in.
The hook is the one of those that needs no call once it is in place, and it exists only because a developer installed it. Each time their assistant finishes a turn, the hook drops fenced code blocks on the developer's own machine and sends at most 4 of the closing lines left, each no longer than 240 characters, so Boosthis can say whether that project's own measurements bear out what was just claimed. Those lines go as they were written: usually prose, but a line of code or a diff line the assistant left outside a code fence would be sent with them. Never the conversation, never the developer's prompts, never a file or a repository. Nothing is sent until a developer installs it, removing it from their settings stops it, and what arrives is screened for personal data and credentials before it is read against anything or answered. What is kept is the reading rather than the sentence, except where a sentence reads as a promise about something the project measures: that one is recorded in its own words on the project's own page, where the developer can remove it. The Privacy Policy sets out what arrives and how long it is kept.

Where to check any of this

Every page listed above answers without a key or an account, and the status page reports the service's own health at the moment it is read.