Automations that run inside your app, against your schema, refused by your gates.
$ npm i @frontierjs/orion
A schema import and one plugin
Flows, versions and runs are declared models with real gates, so they are data in your database rather than rows in somebody else’s.
// db/schema.lite
import "@frontierjs/orion/orion.lite"
// api
import { orion } from '@frontierjs/orion'
app.configure(orion())Triggers, conditions and actions
A trigger is a model write, a cron schedule, a webhook or a manual run. An action creates or patches a model, calls a service, makes an HTTP request or sends a notification. All of them are nouns the app already has.
A flow runs as its owner
Every step goes through the same gates a person does. A flow cannot read or write anything its owner could not, and run history redacts protected fields the way the audit trail does.
Runs on the job queue and survives a crash
The run is checkpointed once per stage, so a worker killed mid-run is replaced by another that finishes without repeating the finished stages. A wait can last days and resumes once.
Flows, runs and credentials, mounted by one file
The builder and the run inspector are components from the same kit as the rest of the app. Each node’s settings form is built from its schema, so a node you add gets a form too.
Nothing — there is no common equivalent to swap out.
The rest of the stack