The platform · on-site controls
How midas works.
Five parts that run tasks, protect your information and keep you in control.
Support
One service, one number to call.
- One service for the whole system.
- One record from the first step to the result.
- Your administrator controls the settings.
- We monitor the machine’s health, without reading your files.
Part 01 · The work
Tasks that keep moving.
midas follows the workflow, tracks progress and waits when it needs you.
View an example job board
EXAMPLE JOB BOARD
15 working · 14 queued · 3 waiting · 1 available
WORKFLOW · VERSION · STATE · ATTEMPT
- Candidate shortlist v7 Working 1/3
- Reference follow-up v3 Working 2/3
- CV reading v11 Working 1/3
- Client pack v4 Review —
- Offer letter v6 Review —
- Customer record tidy-up v2 Working 1/3
- Timesheet check v5 Working 1/3
- Brief summary v9 Done —
WHEN SOMETHING CHANGES
- temporary error
- Retry up to 3 times
- website changes
- Stop and notify you
- power loss
- Resume from the last step
- approval needed
- Wait for a person
- batch window
- 22:00–06:00
A paused job never times out — it waits for a person.
The machine's job board, as it appears on screen.
workflow libraries
Ready-made workflows. Built around your firm.
Thirty-one recruitment workflows come with the machine — no one in your firm writes or updates one.
Browse the workflows →- Choose the connectors, the output and the approval points.
- Updates are tested before they take over.
- Outside AI help is optional. Your feedback stays on your machine.
8–15
Tasks at once
1–2,000
Tasks a day, including overnight work
31
Recruitment workflows included
Next: what the machine is allowed to send outside the building. 02 · Private information →
Part 02 · Private information
Control what is shared.
Outbound requests are checked and recorded before they leave.
Egress ledger
STEP 01 · 03:41:19 HKT
The question, as typed
Priya Raman or Wai-kit Cheung —
who fits Head of Compliance?
Budget HK$1.85M.
Nothing leaves
local · 0 bytes out
1 / 5STEP 02 · 03:41:20 HKT
Found in your own files
2 CVs · the role brief · your files
11 passages · read on the machine
Nothing leaves
local · 0 bytes out
2 / 5STEP 03 · 03:41:22 HKT
What actually left
role: [ROLE_2] · budget: [AMOUNT_7]
candidates: [PERSON_11] · [PERSON_12]
ask: which profile fits, and why
Code words only
1,204 bytes · logged · check: pass
3 / 5STEP 04 · 03:41:24 HKT
The answer, in code words
[PERSON_11] is the stronger fit —
carried [LICENCE_3] through an inspection.
An outline back
inbound · 812 bytes · no identities
4 / 5STEP 05 · 03:41:25 HKT
The answer you see
Priya Raman is the stronger fit —
SFC Type 4 through a first inspection
[CV — Priya Raman.pdf, p.2]
Names put back
3 claims cited · 0 orphans · local
5 / 5The key linking code words to names stays on midas.
An example record of what was shared.
Follow the full example →A complete record
What left, when, how big, and where it went — exportable for any date range.
A hard stop
Names and numbers on each client's list can never leave, even if every other check fails.
No way in
We cannot log in from outside — updates arrive as sealed packages you install yourself.
Evidence and limits
Protection you can check. Limits we explain.
- For things with a fixed shape — HKID numbers, sums of money — the block is exact, every time.
- Beyond those, checks err on the side of hiding too much — when in doubt, nothing goes.
- Behind both, a final stop in the machine itself — and zero leaks across all testing to date.
- We will not say unhackable, provably impossible, or guaranteed private.
Next: who holds the keys to the systems the machine works in. 03 · Access to your tools →
Part 03 · Access to your tools
Your connectors. Your access rules.
Every sign-in to your systems is locked to the machine — we never hold one.
CONNECTORS · PROTECTED SIGN-INS
6 connectors · sign-ins kept on the machine
- ats read + write/gated rotated 12d ok
- crm read + write/gated rotated 12d ok
- erp read only rotated 31d ok
- mail draft only · send gated rotated 7d send held
- client portal submit gated rotated 9d submit held
- regulator public register, read rotated — ok
export refused · sealed material cannot leave the appliance
Example connectors and their access permissions.
You control access
You hold the keys. We don’t.
A stolen box gives up nothing — the keys are useless anywhere else.
- Each job gets only the access its workflow has declared in advance — nothing more.
- Anything that changes a system waits for a person — the stop sits in front of the key itself.
- You set how often keys change, and every use is written into the record.
- The keys can never be copied off the machine — not by a job, an administrator, or us.
- If you leave, every connection is cut and everything the machine has learned is deleted — with proof.
Next: whose name is on the work when a job uses one of those keys. 04 · Clear responsibility →
Part 04 · Clear responsibility
Know who did what.
Each job signs in under a named account, owned by a person in your firm.
IDENTITY · ROY-4812-a
profile isolated · 37 acts · all attributed
- agent
- ROY-4812-a
- owner
- P. Wong · Director, Compliance
- desk
- financial services
- profile
- isolated · no shared cookies
- scope
- ats, crm, client portal
- created
- on-box · 2026-03-04
ATTRIBUTED ACTS · RUN #4,812
- 10:16:04 open client portal
- 10:16:29 fill candidate fields
- 10:18:41 halt gated action
- 10:19:07 auth approved by P. Wong
- 10:19:09 submit accepted MRD-118-S3
no act on this box is unattributed
One named account, and everything done under its name.
Clear responsibility
Every agent has an owner. Every action has a record.
When a client asks who submitted something at 10:19 on a Tuesday, the answer is a name.
- Each job signs in under its own separate account — nothing carries over between clients or candidates.
- Every account is owned by a person in your firm — ownership is part of the record.
- Accounts are created by your administrator — a job can never create one for itself.
- Remove an owner and their accounts stop with them.
- A picture-by-picture record of each account's screen is kept in your building, replayable any time.
Next: the stop that stands in front of every one of those actions. 05 · Your approval →
Part 05 · Your approval
Ready to send? You decide.
When a task needs your approval, midas waits. It cannot skip your decision.
Nothing leaves without your yes — and every yes is on the record, with a name on it.
GATE QUEUE · 3 HELD
nothing sent · nothing submitted
approvals today 7 · all attributed to a named person
expiries none · a held action never times out into being sent
Ready for your review
HELD 00:26 · SUBMIT + SEND
Candidate pack — Head of Compliance, Meridian Partners
run #4,812 · ROY-4812-a · 3 claims cited · 0 orphans held for P. Wong · Director, Compliance
- Offer letter — Cheung, W. HELD 04:11 · OFFER FIGURES
- Reject notice — 3 candidates HELD 12:38 · REJECTION
The phone approves one item at a time — it cannot change where the machine stops.
Your control
The important calls stay yours.
Eight recruitment workflows wait for a person to review and approve.
See which tasks need approval →- The stop sits in front of the key, not in the AI's instructions — so it cannot be skipped.
- Each approval covers one item, once — never standing permission.
- Every approval carries a person's name, and the exact document they reviewed is kept alongside it.
- A no is recorded too, with the reason, and a person finishes the job.
- Where the machine stops is decided by your compliance lead, at the machine — never by us.
See the approval step in action.
Half an hour, no slides — bring a task that ends with something being sent.