This is what it does
Try it
Six packages in this programme run inside this page. Pick one and you are using it — no install, no account, no server call.
Runs in your browser — nothing to install
- What to try: pick a tab. Each one is the product’s own client-side build; where it needs a backend, a mock runs in the page instead, so nothing you type leaves the tab.
- The rest of the programme: Frontier Terminal and Orbit — desktop edition open online elsewhere, GhostWriter is a download, and the key balance panel and PhishGuard are by invitation.
- What cannot be tried: the two invitation packages wait on a registration — a host and a carrier — and no package here charges or stores anything about you.
- Opening or using any package means you accept the beta terms, which state what each product cannot do.
Open online
Eight packages, no invitation needed
Six of them are the tabs above. The other two are a hosted service and an installable app.
RetroSkin
A light cycle racing a grid, five hand-written scene shaders and a catalogue of skins you switch between — all WebGL, no build step.
Orbit Plugin Kit
The kit’s own validator running in the page: it checks a plugin and packs a deterministic archive you can download — 32 cases checked against the Python, including every credential-filename refusal.
pst-tool
Outlook .pst extraction in the page, never uploaded — it found the same 11 folders and 71 messages as the command-line tool on the same archive.
LegacyVault
Split a secret three ways with Shamir, print a shard, name a beneficiary and run the inactivity ladder — the product’s own cryptography and recovery engine.
PreLawyer
Anonymous intake, a deterministic strength estimate, the limitation window, the lawyer feed and the identity reveal — the whole data layer running inside the page.
The Anti-App
Quest list, capture step and the one-day grace streak, in three static files. The verification verdict is simulated and labelled DEMO, in the data and on the screen.
Frontier Terminal
A hosted service, not a mock: SEC filings, insider Form 4 transactions, sentiment scored over filing text and daily market bars on a 30-minute schedule, every signal shown with the run that produced it.
Orbit — desktop edition
The studio’s own application, running on its host, with an install route from the marketplace landing. It is the largest surface here and the one with the longest way to go.
Download
One package runs on your machine
GhostWriter
The packaged browser extension for Chromium and Firefox, with the SHA-256 of each file. Not in a store yet, so the install is a load-unpacked and the notes walk it through.
By invitation
Two packages whose missing piece is a registration, not code
Both are built and tested, and neither can be handed to a stranger today. The reasons are external to the code, so they are listed rather than dressed up as open betas.
Key balance panel
A plugin that reads your own key file and usage ledger and shows the balance, the spend split and whether you are inside a cheap or an expensive window. It installs into the studio’s own console host, so a tester needs that host first — ask and we will walk it through.
PhishGuard
Single-use, short-lived verification links that replace texted one-time codes. The service and its suites are done; sending a real message needs carrier registration for the number it sends from, which is a queue, not a commit in the repository.
Plainly
What this programme is not
- No accounts. Nothing here asks you to register, and no package holds a profile on you.
- No fees, and nothing for sale. No package creates a subscription or requests payment.
- No store listings yet. The download installs the way its notes describe, including the warnings your browser gives about software outside a store.
- No uptime promise. The hosted service runs on a schedule and will be changed while you are using it, sometimes breaking in the process.
- No analytics. These pages load no tracker and no third-party anything; the hosted beta stores what its runs fetched, nothing about you.
The studio site and orbitoracle.ai are the two surfaces this programme runs on, not packages. Counting a website would inflate it.
What broke, and what did you expect instead
A beta is only worth running if the people testing it say what failed. Which package, what you did, what happened, and what you expected — that is the whole report.