Trust

Open client, private routing intelligence

What Ormas makes inspectable, what remains service-side, and where the product creates value.

Your local boundary should be inspectable

The Ormas client, MCP connection, local OpenHands execution, credential storage, worktree isolation, allowed-path enforcement, and verification commands run on your machine. Those components form the public client seam so customers can inspect how source code and provider credentials are handled.

Your repository path, source, local provider key, and plaintext lease tokens do not belong in the Ormas routing request or its receipts.

What the hosted service contributes

Ormas is not valuable because it hides model names. The service maintains the changing evidence needed to decide which approved model and harness are likely to complete a particular task at the lowest verified cost:

  • task classification and routing policy;
  • model × harness × task-type reputation;
  • cost, latency, capability-boundary, and escalation evidence;
  • verification-quality calibration;
  • outcome learning, abuse controls, billing, and settlement; and
  • versioned trust receipts.

The local tuple list is a safety allowlist for server-selected execution, not a downloadable copy of the router.

Forks and the Ormas name

An open client may be modified or forked under its repository license. The Ormas name and visual identity are separate from the code license: a fork must not imply that it is the official Ormas service or endorsed by Ormas. A formal public trademark policy is a beta-launch follow-up.

The client repository is currently MIT-licensed. Apache License 2.0 is the proposed long-term client license, subject to an explicit relicensing and contributor review. Until that work is completed, the repository's checked-in LICENSE file is authoritative.

Verifiable service value

Ormas should earn its fee through measured outcomes, not lock-in. Results should identify the selected model and harness, objective verification, cost, and review evidence. Planned signed receipts will bind those facts to task and settlement identities so a modified client cannot fabricate billable success.