Work

The Vandor ecosystem is maintained as one body of public technical work.

This map is meant for orientation. It shows the main surfaces Vandor maintains and the route each one serves in the larger system.

Map logic

The work is grouped by function, not by one long inventory.

Products, reference, publication, and collaboration should feel like connected surfaces with distinct jobs, not like disconnected sections of a brochure.

Products

Vandor builds tools that structure technical work from the start and keep later changes easier to reason about.

vx

Composable CLI for structured backend work.

vxt

Coming soon

Templating engine for structured Vandor workflows.

vpkg

Coming soon

Packaging system for shipping reusable Vandor artifacts.

Reference

Reference stays close to the product so setup, version changes, and core usage remain readable.

vx Docs

Versioned product reference for current and future `vx` releases.

Getting Started

The shortest path into installation and first use.

Writing

Writing carries slower judgment, field notes, and technical arguments that do not belong in product docs.

Vandor Writing

Editorial desk for essays, security analysis, and working methods.

News

News keeps the release trail visible through announcements, updates, and product notes tied to live work.

Vandor News

Announcements and release-adjacent publication from across the organization.

Partnership work

Collaboration with other teams keeps the ecosystem grounded in real operational systems and public use cases.

Partners

Current partner proof and the collaboration lanes Vandor is built to support.

Collaborate

Fit-check and contact path for teams that may want to work with Vandor.

Next paths

Follow the organizational frame, or open a collaboration path.

Read about Vandor

About

Read how products, reference, publication, and partner work fit together inside Vandor as an institution.

Collaborate

See the kinds of technical situations and organizations that are a good fit for working with Vandor.