> For the complete documentation index, see [llms.txt](https://docs.zongsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zongsoft.com/documentation/en/get-started/hosting.md). # Choose a Host Choose the appropriate Zongsoft host based on debugging, service running, and Web API scenarios. Zongsoft's host is located in [`Zongsoft/hosting`](https://github.com/Zongsoft/hosting) repository. The host is only responsible for starting the runtime and hosting plugins, and should not write business code directly. ## Host Type ### Terminal Host The terminal host runs through a console and is suitable for interactive debugging, command line reproduction, and observing the behavior of plugin-based applications. source code directory: ``` hosting/terminal ``` ### Background Service Host The background service host is suitable for deployment as a Windows Service or Linux systemd service for long-running background applications. source code directory: ``` hosting/daemon ``` ### Web Host Web hosting is based on ASP .NET and is suitable for Web API, authentication and authorization, HTTP pipeline, site configuration and interface debugging. source code directory: ``` hosting/web/default ``` ## How to Choose When developing and debugging plugins, give priority to using the terminal host; when you need to verify the HTTP interface, use the web host; when preparing to deploy as a background service, use the background service host. ## Next Steps After selecting the host, continue reading [Deploy Your First Plugin](/documentation/en/get-started/deploy-first-plugin.md) to learn how to deploy the plugin to the host's `plugins/` directory. ## Reuse Conditions Shared business contracts can be reused in different hosts, and controllers, middleware and interactive commands require corresponding host capabilities. When building business services, try to put protocol adaptation at the edge, so that terminal commands and HTTP controllers call the same service. Existing hosting combines multiple infrastructures by default. If you are learning for the first time, you can use the independent minimal host in the tutorial. When you need a ready-made running solution, read the construction and deployment instructions of [Terminal](/documentation/en/hosting/terminal.md), [Background service](/documentation/en/hosting/daemon.md) and [Web](/documentation/en/hosting/web.md) respectively. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zongsoft.com/documentation/en/get-started/hosting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.