Your APIs, checked every minute. From inside your network.
A schedule runs a request, a folder or a whole project on a cadence — every request with its scripts and its checks, exactly as Send does on your desktop. Sonda Server runs it on a box of yours, so it reaches the APIs only your network reaches, and nothing of a run ever leaves it. When it breaks, the people who need to know hear it. When it recovers, they hear that too.
A schedule
The server runs it. The store keeps it. The team reads it.
On the minute, Sonda Server opens the copy of the project sealed for its key — written from the store at the last publish, never from anyone's computer — checks every file against the project's signed head, and sends each request through the same engine your desktop uses: the folder's auth, the scripts, the checks, the shared environment as the saver resolved it.
The run becomes a record in the team store, signed by the server and sealed under the project's key: whoever opens the project reads its runs, and nobody else does. Not LockFlare, not the box the store is on.
Sonda Server, and pairing itEvery request, every check. Kept where the team reads it.
What a run record holds, what the board shows, and what a record never keeps.
Request by request, as the runner shows them.
Status, time, size and the checks' verdicts for every request. A request that failed keeps its response for diagnosis — 64 KB a body, 8 MB a run.
Run now, when you cannot wait for the cadence.
One run out of its cadence, after a confirmation, within a minute. A paused schedule runs once and stays paused. The run lands in the list as the server writes it.
One board for the workspace, failing first.
Every schedule the person may see, with how many runs in a row it has failed. A project whose last run failed is marked on the Projects page. A bar per run — its height the duration, its color the verdict — with the success rate, the average and the slowest run from the newest 30.
A server started again picks up where it was.
It knows where each schedule was from the runs in the store. One run at a time per schedule; slots missed while the server was down are not made up — one run, then on from there.
A record never keeps what it should not.
No address as it went out — the URL resolved, a key in its query. Every secret value masked in every text of the record and of the alerts: a check's reason, a console line, a response's headers and body.
Told when it breaks. Told when it's fixed. Not every minute in between.
The server sends on the changes, read from the runs themselves, so a restart never loses count. By mail, through the organization's own mail server handed to Sonda Server sealed for its key — plain text, no body, no header, no value, no link, up to 20 addresses. By webhook, a POST of JSON signed with HMAC-SHA256 when a secret is set, set by administrators, never following a redirect.
The mail goes to your mail server, the webhook to the address you give, the runs to your store. Nothing of it reaches LockFlare.
Sign in first. Fetch the list. Run it for each one.
An advanced schedule sends sources before the target — requests of the project — and reads their JSON answers into the variables the target uses.
Sources, up to five
Sent before the target, each through the same engine: its folder's auth and scripts, the environment, what the sources before it filled. Up to 20 variables each, read from the answer by path.
A sign-in, read and dropped
The first source signs in; its token fills a variable for the sources after it and for the target. A source's answer is read and dropped — a sign-in's token is never kept.
The loop
One source can loop the target over an array of its answer: once per element, up to 500, with loopIndex counting from 1. An empty array is a good run with nothing to run over.
A source that fails
No 2xx, no JSON, or a path that finds nothing: the run is refused, the record says which source and why, and the alerts count it.
A schedule gives nobody more than they have.
The server checks before every run, with the permission files as they stand now — not as they stood when the schedule was saved.