taskq.xyz / request-access
private beta intake · customers · operators · partners

Request access to the execution layer.

TaskQ is for teams that need more than an AI API: customer-owned credentials, verified workers, policy-bound placement, private capacity, audit exports, and HashIQ proof for every request.

Access request

Tell us what you need to prove.

Every request should tell us which wedge matters: custody, jurisdiction, private workers, operator capacity, audit evidence, developer integration, or strategic partnership.

Submissions post directly to the TaskQ intake endpoint. We reply from a monitored address once access is provisioned.

Three intake paths

Not every lead is the same. The page should route serious people fast.

Customers need proof. Operators need settlement. Partners need to understand why TaskQ is not a wrapper.

Customer — I need controlled AI execution

Healthcare, legal, public sector, enterprise security, financial services: BYOK credentials, policy-bound placement, HashIQ receipts and exports.

Operator — I can bring verified capacity

Colo, GPU, sovereign infrastructure, edge, private cloud: worker registration and attestation, signed heartbeat and leases, settlement mapped to chain entries.

Partner — I want the control-plane story

Investors, integration partners, auditors, procurement: verified-capacity registry, provable placement engine, non-backfillable proof corpus.

What happens next

Access should feel serious before a sales call exists.

Classify

Customer, operator, partner, or developer.

Scope

Jurisdiction, custody, retention, capacity, and evidence requirements.

Provision

Tenant, policies, credential handles, and proof surfaces.

Prove

First request returns proof headers and a chain entry you can verify.