Docs · Zavent Data

Start here — two product paths

Zavent App and Zpectre are direct-license desktop products. Z-ETL and Zerde are engagement-led infrastructure because the useful answer depends on the buyer's data, environment, and support requirements.

TRACK A

Direct-license desktop products

Choose Zavent App or Zpectre, compare monthly, yearly, and perpetual tiers, then continue to the product buy page.

Compare direct licenses

TRACK B

Engagement-led infrastructure

Contact first, define scope in writing, then receive licensed builds, integration notes, and support terms for that scope.

Request engagement

Product	Path	Primary next step	Delivery model
`Zavent App`	Direct license	Choose tier	Polar checkout, receipt, customer portal, and product access for the purchased tier
`Zpectre`	Direct license	Choose tier	Polar checkout, receipt, customer portal, and product access for the purchased tier
`Z-ETL`	Scoped engagement	Describe the deployment	Licensed build, integration notes, and support terms delivered per engagement
`Zerde`	Scoped engagement	Describe schemas and query goals	Scoped service/deployment configuration and support terms delivered per engagement

Direct-license desktop products

These products can be understood from the public product pages and purchased from the buy pages. Monthly, yearly, and perpetual tiers cover the main individual and small-team paths.

DIRECT LICENSE

Zavent App

Desktop workbook surface

Who it is for: Individuals and small teams doing local spreadsheet, workbook, and tabular data work.
What it does: Opens a local workbook surface for import, inspect, edit, export, snapshot, diff, restore, and provider-configured AI assistance.
What it does not do: It is not a hosted BI platform, warehouse, managed ETL service, or document-corpus workbench.

Choose tier Product page

DIRECT LICENSE

Zpectre

Local document workbench

Who it is for: People building searchable, inspectable corpora from local documents and file collections.
What it does: Processes supported document formats into a local corpus with boundaries, source metadata, review history, and provenance-oriented structure.
What it does not do: It is not a spreadsheet editor, a cloud document vault, a generic chatbot, or an anonymous document-ingestion API.

Choose tier Product page

Engagement-led products — what makes an inquiry serious

Z-ETL and Zerde are specific products, not generic consulting labels. They stay engagement-led because the deployment boundary, data shape, model/runtime choices, and support expectations materially change the licensed build and documentation.

ENGAGEMENT-LED

Z-ETL

Scoped data movement engine

Use it when: Use when you need high-throughput local or customer-controlled data movement with agreed sources, targets, deployment environment, and support terms.
Qualify with: Source systems, file formats, volume, target outputs, deployment host, performance target, audit requirements, and required build flags.
Delivered as: Licensed build, integration notes, deployment instructions, and support window defined in the engagement.
What it is not: It is not sold as an anonymous public binary, hosted ETL SaaS, or unscoped integration promise.

Request scope Product page

ENGAGEMENT-LED

Zerde

Scoped semantic SQL infrastructure

Use it when: Use when you need natural-language-to-SQL or semantic type inference tuned to your schemas, local models, and review tolerance.
Qualify with: Schema shape, data source, query classes, false-positive tolerance, model/backend choice, hardware, access controls, and deployment boundary.
Delivered as: Scoped local service, schema notes, model/deployment configuration, endpoint availability, and support terms.
What it is not: It is not a general-purpose public chatbot, unmanaged database agent, or guarantee that every natural-language question should execute.

Request scope Product page

Licensing and delivery

Polar handles self-serve checkout for direct-license products. Engagement-led products use written scope and engagement delivery instead of anonymous self-serve checkout.

Tier	Meaning	After lapse or purchase
`Monthly`	Subscription rental.	Requires an active subscription. No perpetual fallback.
`Yearly`	Annual subscription with fallback behavior.	Includes fallback access to the eligible version active when the subscription lapses, subject to product license and entitlement checks.
`Perpetual`	One-time purchase for the purchased version.	Includes twelve months of updates. It does not imply unlimited future updates or unlimited support.

Choose the direct-license product and tier on the buy page.
Complete checkout through Polar when a tier link is configured.
Use Polar receipt, license key, customer portal, and any included download access for the purchased tier.
Include any Polar reference when contacting support about a purchase.

The public site does not publish anonymous binary links or invented download commands. Use Contact for purchase support, licensing questions, or scoped engagements.

Support and what happens next

Before purchase

Review the product fit and license tiers.
Use monthly for short evaluation if that path matches your need.
Use contact for product, purchase, or licensing questions.
For team, suite, or bespoke needs, request a scoped engagement.

After purchase

Keep the Polar receipt and checkout reference.
Use the Polar customer portal for subscription and billing operations.
Contact Zavent support for product, license-key, or activation questions.
Use the Zavent contact form for product-support questions.

After an engagement inquiry

Describe the data, deployment boundary, and desired outcome.
Zavent Data confirms fit and what information is missing.
Scope, deliverables, support window, and delivery format are agreed in writing.
Licensed builds and integration notes are delivered against that scope.

Technical notes for evaluators

Keep these as orientation snapshots. Exact build flags, endpoints, performance targets, model backends, and deployment steps are finalized in product materials or engagement scope.

Z-ETL implementation snapshot

Pipeline stages are INGEST, TRANSFORM, and OUTPUT. Common optional build surfaces include DuckDB SQL transforms, local llama.cpp inference, Lua transforms, and optimized release builds. Sources and targets are confirmed during scope.

Published posture includes SIMD CSV parsing, ring-buffered streaming, audit manifests, malformed-row quarantine, and checkpoint/resume behavior. Treat numeric benchmark claims as build-and-hardware-specific until confirmed for your environment.

Zerde implementation snapshot

Zerde runs as a local service with health, query, type-inference, provenance-verification, and model-listing surfaces where they are included in scope. Endpoint availability is finalized per engagement.

The evaluation should focus on schema fit, query classes, review rules, model/backend selection, hardware acceleration, CPU fallback, and what failures must do before any generated SQL is allowed to affect production data.