A standalone marketplace. One guarded bridge.

Hirqo is its own services marketplace — providers list services, seekers hire them, on Hirqo’s own accounts. Hirqo Connect is what ships inside OpSphere: tenant-scoped bridge records that keep one provider identity across your modules, with nothing dispatched and no money moved without review.

THE SHAPE OF IT

Two products. One bridge between them.

Hirqo — the marketplace

STANDALONE

A public services marketplace with two audiences: providers who list and manage services, and seekers who search, request quotes, and hire. It has its own brand, its own accounts, and its own roadmap — it is not an OpSphere suite module, and OpSphere does not resell it.

Own provider and seeker accounts
Own listings, quotes, and bookings
Separate product with a separate roadmap

Hirqo Connect — the bridge

LIVE IN PRODUCT

The integration layer inside OpSphere. It keeps tenant-scoped bridge records — provider links, guarded quote requests, category and service mappings, and a webhook event inbox — so one provider identity can serve your modules without porting the marketplace into your workspace.

Bridge records, enabled per workspace
Tenant-scoped and audit-logged like every OpSphere record
Review-first: nothing dispatched automatically

WHAT THE BRIDGE DOES TODAY

Bridge records, not marketplace promises

Everything below is in the product now. If a capability is not on this list — bookings, payments, live dispatch — it lives in the standalone marketplace or on a roadmap, and we say so.

One provider identity

Tenant-scoped provider links map the companies you already work with — ProBuild suppliers, CareOps vendors, PropertyOps-Zaavi maintenance vendors — to the same provider record, referenced against the standalone Hirqo marketplace.

Provider link records per workspace
Same provider identity across modules
Optional link to your existing business-partner records, validated in your workspace

Guarded quote requests

Quote requests are drafted from ProBuild, PropertyOps-Zaavi, or CareOps records and staged through explicit statuses — draft, internal review, ready — inside your workspace. Nothing is auto-dispatched to the marketplace.

Drafted from module records, per workspace
Explicit status path before anything is sent
Provider links validated before use

Webhook event inbox

Marketplace events land as idempotent inbox records — the same event is never recorded twice — with bookkeeping statuses for review. Receiving an event does not trigger any marketplace action.

Idempotent by event ID
Reviewed and processed on the record
No automatic marketplace side effects

Category and service mappings

Service-category mappings and provider service references keep workspace records pointed at the right standalone Hirqo services — reference records, not a port of the marketplace catalog.

Service-category mapping records
Provider service references
Reference data only — catalog stays in Hirqo

TENANT-SCOPEDAUDIT-LOGGEDENABLED PER WORKSPACE

SEPARATE PRODUCT, SEPARATE AUTH

The line we keep, on purpose

A marketplace and an operations platform serve different people under different rules. Keeping Hirqo standalone keeps marketplace accounts away from your tenant data, and keeps your tenant’s records under OpSphere’s isolation, permissions, and audit discipline. The bridge carries records — it does not blur the two products into one login.

Want the bridge walked through against your supplier and vendor lists? Book a demo and bring both.

WHAT STAYS IN HIRQO

Hirqo accounts, bookings, messages, availability, reviews, payments, and moderation live in the standalone Hirqo app — they are not OpSphere features and we do not claim them

Separate auth, by design: signing in to OpSphere never signs you in to Hirqo — the marketplace keeps its own provider and seeker accounts

The bridge does not auto-send quote requests and does not move money — bridge records are staged and reviewed inside your workspace first

Hirqo is not an internal supplier portal: it remains a standalone public marketplace brand where providers list services and seekers hire them

WHERE IT SURFACES

One provider identity, three modules

The bridge exists so the company fixing a furnace, bidding a scope, and serving a warranty call can be the same provider record everywhere it appears.

ProBuild

Suppliers in the RFQ → bid → purchase-order chain can carry one provider identity through the bridge.

VIA HIRQO CONNECT

PropertyOps-Zaavi

Maintenance vendors on the early-access roadmap map to the same provider records — no duplicate vendor files.

VIA HIRQO CONNECT

CareOps

Pilot vendor records can reference the same provider identity ahead of the warranty-dispatch roadmap.

VIA HIRQO CONNECT

Hirqo is a standalone marketplace product with its own accounts and terms. Hirqo Connect provides workspace bridge records inside OpSphere; it does not make Hirqo part of the OpSphere suite, and marketplace availability is independent of your OpSphere plan.

See the bridge against your vendor list.

A 30-minute demo runs on your suppliers, vendors, and maintenance contacts — provider links, a staged quote request, and the webhook inbox, live.

Book a demo Explore modules