Skip to content

Roadmap

What is coming to Sutra, by area.

This page lists what Sutra released recently and what is coming. Each page in these docs shows its own status, and the Target samples show the API these changes lead to.

Recently released

  • Short project ids and short resource names in every request, and ids that Sutra assigns when a create leaves them out. The SDKs and the CLI take a default project.
  • A new sandbox opens no port, and a port is private unless you make it public.
  • A port serves its own number only. One port of a sandbox can serve all of its ports instead.
  • A sandbox runs until you stop or delete it, or for a time limit of any length that you set.
  • Inputs Sutra does not act on are refused with INVALID_ARGUMENT instead of being ignored.
  • Failures are reported as failures: a process that cannot be started, a command that times out, and work that is still in progress.
  • The SDKs and the CLI offer only what the API carries out.
  • Processes find software installed with sudo or in /usr/local/bin, and each sandbox has its own SSH host keys.
  • A stopped app can be started again.

Surface

The API, SDKs and CLI.

  • One structure for the whole API: one service per resource, full names in every response, operations for slow calls, requestId, etag and field masks on every change, and filters, labels and page tokens on every list.
  • Errors with a reason you can match on.
  • The Sutra SDKs for TypeScript and Python, and the sutra CLI, with the same names in every language.
  • One process resource for commands, terminals and code, with output you can page through or stream, signals and input.
  • Start a stopped sandbox again, and a lifecycle policy with a timeout, an idle timeout and a time a stopped sandbox is kept. Your organization or project sets the defaults and the limits; a sandbox without a policy runs until it is stopped or deleted.
  • Port resources, host names that cannot be guessed, signed links, and a proxy that passes headers, cookies and WebSockets.
  • Egress policies that limit which hosts a sandbox can reach.
  • Agents in place of apps: revisions, sessions with their own sandboxes and the invocation contract. Services that run all the time on a stable host, built on the same revisions.

Storage

What a sandbox keeps, and how fast it starts.

  • Faster creates, with the disk size you ask for, and volumes that attach to a sandbox.
  • Sandboxes and templates from any OCI image.
  • Stop and start with the whole disk, on any machine.
  • Snapshots you can create sandboxes from, and forks.
  • Stop and start with memory, so processes continue where they were.
  • Sandboxes from a template that start from a booted system instead of booting.
  • Faster starts and forks.

Identity

Who can do what, and who did it.

  • Resources that are ready to use as soon as the create call returns.
  • An audit record for every change, with the project and who made it.
  • A workload identity for each agent and service, so they can own resources and use integrations.

Platform services

What every sandbox can reach with its workload identity.

  • A model gateway from every sandbox, with no key, including streaming.
  • Telemetry for agents, tools and model calls in the OpenTelemetry format.
  • Workflows: a Temporal namespace for each project.
  • Events you can subscribe to, webhooks and a usage API.
  • Jobs, workers and schedules.
  • Memory for agents.

Type to search…

↑↓ navigate↵ selectEsc close