AI agents: use the documentation index at llms.txt to locate machine-readable pages. This section is indexed by https://docs.particular.net/platform/llms.txt. The markdown version of this page is served as plain text. An MCP server at /mcp serves the same content via the search_docs and read_doc tools; it is read-only and needs no credentials. Markdown versions of documentation pages are available by appending .md to the page URL. Directory URLs use index.md. They are served as text/plain because some retrieval backends reject text/markdown.

Running the Particular Service Platform in containers

The Particular Service Platform can be deployed using Linux containers instead of Windows hosting. This page gives an overview of how the pieces fit together and links to the detailed deployment guide for each one. It's the starting point for anyone setting up the platform in containers for the first time; each linked page has the full configuration reference for that piece.

Component overview

graph LR subgraph Storage errordb[(RavenDB<br/>Error instance)] auditdb[(RavenDB<br/>Audit instance)] end errordb --> error["ServiceControl Error instance<br/>+ integrated ServicePulse"] auditdb --> audit[ServiceControl<br/>Audit instance] monitoring[ServiceControl<br/>Monitoring instance] audit --> error monitoring --> error

Only the Error and Audit instances need a RavenDB container; Monitoring instances don't store any data. Audit and Monitoring instances are optional but recommended.

Deploying the pieces

Deploy the pieces in this order:

  1. RavenDB, one container per Error or Audit instance. See Managing ServiceControl RavenDB instances via Containers.
  2. ServiceControl Error instance, the only required piece. Enable integrated ServicePulse on this container so no separate ServicePulse container is needed. See Deploying ServiceControl Error instances using Containers.
  3. ServiceControl Audit instance (optional), if audit message history is needed. See Deploying ServiceControl Audit instances using containers.
  4. ServiceControl Monitoring instance (optional), if endpoint performance monitoring is needed. See Deploying ServiceControl Monitoring instances using containers.

A standalone ServicePulse container is still available, and is needed to view a Monitoring instance and an Error instance from a single address, or to manage more than one Error instance from the same ServicePulse. See Running ServicePulse in containers for that scenario.

Next steps