Run the task. Check the result.
Rofoil is a platform for running browser and API jobs with the outcome check built in. Every run ends in a verdict, and every verdict comes with the evidence behind it.
Early access. No account yet? Ask Enviera.
- Runner picks up the job
- Opens the product list
- Page answers 200, reads 24 products
- Saves a screenshot
- Check: at least 20 products. Found 24.
- Targets
- Web pages and APIs
- Verdicts
- Verified, not verified, held, fault
- Evidence
- Steps, screenshots, audit trail
- Access
- Viewer, staff and admin roles
Every run ends on one of four lamps.
Fencers know the scoring box. A coloured lamp is a touch. A white lamp is a hit that landed off target. Rofoil gives a run the same kind of answer, and the answer comes from a check you wrote, not from the runner reporting that it finished. The fourth lamp is the referee calling halt: the run stops until a person decides.
Select a lamp to see an example.
Verified
Catalog size on shop.example
- Check
- At least 20 products
- Found
- 24 products
The runner's result matches what you said it should be.
A job with no check can never show as verified. That is on purpose.
Every run leaves a record.
Open any job later and see what happened, in order, without asking the person who started it.
| Job | Catalog size, shop.example |
|---|---|
| Started by | A staff member, from the console |
| Runner | The runner that picked it up |
| Steps | 5, each with its own time |
| Screenshots | 1, taken before the check |
| Check | At least 20 products |
| Found | 24 |
| Verdict | Verified |
| Audit trail | Created, picked up, finished |
Pick the thing that has to be true.
Each job names its check before it runs. These three work today. Jobs read web pages and public APIs, including pulling data from public pages, and a runner that Enviera operates does the work.
| The check | A job could say |
|---|---|
| An exact number | The export has 412 rows. |
| A minimum | The store lists at least 400 products. |
| A page status | The pricing page answers 200. |
Controls your team can rely on.
What is built and running today. Where something is still being switched on, it says so.
- Roles
- Viewers look, staff run jobs, admins manage runners. The API enforces the role itself, not only the screens.
- Separate by organisation
- Jobs, runners and records belong to one organisation, and every query is scoped to it.
- Audit trail that is not editable
- Who created, started, stopped or changed a job is written to a trail that the application cannot alter or delete.
- Targets that are refused
- Jobs aimed at health, payroll or identity systems are refused up front. Runners also refuse addresses inside private networks.
- A person says yes first
- A job can require approval before it runs, or stop partway and wait. Only admins and owners decide, never the person who asked, and a request nobody answers in time expires, with nothing carried out.
- Sign-in through Enviera
- Accounts sign in through the Enviera portal, with the role carried across. Being enabled for early-access accounts.
Where it stands, and where it goes.
-
Today
Jobs against web pages and APIs. A live timeline, screenshots and an audit trail for each job. Approval before a job runs, or when a runner stops partway.
-
Next
Crawls across many pages, with limits on size and speed. A runner on your own computer, so it can work where your logins and network are. It connects out to Rofoil, so nothing is opened on your network. Notice by email or chat when something is waiting for approval. Job types that act on other systems, such as submitting a form, with approval built in.
-
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 keep the passwords of the sites it works on.
