Leadership

Muhammad Faheem Bantva

Founder & Chief Executive Officer

Muhammad Faheem Bantva is the Founder and Chief Executive Officer of ORQVION. He leads product, engineering, and go-to-market from Pakistan — not as a remote brand overlay on a foreign SaaS, but as the company that ships the desktop and the license server.

The bet is architectural: an autonomous coding agent is useful only if the customer still owns the repo, the prompts, and the indexes. ORQVION is built so AI assistance does not require uploading a private codebase to someone else’s cloud.

Commercial operations match that constraint. We bill in PKR through JazzCash, Easypaisa, Alpha, and bank transfer, and we sell international plans on the same entitlement catalog the desktop app reads from the license server.

Headquarters

Pakistan-based

Pakistan

ORQVION is a Pakistan-based company. Headquarters, product decisions, and customer support are led from Pakistan. We build for Pakistani agencies, banks, public-sector teams, and global organisations that cannot put source code on a hosted coding cloud.

That is why payments include JazzCash, Easypaisa, Alpha, and bank transfer, why the license server can run inside your network, and why this website’s admin license panel talks to that same server — the one the desktop already uses to activate and refresh a device-bound key.

We sell software that stays on your hardware. Cloud in ORQVION means accounts, subscriptions, device activation, entitlements, updates, and optional consented diagnostics — never a silent dump of the working tree or a permanent prompt archive.

Leadership and the board operate from Pakistan while serving PKR checkout and international plans on the same entitlement catalog. Enterprise conversations focus on SSO, seat counts, and air-gapped license servers — we do not ask for a Git remote or a repository upload to qualify you.

This public site is maintained in English and Urdu and tracks what the desktop actually ships: Online Beta, ONLINE · OFFLINE · AUTO routing, ORQVION AI + GGUF offline paths, and governed agent mode with write approvals. When policy or pricing changes, we update the license control plane and marketing together so desktop activation and website checkout stay aligned.

HQ-led product, engineering, and customer support
PKR billing: JazzCash, Easypaisa, Alpha, bank transfer
Self-hosted license server + this website admin on one control plane

Board

Directors

Board members supporting product, operations, and commercial delivery from Pakistan.

Syed Shozab

Director

Director — strategy, partnerships, and Pakistan go-to-market for ORQVION.

Muhammad Bilal

Director

Director — operations, customer delivery, and enterprise account support.

Mission

AI for software engineering that does not take the repo hostage.

ORQVION exists so teams can use an autonomous coding agent without making a foreign SaaS the system of record for their source.

Online and offline on your machine

AUTO defaults online; OFFLINE uses ORQVION AI + GGUF (llama.cpp). Indexes and agent context stay local. Cloud APIs receive inference only when your routing mode and keys send them there.

Control plane, not prompt proxy

Desktop activate/refresh, website checkout, and admin lookup/revoke call the ORQVION license server for seats and entitlements — not to archive chat or source. One Ed25519 key format everywhere.

Enterprise in the perimeter

SSO, RBAC, policy, audit, and the license database can run on infrastructure you control. Pakistan billing is first-class, not an afterthought.

Why we exist

A user describes what they want in natural language. ORQVION plans, writes, tests, debugs, and maintains the project on the local machine — with AUTO routing (online entitlement/BYOK or offline ORQVION AI + GGUF via llama.cpp, not the Ollama app), a sandboxed agent, and no requirement to paste the repo into a browser chatbot.

Most teams today stitch together a separate IDE, a cloud assistant that wants the repository, a terminal, Git hosting, and a pile of media tools. ORQVION is one desktop: Monaco editor, Cmd+K and Composer, Git, tests, Laravel/web workflows, and stack panels from mobile to XR — indexes and source stay local.

Enterprise is not a slide. The same binary that a freelancer runs is what an organisation deploys behind OIDC/SAML/LDAP, RBAC, org policy, a Docker agent sandbox, and a PostgreSQL license server with an audit trail.

We label what is still deferred or opt-in. LanceDB semantic search ships in the desktop app; ONNX Runtime has a CPU CI benchmark with user-supplied production models. Online Beta Ready defaults online; offline ORQVION AI + GGUF is in the same binary. GitLab review-bot parity and cloud background agents are not claimed as complete.

If you need a design-partner pilot or an on-premise license server, you talk to us. You do not upload a repository to get a quote.

Shipped, not sketched

From local IDE to governed enterprise platform.

Public copy tracks implemented phases. Research boxes that are still open are listed on Features — we do not bury them.

Tauri + Rust + React IDE: Monaco, AI engine, sandboxed coding agent, Git, terminal, tests, Laravel/web stacks, and local project intelligence. Online Beta adds online + offline AI with AUTO routing.
SSO (OIDC/SAML/LDAP), RBAC, PostgreSQL license server, org policy, container sandbox, and structured audit — the governance layer around the same desktop.
PK payments, this marketing site, ops/hardening, device-bound licenses, and fail-secure defaults so a pilot can run without JSON-file “databases” for org data.
Cmd+K, Composer, MCP, Ask/Plan/Debug, and related editor workflows — shipped as Tier A/B. LanceDB (desktop) and ONNX CI benchmark are implemented (C7); GitLab bot and Tier C cloud depth remain deferred.

Values

How we decide what to ship.

Privacy boundary

If a feature needs your repo stored permanently on our servers, it is the wrong feature.

Honest limits

Partial research stays labeled partial. Marketing does not outrun the test suite.

Least privilege

Agent tools, website admin roles, and license admin keys are gated. Secrets stay out of logs.

Pakistan-built

Product, support, and PK payment rails are run from here. Global teams are welcome; the HQ is not fictional.

What you actually get

A desktop engineer, plus the server that governs seats.

This is the same surface documented on Features and Enterprise — summarised for people who landed on About first.

ORQVION Desktop

Online Beta IDE: editor, ONLINE/OFFLINE/AUTO routing, Cmd+K, Composer, MCP, agent approvals, Docker sandbox, Git, debugger, and stack adapters.

License server

Self-hostable PostgreSQL control plane: packages, JazzCash / Easypaisa / Alpha / bank transfer checkout, device bind, Ed25519 activate/refresh, revoke, usage metadata — not chat or repo storage.

This website

Public catalog and PK checkout against that server. Authorized operators look up and revoke the same keys the desktop presents in Settings.

Read every shipped feature →

How we work

Design partners and on-prem first. No repo as a cover letter.

Sales conversations start from your perimeter, your identity provider, and your license server — not from a source upload.

Talk, then deploy

Contact sales for pilots. We will ask about SSO, air-gap, and seat counts — not for a Git remote to clone.

Same key everywhere

A key bought here or issued in the enterprise console activates in the desktop. Authorized operators verify keys through the same license server.

Support from Pakistan

Enterprise@ and the contact form reach the team that ships the product. Legal pages cover privacy, terms, refunds, and digital returns.

Who it is for

Individual developers, agencies, startups, enterprise teams, and creators who need code plus media in one place — without a cloud coding tenant holding the source.

What stays local

Source, documents, credentials, local databases, chat history, indexes, offline GGUF weights, and Git repositories. Online inference goes to providers you enable (BYOK in keychain) — not through the license server as a relay.

What the cloud holds

Accounts, subscriptions, device activation, entitlement metadata, updates, and optional consented diagnostics. Checkout and license lookup hit your license server control plane — not a second copy of your repo.

Work with the team that builds ORQVION.

On-premise license servers, design-partner builds, and Pakistan billing — without handing over the repository.

Contact us Enterprise overview

ORQVION is built in Pakistan for teams who will not send their source to the cloud.