Access model

Review access depth before the search becomes account work.

Use public search first. Move into governed account access when your team needs larger result sets, workspace collaboration, exports, licensed datasets, RFQs or demand workflows.

Enter workspace Browse public data

Plans

Use records your team can govern

Manufacturers, distributors, wholesalers, installers, buyers, analysts and portals can use deeper structured access without changing the database flow.

License repeatable data instead of manual research

Use normalized product, company, document, price, country and market datasets when your workflow needs repeatable data.

Use demand when sourcing becomes commercial

Use structured demand, RFQ and matching workflows when product and market data becomes part of commercial operations.

Access

Result depth, seats and limits

Plans define users, saved work, exports, licensed data and the workspace actions an account can run.

Public preview stays open More rows unlock by plan Seats and export limits stay explicit

Data

Exports and licensed datasets

Detailed records, documents, change history, market checks and enriched datasets become governed operational value.

CSV and JSON exports by package JSON feed exports for repeat workflows Documents and change history included

Scale

Demand and matching workflows

RFQs, requested items, supplier matches and lead workflows can become account-controlled commercial modules.

RFQ and matching modules Supplier and buyer workflows Demand data remains account controlled

Decision

Start with public results, then review access

If the public catalog answers the first question, the access model helps decide whether workspace depth, exports or licensed data is the next step.

Browse databases first

Start with public search Request account access when records become operational Contracted access packages Access follows use case and depth