> For the complete documentation index, see [llms.txt](https://yvechat.gitbook.io/wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yvechat.gitbook.io/wp/landscape.md). # Landscape The web3 AI category is occupied. Each occupant holds a different word. *** ### Who Holds What | Project | Category | The word they hold | Our edge | | ------------------------- | -------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | **Venice AI** | Private hosted inference with a token | Private | Venice runs inference on infrastructure it operates. YveChat runs inference on infrastructure the user operates, including the user's own machine. | | **Bittensor** | Decentralized machine learning network | Decentralized | Bittensor coordinates model production. YveChat is the surface a person works in daily. | | **Morpheus** | Decentralized AI agents and inference | Agents | Morpheus routes to a permissionless inference network. YveChat defaults to the user's own hardware and keys, with networks as an opt-in later phase. | | **Akash, io.net, Aethir** | Decentralized GPU compute | Compute | These sell capacity to operators. YveChat sells custody to individuals. | Each of these is a serious project holding a defensible position. None of them holds **Sovereignty**, and none of them defines the category as the user physically holding keys, data, identity, and compute at once. *** ### The Creneau Category leaders occupy the words that matter most in their space. Hosted assistants own convenience. Venice owns private. Bittensor owns decentralized. Going at any of those directly means fighting on ground already held. The uncontested hole is custody. Privacy describes a policy about what a host chooses to do with data. Custody describes a physical fact about where data sits and who can reach it. That distinction is already fully formed in the mind of a crypto-native audience, because they learned it the expensive way with exchanges. YveChat enters an occupied mind through a door that is already open. *** ### Position, Risk, Opportunity | Dimension | Assessment | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Position** | The only workspace defining itself by user-held custody across keys, data, identity, and compute simultaneously | | **Strength** | The claim is verifiable. A user can watch network traffic and confirm it, which is rare in this category | | **Risk** | Requiring a local installation narrows the addressable audience and adds onboarding friction | | **Mitigation** | The audience already installs wallets, nodes, and self-hosted software. The install is a familiar act for this audience | | **Risk** | Local models sit measurably behind frontier models, which can read as a quality gap | | **Mitigation** | Frontier models remain available through the user's own keys. Local inference is offered where privacy outweighs capability, with the tradeoff stated | | **Risk** | A hosted incumbent could ship bring-your-own-keys and local model support | | **Mitigation** | Doing so would cannibalize the subscription margin that funds them. The zero-margin position is structurally hard for an incumbent to copy | | **Opportunity** | Local model quality improves continuously, and every improvement strengthens the sovereign path at no cost to us | *** ### The Sacrifice Positioning requires giving something up. YveChat gives up the user who wants a single button and no installation. It gives up the enterprise seeking a managed vendor with an accountable support contract. It gives up the promise that the product will be the smartest possible assistant in every configuration. What remains is a defensible position with a narrow, self-selecting audience that already believes the underlying premise. *** Others made intelligence accessible. YveChat makes it yours. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://yvechat.gitbook.io/wp/landscape.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.