Skip to content
For builders

Publish your connector on the Orchard.

Built a VGI worker? List it in the marketplace, set your pricing, and let teams discover and subscribe to it with one line of SQL.

Apply to publish Build a worker first
How it works

From worker to listing in four steps

Step 01

Build a VGI worker

Implement your connector as a VGI worker in any supported language. It exposes schemas, tables, and functions over the VGI protocol.

Step 02

Describe your listing

Add a manifest: name, category, summary, the tables and functions you expose, an example query, and your pricing model.

Step 03

Submit for review

We review the worker for correctness, security, and a clean schema. We test the attach flow and your example queries.

Step 04

Publish & get paid

Once approved, your connector appears in the Orchard. Subscriptions are billed by Query.Farm and paid out to you on a revenue share.

The manifest

One file describes the listing

The manifest is what the marketplace card, the detail page, and the review checklist all read from — name, category, pricing, the objects you expose, and a query that actually runs.

Prototype

The manifest format is a prototype and will change as the Orchard matures.

orchard.toml 
# orchard.toml — connector listing manifest (prototype)
id = "my-connector"
name = "My Connector"
category = "Streaming"
summary = "One-line description shown on the marketplace card."
language = "python"

pricing.model = "subscription"   # free | subscription | enterprise
pricing.note  = "From $49/mo"

[[offers]]
kind = "table"
name = "my.things"
description = "What this table contains."

[example]
sql = """
ATTACH 'my-connector' AS mc (TYPE vgi, LOCATION 'https://orchard.query.farm/my-connector', TOKEN getenv('ORCHARD_TOKEN'));
SELECT * FROM mc.things LIMIT 10;
"""
Apply to publish

Have a connector to share?

Tell us what you’ve built and we’ll help you get it listed. Query.Farm runs the commercial side so you can keep working on the connector.

  • Query.Farm handles billing, credentials, and distribution.
  • You keep a revenue share on every subscription.
  • Your listing sits in the catalog beside every other connector.
  • Exact terms are set during onboarding while the Orchard is in preview.

Or just email [email protected] — that reaches the same person.

Requirements

What a listing needs

  • A working VGI worker that runs as a hosted service.
  • A stable schema — tables and functions that won’t change without versioning.
  • Auth handled via DuckDB secrets / Orchard tokens, never hard-coded.
  • A runnable example query that returns rows.
  • Clear docs for each table, function, and required credential.
Apply to publish Schedule a call

We reply within two working days. Exact revenue-share terms are agreed during onboarding while the Orchard is in preview.