Apps

The read side of an app: the catalogue, its deployments and the framework Deplo detected for it.

Queries

apps lists the caller's apps, app(slug) reads one. Both take an optional q, which keeps only apps whose name, slug or id contains it (case and separators ignored).

deployments reads deployment history directly; the same list is also navigable from the entity, App.deployments and App.latestDeployment.

App.framework names the JavaScript framework Deplo detected for the app, re-derived on every deploy. Before an app exists, the same detection runs as detectRepoFramework(repo, buildMethod, ...), which is what the new-app wizard shows while you pick a repository.

search(q) is not scoped to the active team

It answers with the apps and databases matching q in every team the caller can reach, each hit carrying the team it lives in, so a client that has an app's name but not its team can find it and then work there, with X-Deplo-Team for an API token, or the team argument of an MCP tool call. It is a loop over the ordinary per-team reads, so a team the caller cannot enter right now (an unmet two-factor policy, a token scoped elsewhere) simply contributes nothing. At most 50 of each kind.

Example

List apps with their latest deployment:

query {
  apps {
    name
    status
    latestDeployment {
      status
      createdAt
      commitMessage
    }
  }
}

Queries

Example

See also

Deploying and rollbacks

Deploy hook

Databases

On this page