A few flows, written, rather than an engine to configure.
Agents that grind through the repetitive work, on whichever model you choose, is the intention. The decision for the first year is deliberately smaller: a handful of hard-coded flows behind feature flags, no rules engine and no configuration screen. This page describes that narrow shape, not a shipped product.
No flow is written or switched on today
What this product does
Hard-coded flows
Every planned automation is code, written, reviewed and deployed like the rest. It isn't assembled with a mouse in an interface.
Switched on by feature flag
A flow goes on or off with a flag, not with a setting exposed to the user. What you see stays decided in the code.
Whichever model you have
An agent that only runs on one provider's model is that provider's hostage. The ones written here are meant to run on a cheap open model or on the plan you already pay for — the same rule the rest of the ecosystem follows.
In detail
No rules engine, and that's the choice
A generic engine is quick to build and long to maintain: triggers, conditions, retries, rule versions. As long as a handful of written flows is enough, the ecosystem prefers readable code to the abstraction. No engine here means a decision, not a project running late.
No configuration screen
No screen will let you compose a flow this year. You ask for a trigger, then it gets written.
What would reopen the question
Two signals, and only two: more than ten flows to maintain, or a client asking for configuration.
The current surface is an illustration
The screen this page opens shows three example flows with dead toggles. Nothing is wired behind them, and nothing runs.
No state to show
With nothing running, there's no history, no log, no counter. This page invents none.
Who it is for
- Something you keep doing between two Morax products
- Once the need has come up several times, it becomes a written flow, rather than a checkbox for everyone.
- A reminder nobody wants to carry
- The trigger and the message are fixed in the code, so they're readable and testable like any other behaviour.
- A flow to try without imposing it
- The flag turns it on for a small scope, and turns it off without a deploy if the result doesn't convince.
See the surface
The screen exists, its content is an illustration. It shows the intended shape, not a service that runs.