Run the task. Check the result.
Rofoil runs tasks in a browser or on a computer. A run counts as done only when its own check passes, and everything the runner saw is kept as evidence.
Rofoil is in early access. If you do not have an account yet, ask Enviera.
A hit only counts when the lamp lights.
In fencing, the scoring box lights a lamp when a touch lands. Rofoil gives every run the same kind of verdict, and it comes from a check you wrote, not from the runner saying it finished.
- Verified
- The check passed. What the runner found matches what you said it should be.
- Not verified
- The runner finished, but the check failed or could not be made. You see what it found and what you expected.
- Fault
- The run failed or was stopped. The error is shown in plain words.
A job with no check can never show as verified. That is on purpose.
From a task to a result you can trust
-
Describe the job and its check
Say what to read and what counts as success: an exact number, a minimum, or a page status. Start it from the console or the API.
-
A runner does the work
A runner opens the page or calls the API and reports what it sees as it goes. You can watch the steps arrive live.
-
Rofoil checks and keeps the evidence
The verdict comes from your check. Screenshots, a step-by-step timeline and an audit trail stay with the job.
What works today, and what comes next
- Today
- Jobs against web pages and APIs, run by a hosted runner. Live timeline, screenshots, an audit trail, and access by role: viewers look, staff run jobs, admins manage runners.
- Next
- A runner on your own computer, so it can work where your logins and network are. It connects out to Rofoil, so nothing has to be opened on your network. Approval by a person before an action changes anything.
- Later
- Desktop applications that have no browser or API.
Boundaries
Rofoil does not run against health, payroll or identity systems yet, and it does not store your passwords.
