Environments
The instances that run your rule sets.
You author a rule set once and run it many times. The place where a run happens is an environment: an isolated instance that accepts run requests, evaluates rule sets against the input you provide, and keeps its own variables, secrets, schedules, and logs. Authoring and running are two separate sides of the product — see Authoring & Executing for how they fit together.
Environments and organizations
Every environment belongs to exactly one organization, which is the ownership and billing boundary. The organization decides which plan limits and credit balance apply to its runs and controls who can administer it. A single organization can own many environments — for example, separate development, staging, and production instances of the same rule sets.
Access is granted per environment through environment users, each carrying one or more roles: Read, Write, Run, Debug, and Admin. The Run (or Admin) role is what lets a member start runs. How sign-in maps to environment access is covered under Authentication.
Creating an environment
Create an environment from the environment editor. You give it a name, choose a hosting option (this choice is fixed once the environment exists), and add the environment users and roles who should have access. The options — Dedicated, Shared, and Free tier — are covered on Hosting Modes.
Getting an environment ready
An environment must be registered before it will accept runs. What that takes depends on the hosting option:
- Shared and Free tier environments run on the shared host and are ready immediately — no setup is needed.
- Dedicated environments are linked to your own cloud resources through a guided setup. Once the linked instance reports in, the environment moves from Not Deployed to Deployed and can run.
The environment dashboard
Each environment has a dashboard that summarizes recent activity and configuration: a recent logs panel, the list of environment users and their roles, and an environment details card showing the name, user count, and registration status. Admins get a Manage Environment action that opens the editor to change the name or adjust users. For dedicated environments, an update banner appears when a newer version of the app is available.