> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/applications/private-sub-network.md). # Private Sub Network Keeta has built the network with real-world applicability in mind. Some specific use cases require a level of privacy that a public network cannot provide. To accommodate this, Keeta Network can be launched in a private setting. Instead of the main network, this is known as a sub network. Sub networks operate identically to the main network, but the transactions are private so they cannot be viewed by main network participants. These networks can be launched in a centralized or decentralized manner, leaving the distribution of power and overall accessibility to be determined by the sub network creator. Accounts from the main network can be transferred to any sub network, allowing users to seamlessly utilize the main network and any relevant sub network with their single universal key pair. Balances can also be transferred between networks, allowing sub network transactions to be reflected on the main network once the accounts are transferred back. --- # 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://docs.keeta.com/applications/private-sub-network.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.