Run-App

Run-App hosting is a platform that lets you deploy and manage applications in a containerized environment, typically using Docker. Applications are organized as stacks, and each stack contains one or more services.

GraphQL Gateway

All Run-App operations go through a single GraphQL endpoint:

https://cloud-gateway.sabay.com/graphql

Authentication

Every request must carry both headers:

HeaderValue
service-codecloud_user
AuthorizationBearer {token}

Subscription vs Pay As You Go

Most operations accept an optional subscriptionId (String). It is optional in the schema, but the app.web.cloud.sabay.com frontend always sends it, taken from the route or the stack record. The pages in this section document that Subscription flow.

The schema also has productId and appCode arguments for the Pay As You Go flow. The frontend never sends them; that flow is documented separately on Pay As You Go.

Asynchronous actions

Every stack and service action — container_createStack with deployNow, container_updateStack, container_deployStackById, container_startStackById, container_stopStackById, container_deleteStackById, and the service actions — only says whether the request was accepted (success / message, for example "Stack is being processed"). The outcome arrives later through the container_stackActionReceived subscription, documented on Real-time Events.

The frontend shows a toast only when success is false; otherwise it waits for the event. Stack and service lists, the service detail and the service log poll every 5 s, but only while a status can still change.

Status codes

Stacks and services carry a numeric status: Int.

Stack

CodeMeaning
1Deployed (running)
2Stopped
3Processing
4Created (never deployed)
6Failed

Any other stack value is shown as Stopped.

Service

CodeMeaning
1Running
2Stopped
3Processing
4Created
5Removed
6Failed

Real-time event statuses map to these codes as follows: ACTIVE → 1, INACTIVE → 2, PROCESSING → 3, CREATED → 4, REMOVED → 5, FAILED → 6.

The frontend blocks every mutating control while the stack is 3 (Processing). A service can be started only when it is not Running, Created, Processing or Removed, and stopped only when it is not Stopped, Created, Failed, Processing or Removed.

Reference

SectionContents
StackList, create, update, inspect, start, stop, restart, deploy and remove stacks
ServiceList and inspect services, start, stop, restart, pull & restart and remove them, read their logs
Resource & PolicyCPU and memory options, restart conditions, and stack resource usage
Container RegistryManage the registries that stacks pull private images from
Pay As You GoThe productId flow, not used by the app.web.cloud.sabay.com frontend