Open schema · semver’d · Apache‑2.0

The format your cap table leaves in.

Every Tenacap account exports its complete state as a single archive — spreadsheet files plus a versioned cap-table.json document, bundled with your signed PDFs. The structure is openly documented here and licensed so any tool, or your own accountant, can read it without asking us. This is one of the promises written into our terms: if you ever want to leave, your data walks out the door with you.

What’s in the bundle

Eleven sections, one document.

The export zip contains a MANIFEST.json, per-entity CSV files, attached PDFs, and a single cap-table.json with these top-level sections:

schemaVersionThe format version this bundle conforms to (currently v1).
manifestEvery file in the export zip with its size and SHA-256 checksum — proof the bundle was not altered after Tenacap produced it.
workspaceThe account the company belongs to.
companyThe legal entity: name, jurisdiction, and formation details.
shareClassesEvery class of stock — common, preferred series — with authorized counts and rights.
stakeholdersEveryone on the cap table: founders, employees, investors, and entities.
securitiesIssued holdings — share certificates and option grants — tied to stakeholders.
instrumentsConvertibles: SAFEs, convertible notes, and warrants, with caps and discounts.
vestingSchedulesVesting terms — cliffs and durations — referenced by securities.
transactionsThe append-only ledger of every event that changed the cap table.
auditLogA tamper-evident record of who did what, and when.

// cap-table.json (v1) — abbreviated
{
  "schemaVersion": "v1",
  "manifest": {
    "generatedAt": "2026-05-17T19:42:00Z",
    "files": [ /* path · sizeBytes · sha256 */ ]
  },
  "company": {
    "name": "Hypothetical Co, Inc.",
    "jurisdiction": "US-DE"
  },
  "shareClasses": [
    { "id": "common",
      "name": "Common Stock",
      "authorized": 10000000 }
  ],
  "instruments": [
    { "type": "safe.yc.post",
      "investor": "Acme Angels",
      "amountUsd": 250000,
      "valuationCap": 8000000 }
  ],
  "transactions": /* append-only ledger */,
  "auditLog": /* tamper-evident */
}

Governance

Change-controlled, on purpose.

The schema is published under Apache-2.0 and versioned with semver. The Zod validators in @opencap/schema are the source of truth; the JSON Schema is generated from them.

Any breaking change requires a major-version bump and a six-month deprecation window, with Deprecation headers served on the prior version throughout. We publish migration guides — including ones that take you away from Tenacap.