Skip to main content
Revolte uses a small set of terms the same way on every page. Each entry below gives a short definition and a link to the page that goes deeper. The full list is in the glossary.

Project

A project groups related applications. Your plan sets how many projects and applications you can have. See Pricing and usage plans.

Application

The thing you build, deploy and operate in Revolte. An application is connected to a repository source and has its own environments and configuration. You can move an application to a new repository without affecting active deployments. See Migrate existing repositories.

Repository

The code Revolte reads, branches and opens pull requests against. Revolte works with GitHub repositories today. See Connect GitHub.

Sandbox

An isolated cloud environment where the agent reads, writes and runs your code. Every task runs in a sandbox, so the agent never works directly on your machine or on production. See Sandboxes.

Thread

One conversation with Revolte about a task in Interactive Chat. You can return to a thread later to continue the work. See Continue existing work.

Agent run

One execution of the agent against a task, for example an autonomous workflow run that takes a Jira ticket to a pull request. A run keeps its plan, code changes and status so you can review what happened. See Review the execution plan.

Workflow

A workflow coordinates agents, context, a sandbox, human checkpoints and external systems around one outcome. It can start from a prompt, a Jira ticket, a bug report or a repository. You can run one interactively or hand it off and come back to review. See Workflow overview.

Environment

Where an application runs: Production, Staging, QA or Preview. Each environment has its own settings, variables and limits. Preview environments let you validate a change before you merge it. See Environments and promotion.

How the terms fit together

You connect a repository to an application. You start a thread or a workflow. Each task runs in a sandbox and produces a pull request. Changes move through environments until they reach Production. Where a person approves is described in the human-in-the-loop model.