Guarded Recurring Runs
You demonstrate a browser task to Lokbox once. It then runs to your schedule and within clear boundaries. Before data is transmitted or an external action is triggered, Lokbox waits for your approval. Every run leaves a signed Run Certificate.
Swiss company · Swiss jurisdiction · EU hosting (Germany)
Example run
Four clear inputs
Every run is a small dossier: task, schedule, firm boundary and verifiable outcome.
ART. 01
You describe the concrete outcome, not the technology behind it.
ART. 02
You set the recurring schedule and keep the rhythm in view.
ART. 03
You set the boundary. No defined external action happens without your approval.
ART. 04
After every run, you receive a signed protocol with steps and decisions.
How it works
Not more interface, but one clear workflow with approval built in.
Demonstrate the task once in the browser. Lokbox records the steps, fields and allowed destinations.
Set the timing and boundaries. If something drifts, Lokbox parks the run instead of guessing.
You receive the steps, approval decisions, outcome and hash as a signed PDF with QR verification.
Run Certificate
The Run Certificate is the signed audit protocol for one individual run.
Lokbox · Signed audit protocol
Recorded steps
Approval decision
Approved · User ID DEMO-14 · 07:33:41
Integrity hash · shortened example
SHA-256 · 67c9 2a10 4f71 8b25 … d18b
Example QR · not scannable
01
Links the certificate to one run and time window.
02
Shows the sequence and status of each step.
03
Records the time and user ID.
04
Enables an integrity check.
05
Opens the certificate verification view.
The run data, user ID, hash and QR shown here are non-production examples.
Brakes & security
Approval, drift-stop and evidence are part of every run — not an add-on afterwards.
Approval gate
Before Lokbox transmits data or triggers a defined external action, the run pauses.
Park instead of fail
If a page, field or sequence changes, Lokbox parks the run at that point.
0 credits
Only successful runs use your credit allowance.
Client dossier
AES-256-GCMTraceability
Audit-TrailControl
Access logHosting
EU · GermanyData protection
GDPR / revDSG-alignedFour typical use cases
Four clear starting points — the same controlled frame.
Fiduciaries
Retrieve defined monthly data from heterogeneous approved systems and prepare it in the encrypted client dossier.
View fiduciary workflowStaffing agencies
Repeat the defined monthly cycle, prepare occupation-code assignments and pause before submission.
View staffing workflowInsurance brokers
Retrieve defined portfolio and renewal data from approved portals, prepare it for review and pause before every external action.
View broker workflowProperty management
Retrieve defined property data from approved portals, prepare monthly overviews and approve before external actions.
View property workflowPricing
The approval gate, parking on drift, Run Certificate, encrypted dossier and access log are included in every tier.
Starter
CHF 29/ month
For one clearly defined routine.
Pro
CHF 99/ month
For several clients and regular monthly runs.
Business
CHF 299/ month
For many recurring and more extensive runs.
What is a credit? A credit is the usage unit for successfully completed run work. Shared overage rate: CHF 0.05 per additional credit. Failed or parked runs use 0 credits.
The decisive difference
Free AI browsers schedule tasks. Lokbox adds brakes and verifiable evidence.
| Criterion | Lokbox | Free AI browser |
|---|---|---|
| Recurring schedule | ✓ Yes | ✓ Yes |
| Approval before external action | ✓ Fixed approval gate | — No fixed brake |
| Response to drift | ✓ Parks the run | — No defined parking mode |
| Protocol after every run | ✓ Signed PDF + QR | — No Run Certificate |
| Verifiability | ✓ Run ID, hash and QR | — No verifiable run record |
FAQ
A recurring browser workflow with a fixed schedule, clear boundaries and human approval before defined external actions. Every run produces a signed Run Certificate.
No. You demonstrate the task once in the browser and set its schedule and boundaries. Lokbox repeats the defined workflow.
Lokbox parks the run at the point of drift. A failed or parked run uses 0 credits.
Before a defined data transfer or external action, the run pauses at the approval gate. You approve or reject the prepared step; the decision is recorded.
It records the run ID, time window, steps, results, approval decisions and integrity hash. The PDF with QR verification is a signed audit protocol — not an official document or a qualified electronic signature.
Lokbox is a Swiss company under Swiss jurisdiction. Hosting is in the EU, in Germany. Client dossiers are encrypted with AES-256-GCM and access is recorded in the access log. The service is aligned with GDPR and the revised Swiss Data Protection Act.
Your first Guarded Recurring Run