heaventree's database tips its hand: this fork wants to be a product

heaventree laid down the fork's entire database design in a single pass, and the shape of it is telling. Every user gets their own encrypted slots to store AI provider keys, so each customer can bring their own account rather than sharing a central one. There are also account tiers and message credits, which look a lot like the bones of a billing system. Documents carry full version history, and there's a structured, spreadsheet-style review feature for working through documents in bulk.

heaventree also made a deliberate security call: the front end can't reach protected data directly. Every request routes through the backend, which acts as the sole gatekeeper for who sees what. It's a defensible design and a sign someone is thinking about access control, not just features.