Skip to content

Zev Product Profiles

This site holds one canonical profile per Zev product. Each profile captures what the product is, who uses it, what it does, how it's built at a summary level, and the security and compliance posture behind it.

Access

You're reading this because you authenticated through Cloudflare Access with an allow-listed email. Sessions last 24 hours; re-authenticate after that. To request access for a colleague, partner, or investor, contact the cofounder.

Why this site exists

The cofounder uses these profiles as the base material for company-level documents — investor briefs, partner overviews, vendor security questionnaires, NDPC filings, the parent-company narrative. Product owners use them as a single canonical brief they can hand off when someone asks "what does actually do?"

The profiles are short on purpose. Marketing detail lives on zevop.com. The full data-protection record lives at compliance.zevop.com. Engineering depth lives in each product repo's docs/ directory. This site is the middle layer — the brief that knits the others together.

Where to start

  • New here? Read About ZevOP — the parent-company overview and how the products relate.
  • Looking for a specific product? Start with the Products index — every Zev product, one page.
  • Drafting a new product profile? See TEMPLATE.md and CONTRIBUTING.md at the repo root on GitHub.

Section conventions

Every product profile uses the same twelve sections, in the same order:

  1. Snapshot
  2. Mission
  3. Audience
  4. Core capabilities
  5. Architecture summary
  6. Data the product handles
  7. Security posture
  8. Compliance posture
  9. Integrations
  10. Roadmap signals
  11. Contacts
  12. Change history

Predictability matters more than per-product creativity — readers compare across products, and a deterministic shape is what makes the cofounder's job (composing a parent-company brief) tractable.

Conventions

  • Verifiable claims only. Every sentence describes something that is true today and could be verified by looking at the product, the database, or the code. Aspirational content goes under section 10 (Roadmap signals) — and nowhere else.
  • Summary, not detail. Security and compliance sections summarise; the source of truth for detail is compliance.zevop.com. Profiles link out rather than duplicate.
  • No customer names, vendor terms, or pricing. This site is shared with partners and reviewers; treat it accordingly.
  • One H1 per page. The product name.

The full style guide lives in STYLE.md at the repo root.