FAQ
Is my code sent to Helmora’s servers?
Section titled “Is my code sent to Helmora’s servers?”No. The agents run on your machine, under the bridge, against your local files. Nothing executes on our infrastructure.
When you’re on the same machine as the bridge, traffic never leaves the host at all. When you’re remote, protocol payloads are encrypted at the endpoints and the relay forwards ciphertext — it cannot decrypt frames or read message contents.
What the account service does hold, in plaintext, is operational metadata: device and agent records; session titles and status lines, which include folder names and todo text; and notification titles and bodies, because push delivery requires them. That is real information about what you’re working on, and we’d rather you know it than discover it. The full boundary, including what the relay can still observe and what isn’t implemented yet, is on the Security page.
Which platforms are supported?
Section titled “Which platforms are supported?”The client is one codebase for web, iOS, and Android. The bridge runs on macOS, Linux, and Windows.
In practice, the pre-alpha is exercised on web and iOS (TestFlight). Android builds from the same codebase, but it is not where the daily dogfooding happens, so treat it as less proven.
What does it cost?
Section titled “What does it cost?”Nothing is for sale yet. There is no paid tier you can buy, no trial clock running, and no billing wired to a public signup. See Pricing for the current state — it will say so plainly, and it will change when that changes rather than before.
Can I use my existing agent subscriptions?
Section titled “Can I use my existing agent subscriptions?”Yes, and that’s the intended shape. Helmora drives the CLIs you already have, signed in the way you already signed them in — your Claude login, your Codex login, your Copilot seat, your OpenCode or Goose provider configuration.
Helmora does not resell model access, proxy your prompts through our own API keys, or copy a provider credential off your machine and into the browser. The runtime authenticates itself, locally, the same as when you run it in a terminal.
The practical consequence: whatever plan limits and usage windows your agent subscription has, you still have. Helmora surfaces those usage numbers where the runtime exposes them, rather than metering you separately.
How do I get access?
Section titled “How do I get access?”Helmora is an invite-only private pre-alpha. Account creation and the bridge installer are both gated — the installer endpoints only respond to a live pairing code minted from a signed-in session, so there is no public download to try.
Join the waitlist and we’ll email you when the beta opens.
Is it open source?
Section titled “Is it open source?”No. Helmora is proprietary and the repository is private. That includes the relay, the bridge, and the adapter SDK — so there is no public extension package or build-your-own-adapter guide today.
If you want another runtime supported, the generic ACP adapter makes it a preset plus a verification pass rather than a new codebase, and we take those requests case by case. Tell us which one.
Can I run my own relay?
Section titled “Can I run my own relay?”Not as a supported product. Your two options are the managed relay or a tunnel you run yourself directly to the bridge — and same-machine sessions skip both. Remote access covers the trade-offs, including the fact that a direct tunnel bypasses the relay’s envelope encryption because there is no relay to keep out.
Has the encryption been audited?
Section titled “Has the encryption been audited?”Not independently. The Security page describes what is implemented, and says the same thing there. We’ll update it when that changes, not in anticipation of it.