What leaves your computer.
You can reach OpenThunder from app.openthunder.ai in a few different ways. For each one, this page says what runs where, what is sent, what is stored, and how to delete it.
Ways marked Available work today. Ways marked Coming are planned and described as plans, not as something you can use yet. For everything OpenThunder does with data, see the Trust Center and the Privacy Policy.
Use OpenThunder on this computer Available
The web page talks straight to OpenThunder on the same computer. Your code does not leave the machine.
If the OpenThunder desktop app or npx @skillstech/openthunder serve is running, the web page can show that computer’s results. Click Use OpenThunder on this computer in the banner, then Use it.
| What runs where | The page itself loads from app.openthunder.ai. The analysis runs in OpenThunder on your computer, at 127.0.0.1:7700. Your browser calls it directly; OpenThunder’s servers are not in between. |
|---|---|
| What is sent |
|
| What the page can do | View results only, and only for repositories you already added in OpenThunder on that computer. It cannot change files, run commands, run tasks or agents, open a terminal, browse your folders, or read your settings or keys. Other websites are refused. |
| What is stored | Nothing new in OpenThunder Cloud. Your browser remembers, for that tab only, that you chose this computer; it is forgotten when the tab closes. OpenThunder on your computer keeps its data on your computer, as it always does. |
| How to stop or delete |
|
| Needs | The current OpenThunder desktop app or CLI. If an older version is running, the page says so and asks you to update instead of connecting. |
Upload a folder to Cloud Available
Your source is uploaded only when you choose it, to a temporary place that is scheduled for deletion.
For people who cannot install anything. In Add repository, choose Local folder, read the notice, and pick a folder.
| What runs where | Your browser reads the folder. The analysis runs on OpenThunder Cloud’s servers. |
|---|---|
| What is sent | The text files of the folder you picked. Build output, node_modules, .git, and binary files are skipped. Limits: 4,000 files, 30 MB in total, 1 MB per file. |
| What is stored | The uploaded files, in a temporary folder on the Cloud server, scheduled for deletion about 30 minutes after upload. The results and records of the scan follow the data retention section of the Privacy Policy. |
| How to delete | Remove the repository on the Repositories page to delete the uploaded files at once, or use Delete repository data for everything derived from it, which gives you a receipt listing what was deleted and anything kept, with the reason. See the privacy FAQ. |
Try it now, no account Coming
Planned: a sample repository in a throwaway environment that deletes itself, with a receipt.
| What runs where | Planned first version: a sample repository already on OpenThunder’s servers, read-only, reset every hour. Later: a separate, short-lived environment for each visitor. |
|---|---|
| What is sent | Planned: nothing of yours. You look at a sample, not your own code. |
| What is stored | Planned: nothing tied to you. The environment shows a visible timer and deletes itself when it ends. |
| How to delete | Planned: nothing to do. When the timer ends you get a deletion receipt. |
Control your desktop from anywhere Coming
Planned: your desktop connects out to us, you approve every browser on the desktop itself, and we pass along only encrypted traffic we cannot read.
| What runs where | Planned: everything runs on your desktop. The desktop opens one outgoing, encrypted connection to OpenThunder; no ports are opened on your computer or router. |
|---|---|
| What is sent | Planned: commands and results, encrypted between your browser and your desktop with keys made when you pair them. OpenThunder relays the traffic but cannot read it. Your code is not copied to Cloud. |
| What you control | Planned: you approve each browser on the desktop (“Allow this account to control this computer?”), choose what it may do (view results, run Checks, or run agents and the terminal, which is off by default), and pick which repositories it may use. The desktop always shows “Remote session from …, Stop”, a device list with Revoke, an activity log, and a switch that cuts off every remote browser at once. |
| What is stored | Planned: Check results and their proof sync to Cloud, as they do when you publish a Check today. Your code stays on the desktop. The activity log stays on the desktop. |
| How to delete | Planned: revoke a browser or turn remote control off on the desktop. Results that synced to Cloud are deleted the same way as any repository’s data. |