Documentation menu

Getting started

Introduction

Build and run AI-native business systems in Perstack Studio, from Project to Activation.

Perstack is a subscription platform for building and running AI-native business systems, operated by Wintermute Technologies, Inc. at perstack.ai. Agents carry out business processes through declared operations, with rules enforced by the platform before a write takes effect.

Start in Studio with a Project. Use Perstack FDA or the API to author immutable Agent and Definition revisions. A Definition's source is a JSON envelope with a nonempty dsl string containing the definition text for its records, operations, and rules. A plain-language description can help FDA plan that Definition. Return to Studio to review revisions and create a Release: select exact Agent revisions and check Definitions to include their displayed latest revisions. Studio does not offer an older Definition revision selector; use the existing Release API to pin an older exact Definition revision. Submit an Environment Deployment with a configuration revision, wait for it to be ready, then activate it to receive new runs.

The authoring and promotion sequence is Project → Agent revision → Definition revision → Release → Environment Deployment → Activation. Saving a revision alone does not activate it. Your first Project walks through each step, including the separate logical Environment lifecycle transition.

What makes it different

An agent given real work can do real damage. The usual answers are to keep agents away from anything consequential, or to wrap them in hand-built guardrails that someone has to maintain.

Perstack takes the rules out of the agent's reach. They are part of the definition, enforced by the platform before an operation executes, not instructions the agent is asked to follow. An agent cannot pay above a limit, post the same invoice twice, or call an operation nobody defined, because those are not choices available to it.

That is what makes it reasonable to hand over work that matters. Every run leaves a record showing what was requested, what was checked, what committed, and why — so the delegation stays inspectable after the fact.

What you work with

A Project is the boundary for a workflow. It contains Environments, Agents, Definitions, Releases, and Deployments. An Agent is a versioned coordinator or delegate that carries out operations. A run is one unit of work an Agent performed, and the record is what it left behind.

Some operations complete on their own. Some wait for a person to approve them. Some are refused outright. Which is which is stated in the definition, and the platform enforces it.

Where to go next

To build something, start with Your first Project. To understand the model before building, read Definitions.

To integrate Perstack with systems you already run, see the API reference.

Related