Skip to main content
Gravix Layer Agent Runtime gives each runtime its own sandbox with dedicated CPU, memory and disk, for running code, shell commands, a browser or a desktop. It is called over HTTPS. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to gravixlayer and these variables:
  • GRAVIXLAYER_API_KEY
Sandbox size comes from the template set as providerTemplate.

​
Key and permissions

GRAVIXLAYER_API_KEY is a Gravix Layer API key. Create it in the console at app.gravixlayer.ai; it is shown once. It is sent as a Bearer token. The provider doesn’t document key scopes or roles, so a key has full access to the account. Sources: docs.gravixlayer.ai: sdk usage, docs.gravixlayer.ai: runtime overview, docs.gravixlayer.ai: templates, docs.gravixlayer.ai: overview, docs.gravixlayer.ai: update timeout.

​
Limits

  • The runtime terminates when it reaches its timeout, which is set in seconds and can be extended. The SDK example uses 300 s. No maximum is documented. (source)
  • Pause frees CPU and memory and keeps the runtime. Automatic idle pause is not documented. (source)
  • Template sizes: base-small 1 vCPU/1 GB/4 GB disk, base-medium 2/2 GB/6 GB, base-large 4/4 GB/8 GB. No larger maximum is stated. (source)
  • Regions: AWS us-east-1 (default) and AWS ap-south-1. The docs do not state the CPU architecture. (source)