Build with Qorvyn, from first sign-in to SDK

Quickstart

Qorvyn is proprietary software that is free to use with a free account. It is published on npm; the source is not public. Node.js 22.13+, Git and internet access are required (Qorvyn checks your account online before protected commands).

# in a JavaScript/TypeScript project (or: npm install -g qorvyn for any repository)
npm install --save-dev qorvyn
npx qorvyn activate
npx qorvyn init
npx qorvyn status
npx qorvyn dashboard

1. Activate this device. Open the displayed sign-in URL and use Microsoft or verified email. Never share the device code.
2. Initialize the repository. Qorvyn creates private state under ~/.qorvyn, detects the project and builds its local index. It never joins a team on its own: to share the project with your team, run qorvyn team link.
3. Optional: let your agent tailor the setup. qorvyn init --ai (or qorvyn setup --ai later) asks Claude Code or Codex to read the project and propose agents made for it; everything it proposes is marked for your review.
4. Review before running. Inspect generated agents, workflows, guardrails and every proposed plan or diff.

Daily use

Free and Enterprise access

• Every account starts on the Free plan: it does not expire and includes up to three personal projects. A project is one product, not a folder or a clone: the same repository on a second computer uses the project it already has. Qorvyn sends only a hash of the repository address, never a path.
• One sign-in covers your personal account and every organization you belong to, each with its own role and its own project allowance (qorvyn account shows them). Belonging to an organization never changes your personal allowance, and an organization's projects never use your personal projects.
• Organization projects are authorized separately and never consume personal project slots; an organization's allowance is set in its own agreement.
• A blocked personal account can still use an active Enterprise project. A disabled account blocks every scope.
• Protected operations require a short-lived, project-bound authorization. There is no offline grace period.
• Activation, help, version, entitlement status, export and uninstall remain available for recovery.

Start the local runtime once

All non-TypeScript SDKs use the same loopback-only OpenAPI contract. Start the runtime inside the initialized project, then pass the printed metadata-file path to your application.

npx qorvyn serve
export QORVYN_RUNTIME_FILE="/path/printed/by/qorvyn/runtime.json"

Choose your SDK

The TypeScript SDK ships in the npm package: import { connect } from "qorvyn". Other languages are coming; until then any language can use the CLI's --json output or MCP.

import { connect } from "qorvyn";
const q = await connect({ root: process.cwd(), mode: "auto" });
const hits = await q.context.search("authentication", { limit: 10, path: "src/" });
console.log(hits);
q.close();

One consistent API surface

Security rules

• Never put a runtime token, device key or provider key in source control, logs, crash reports or support tickets.
• Do not proxy the runtime onto a LAN or public address. It is designed for same-machine processes.
• Do not infer Free or Enterprise access in client code. The FACTn service is authoritative.
• Authorization traffic contains identifiers and signed claims—not code, prompts, repository addresses, indexes, secrets or outputs.

Troubleshooting

For support, include the Qorvyn version, operating system, error code and a redacted description. Never include secrets or private source.