---
title: "Services"
description: "Run a long-running server on a stable host."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.jgcp.mistrivedev.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Services

:::note[Planned]
Services are not available yet. The samples show the planned API.
:::

A service is a server that runs all the time and answers requests on a stable host. Use it for APIs, web apps and anything else that is not tied to a session.

## How a service runs

A service runs in a sandbox that it owns. The sandbox appears when you list sandboxes, with `owner` set to the service, and you can run processes in it and read its files like any other sandbox. Requests to the service's host, in `uri`, go to the port named in the revision.

A service runs one sandbox. Running more than one, with requests spread across them, comes later.

## Shared with agents

Services and agents use the same parts:

- A [revision](https://docs.jgcp.mistrivedev.com/services/revisions/) holds the definition, and the service runs its active revision.
- Instances are ordinary sandboxes owned by the workload.
- Each has its own workload identity and can use [integrations](https://docs.jgcp.mistrivedev.com/platform/integrations/).

The difference is how requests are routed. A service sends every request to its one host. An [agent](https://docs.jgcp.mistrivedev.com/agents/) gives each session its own sandbox.

:::note[Today]
Today `anchor app deploy` runs an image in one sandbox behind a host of its own, which is close to a service. See [Deploy an agent](https://docs.jgcp.mistrivedev.com/agents/deploy/).
:::

Source: https://docs.jgcp.mistrivedev.com/services/index.mdx
